cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Error in executing Xacute Query Template

Former Member
0 Likes
401

Hi All,

While executing Xacute Query Template im getting below error:

Could Not Execute Transaction: [HEM-MES/DataCollect/DataCollect_InsertRecords] Premature end of file.

But this DataCollect_InsertRecords BLT exists in Workbench.Kindly help me to solve this issue. Im using MII version 12.2.3.

Accepted Solutions (0)

Answers (4)

Answers (4)

swaroop_anasane
Active Contributor
0 Likes

Just to add, premature end of file error would occur if you are using an output param and not assigning it from bls or if your transaction is getting completed before it assigns the output property.

You may want to check this dimension as well.

Regards,

Swaroop

Former Member
0 Likes

Hi.

I had the same error org.xml.sax.SAXParseException: Premature end of file after Upgraded from 12.0.0 to 12.2.5. and finally was that the BLS was incomplete because in a condition IF I had no a XML to output.

This error was solve when i added a XML empty to de output when not return a list from the BLS.

Regards,

salvatore_castro
Product and Topic Expert
Product and Topic Expert
0 Likes

Export the 12.0 version of the transaction to the file system so you just have the .trx file.  Then from the 12.2 workbench right-click and import the file directly.  This will perform and inline migration and should alleviate your problem.

Sam

Former Member
0 Likes

HI Experts,

I have similar problem in executing the Query Template. I tried creating empty transaction and copied the entire content but it didnt worked. So i pasted some well formed XML content in the output XML and its worked fine without Premature end of file error. My MII server got updated to 12.2.3 and got this error for most of the transactions. Is there any unique solution to fix it, instead of pasting everytime XML content in every transactions.? And also i want to know how to pass runtime value from transaction to output XML.

Kindly help me..

agentry_src
Active Contributor
0 Likes

Hi Rajalakshmi,

Which version were you updated from? 

In general, I recommend saving your projects off-line prior to any upgrade.  There is a conversion program for importing which usually takes care of any configuration changes, but I suspect there are a few things which get missed. 

When you pasted in the new content into the OutputXML property, it may have corrected the configuration or syntax of the transaction when you saved it.

Use an Assignment action block to link runtime values to your output XML property.  Take a look at some of the downloadable projects which almost always have a similar set up.

Regards, Mike

Former Member
0 Likes

Thanks for your response.

Upgraded from 12.0.5 to 12.2.3.

Actually Basis people will  import project data from 12.0.5 to 12.2.3. So do I need to ask BASIS people to import project again?

Regards,

Raji

agentry_src
Active Contributor
0 Likes

You may want to export it from the 12.0 project and then import it manually to see if that corrects the problem.  You may also want to ask the BASIS folks how the migrated the projects?  I would not have them import the projects again without reviewing the process first.

Regards, Mike

Former Member
0 Likes

Hi Rajalakshmi Sivamani. I have the same problem executing a Xacute Query Template and i did this, and finally works. I formed XML content in the output XML and its worked fine without "Premature end of file error".

So Thanks you!

Note: Tested on sapmii 15

agentry_src
Active Contributor
0 Likes

Hi Annamalai,

Premature end of file usually indicates a problem with the saved transaction contents.  If you have a backup copy of the file, you may want to import on top of your current one. 

Causes of this error that I have run across were usually direct editing of the xml in the transaction or an interrupted save (server or communication link died in the middle of the save).

Can you open the transaction in the workbench?  If so, try to save under a new name and then test the Xacute Query Template with the new transaction.  I have run into problems occasionally when importing transactions from earlier versions of MII.  This sometimes forces MII to correct the syntax or data errors during the creation of the new TRX.  In the worst case, you may have to deleted the transaction in the workbench and rebuild it from scratch.

Regards, Mike

Former Member
0 Likes

Thank you Mike . let me try your idea and update you.

Regards,

Annamalai.

agentry_src
Active Contributor
0 Likes

Hi Annamalai,

I also forgot, but depending on your MII version, you can also create an empty transaction, copy the entire contents of the original transaction into the new one, then save it.  That sometimes also works.

Regards, Mike