Hi,
We are receiving an XML Error 68 but the error list only convers until error 67. The error happens in an XMLExportFile:
CALL "XMLInitialize" GIVING XML-STATUS.
CALL "XMLAttributes" GIVING XML-STATUS
USING XML-ATTRENABLEV.
CALL "XMLAllOccurrences" GIVING XML-STATUS
USING XML-ALLOCCURENABLEV.
CALL "XMLExportFile" GIVING XML-STATUS USING
WSSAMPLE-SOAPDATA
"../wssample.wsdl"
"../bin/wssample-soapdata"
"CobolToWsdl.xsl".
DISPLAY XML-STATUS.
Any ideas?
Regards,
Juan Urraburu
#XMLExtensions#RMCOBOLThe problem seems to be related with Windows 10. In Windows 7 the XML-STATUS returns 0000.
Hi,
We are receiving an XML Error 68 but the error list only convers until error 67. The error happens in an XMLExportFile:
CALL "XMLInitialize" GIVING XML-STATUS.
CALL "XMLAttributes" GIVING XML-STATUS
USING XML-ATTRENABLEV.
CALL "XMLAllOccurrences" GIVING XML-STATUS
USING XML-ALLOCCURENABLEV.
CALL "XMLExportFile" GIVING XML-STATUS USING
WSSAMPLE-SOAPDATA
"../wssample.wsdl"
"../bin/wssample-soapdata"
"CobolToWsdl.xsl".
DISPLAY XML-STATUS.
Any ideas?
Regards,
Juan Urraburu
#XMLExtensions#RMCOBOLHi, Juan Manuel!
This error was added in 12.06 and is documented in the Release Supplement. Download the latest Release Supplement. You will find this:
68 Error in function: AddAttribute.
An attribute node could not be added during export of a document. Attributes are only added by XML Extensions when the XML ENABLE ATTRIBUTES statement has been executed. This error will not normally happen. One cause could be that the XML engine did not have enough memory to add the attribute node to the document.
What RM/COBOL version are you using? I have not had this problem in years, but I think there was some issue around this at one time.
Hi,
We are receiving an XML Error 68 but the error list only convers until error 67. The error happens in an XMLExportFile:
CALL "XMLInitialize" GIVING XML-STATUS.
CALL "XMLAttributes" GIVING XML-STATUS
USING XML-ATTRENABLEV.
CALL "XMLAllOccurrences" GIVING XML-STATUS
USING XML-ALLOCCURENABLEV.
CALL "XMLExportFile" GIVING XML-STATUS USING
WSSAMPLE-SOAPDATA
"../wssample.wsdl"
"../bin/wssample-soapdata"
"CobolToWsdl.xsl".
DISPLAY XML-STATUS.
Any ideas?
Regards,
Juan Urraburu
#XMLExtensions#RMCOBOLAre the two tests running the same version of MSXML.DLL?
Hi,
We are receiving an XML Error 68 but the error list only convers until error 67. The error happens in an XMLExportFile:
CALL "XMLInitialize" GIVING XML-STATUS.
CALL "XMLAttributes" GIVING XML-STATUS
USING XML-ATTRENABLEV.
CALL "XMLAllOccurrences" GIVING XML-STATUS
USING XML-ALLOCCURENABLEV.
CALL "XMLExportFile" GIVING XML-STATUS USING
WSSAMPLE-SOAPDATA
"../wssample.wsdl"
"../bin/wssample-soapdata"
"CobolToWsdl.xsl".
DISPLAY XML-STATUS.
Any ideas?
Regards,
Juan Urraburu
#XMLExtensions#RMCOBOLHi Tom! Nice to "see" you!
RM version 12.09 with MSXML.DLL v 6.3 in both PCs (Windows 7 and Windows 10)
And other PC with 12.12 and Windows 10 (not sure what msxml is running but it seems that also runs v6)
Hi,
We are receiving an XML Error 68 but the error list only convers until error 67. The error happens in an XMLExportFile:
CALL "XMLInitialize" GIVING XML-STATUS.
CALL "XMLAttributes" GIVING XML-STATUS
USING XML-ATTRENABLEV.
CALL "XMLAllOccurrences" GIVING XML-STATUS
USING XML-ALLOCCURENABLEV.
CALL "XMLExportFile" GIVING XML-STATUS USING
WSSAMPLE-SOAPDATA
"../wssample.wsdl"
"../bin/wssample-soapdata"
"CobolToWsdl.xsl".
DISPLAY XML-STATUS.
Any ideas?
Regards,
Juan Urraburu
#XMLExtensions#RMCOBOLHowdy from Texas, Juan!
My next step would be to use Process Monitor to investigate the process while it is running. (Perhaps by setting a breakpoint in CodeWatch after the XML Initialize.) You can find out more here:
https://technet.microsoft.com/en-us/sysinternals/bb896645.aspx
Also, since this is happening on the generation of the initial XML document, you should be able to simplify the test by eliminating the XSLT.
It is possible that the Windows 10 process is somewhat more memory constrained. Again, using ProcMon to investigate differences between the Win7 and Win10 processes might expose the difference.
Hoping for a good result...
Hi,
We are receiving an XML Error 68 but the error list only convers until error 67. The error happens in an XMLExportFile:
CALL "XMLInitialize" GIVING XML-STATUS.
CALL "XMLAttributes" GIVING XML-STATUS
USING XML-ATTRENABLEV.
CALL "XMLAllOccurrences" GIVING XML-STATUS
USING XML-ALLOCCURENABLEV.
CALL "XMLExportFile" GIVING XML-STATUS USING
WSSAMPLE-SOAPDATA
"../wssample.wsdl"
"../bin/wssample-soapdata"
"CobolToWsdl.xsl".
DISPLAY XML-STATUS.
Any ideas?
Regards,
Juan Urraburu
#XMLExtensions#RMCOBOLWindows 10 might not be configured for sufficient page file space. Have you tried configuring the page file space to be 2 - 4 times the physical memory on the machine.
We did have an error in XML Extensions when 12.06 was released. This error caused a 68 error when attributes were enabled because the attribute name for the uidref incorrectly had an "=" sign in it. I am not sure which version fixed this error (the fix was dated 2011-05-20), but certainly the current version no longer has this error. If you're using the same version of XML Extensions on Windows 7 where you don't get the 68 error, then this isn't the problem anyway.
Hi,
We are receiving an XML Error 68 but the error list only convers until error 67. The error happens in an XMLExportFile:
CALL "XMLInitialize" GIVING XML-STATUS.
CALL "XMLAttributes" GIVING XML-STATUS
USING XML-ATTRENABLEV.
CALL "XMLAllOccurrences" GIVING XML-STATUS
USING XML-ALLOCCURENABLEV.
CALL "XMLExportFile" GIVING XML-STATUS USING
WSSAMPLE-SOAPDATA
"../wssample.wsdl"
"../bin/wssample-soapdata"
"CobolToWsdl.xsl".
DISPLAY XML-STATUS.
Any ideas?
Regards,
Juan Urraburu
#XMLExtensions#RMCOBOLJuan, did you ever determine the cause of the error 68?
