No, other users are running on this machine (this is Windows Server) and the same project works for them. Do I need a log to localize the problem?
I'm not sure if this is relavent in your case, but in a totally different scenario I was getting a strange InvalidDefinitionException. It turns out that the functionality that adds/updates WSDL always assumes a HTTP 200 OK response and that the reply contents is a WSDLdocument, thus if ever some other response is returned e.g. HTTP 401 Unauthorised, the add/update functionality ignores it and tries to process the associated reply contents as WSDL when it is not, hence the unexpected InvalidDefinitionException.
This issue was reproduced by SmartBear support and logged as defect number SOAP-5946 (while I found this bug in version 1.7 I haven't seen it mentioned in any of the change logs so I assume it's still there).
Try looking at the HTTP log to see if it gives you any clues.
Thanks, helped disabling Proxy. But there were questions:
1) where to look, what unresolved bugs exist?
2) in the case of an error: "InvalidDefinitionException", the HTTP log was empty. Is it possible to raise the level of logging? so that it was possible to understand where the error originated and which one?
1) Sorry I don't think that SmartBear publish a list of bugs (at least I haven't seem one).
2) I've just double check my Ready API (Version 1.7) and when I update a WSDL definition the HTTP log panel is populated. I know it's an obvious question but is the HTTP log enabled? Each of the log panels can be enabled/disabled?
Yes, I'm sorry, the HTTP log has information: "end of stream".
But it is not yet clear what is causing this? other users in the enabled Proxy all works.
