Cecil C Taylor 15.Feb.11 04:27 PM a Web browser Applications development/customization 6.5.1 Windows 2003
We have some custom code in a wqs agent on Server X that creates binders and documents within Dom Doc on Server Y. Periodically (sometimes several weeks, sometimes several days), we start getting this error upon any attempt at using the Dom Doc API to create/edit documents and binders:
ddoc2api:Timeout occurred trying to access server.General network problems.A network cable is perhaps either loosely connected or not connected at all
We can still access Dom Doc through the Dom .Doc web interface on server Y once this error starts getting thrown, but any subsequent attempt at adding/editing docs/binders from the web on server X seems to fail with the error above once the errors starts occuring. We end up having to reboot the servers in order for the code to start functioning again. All thats happening is that we are accessing the Dom .Doc API to create/edit binders and documents.
The code works fine, it just seems like there is a point at which something gets hung making it impossible to programatically access Dom .Doc from another server using the Dom .Doc API.