Re: XML error logging
Expecting </message> got </session>
Can you show us the XML log that results in this error?
- martin
Can you show us the XML log that results in this error?
Post a reply
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
Topic review
Can you show us the XML log that results in this error?
- Marlon
XML error logging
Hello,
When I have enabled the XML logging for errors within any WINSCP script that we are running seems the structure is different for all the WINSCP connections we have established. I say this as we are using the schema as a reference to validate. I can say this as we see the below error
When I have enabled the XML logging for errors within any WINSCP script that we are running seems the structure is different for all the WINSCP connections we have established. I say this as we are using the schema as a reference to validate. I can say this as we see the below error
Expecting </message> got </session>
- martin
Sorry, I didn't upload the new version. Please download it again.
- Marlonrea
I did, yes.
- martin
Did you redownload the schema?
- Marlonrea
Hi MARTIN,
Thank you but still appears to be an issue when validating.
Error - This schema doesn't appear to be valid by itself (as part of another schema, it might still be ok)
DTD/Schema error - element 'owner' is undefined.
Thank you but still appears to be an issue when validating.
Error - This schema doesn't appear to be valid by itself (as part of another schema, it might still be ok)
DTD/Schema error - element 'owner' is undefined.
- martin
Re: https://winscp.net/schema/session/1.0
OK, now I understand. I've updated the schema. Thanks!
- Marlonrea
Re: https://winscp.net/schema/session/1.0
Martin,
When validating the schema the errors shown in the screenshot are saying "Owner"ve: Cannot resolve the name 'owner' to a(n) 'element declaration' component.
Seems it not being declared which makes it a none valid xsd.
When validating the schema the errors shown in the screenshot are saying "Owner"ve: Cannot resolve the name 'owner' to a(n) 'element declaration' component.
Seems it not being declared which makes it a none valid xsd.
- martin
Re: https://winscp.net/schema/session/1.0
Sorry, I do not understand what does the screenshot show. What exactly are you doing? How can I reproduce that? I do not see any
owner at (or around) the line 76 of session_1.0.xsd.
- Marlonrea
https://winscp.net/schema/session/1.0
Hello,
We have recently started using the XML logging. When validating the schema its appears the Owner tag has a minor issue, see below.
76:43 schema.xsd src-resolve: Cannot resolve the name 'owner' to a(n) 'element declaration' component.
1:1 sample.xml Premature end of file.
What we are trying to accomplish is using xml logging file within our middleware to alert the team if any failures.
Please help with the above issue, thank you a head of time.
We have recently started using the XML logging. When validating the schema its appears the Owner tag has a minor issue, see below.
76:43 schema.xsd src-resolve: Cannot resolve the name 'owner' to a(n) 'element declaration' component.
1:1 sample.xml Premature end of file.
What we are trying to accomplish is using xml logging file within our middleware to alert the team if any failures.
Please help with the above issue, thank you a head of time.