This content has been marked as final. Show 4 replies
Hello,1 person found this helpful
It seems a network configuration issue - can you try ping your DMS URL from a web browser running on same machine where AutoVue server is running & verify if URL is reachable on your 64-bit machine? Also, check if you have any firewall that is blocking incoming calls.
DMS Url is accessible from Web Browser, I also did a Java console app and a test servlet which connected to the DMS server, I am running everything on a single Virtual Machine so not sure if it has something to do with network configuration.
This is most certainly a config problem, but to properly diagnose we will need a complete log1 person found this helpful
You might need to review the config is network config for proxy/firewall, dns, IP, typo on the url ie spaces
Antivirus (blocked ports?), port number changed from 2003 migration to 2008?
If you can access the DMS url, there more likely error is a typo on the DMS URL (verify and or attach html that launches the applet with the logs client/server)
verify if the accept is properly handled by the DMS (review the app server logs)
After all if it was working on 2003 server, chances are that something was not updated in the 2008 server
Also depending on the implementation and the version of .NET you might not be able to handle more than one request at a time
The exception thrown means the jvueserver is not able to open that URL but the reason for it is on the logs prior to this one
Just in case if anyone is interested,1 person found this helpful
I had NetBeans installed on the Virtual Machine on which above exception was happening, after creating a new VM without NetBeans, everything seems to work, I am not sure if some Java libraries that were installed as part of Netbeans messed up AutoVue's communication with my DMS or not