on 2007 Dec 20 12:35 PM
I'm using 11.5, sr3.
I am having problems with the Business Logic Services Logic Editor. Sometimes it is unable to open a file that it had created just hours before. Sometimes is cannot link to a transaction using the Transaction Call action even though the logic editor can still open the file. I have not found a solution other than recreating the file and that is getting a little tedious.
What is going on here? What is the best solution?
Oh, by the way, the transactions that will no longer open are not even the largest ones I have created... some are as small as 25K or smaller where I have some 60K that open without problems.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I had the possibly good fortune to catch a file at the moment of corruption with a good recent backup. I compared the files side by side and found the following malformed xml tags. The malformed tag is the first, the corrected tag is the second:
<Value xsi:type="xsd:string"/>
<Value xsi:type="xsd:string"></Value>
<Value xsi:type="Xml"><ReferenceDocumentSource/>
<Value xsi:type="Xml"><ReferenceDocumentSource></ReferenceDocumentSource>
Note: even the correct tag above appears to be malformed even though the transaction functioned correctly. It probably should be:
<Value xsi:type="Xml"></Value><ReferenceDocumentSource></ReferenceDocumentSource>
<Name/><Description/>
<Name></Name><Description></Description>
</Name></Description>
</Name><Description></Description>
When I made these corrections I was able to get some of the files back. One file also had a <Local/> tag that appears to be the remains of a malformed <Local></Local> but I don't have a non-corrupt file to compare this one with.
So, what is going on here?
User | Count |
---|---|
5 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.