Timeouts from Opalis4 trying to access SQL Server RRS feed

  • Question

  • We are still running Opalis 4. We are having a problem running multiple file loads from a VMWare/Win2003 virtual app server to a standalone SQL2005 Server DB in the same datacenter. We get a timeout error from the Opalis job. THe SQL Server box should be more than adequate power and licensing is processor based, not CAL. If we run load loads individually, they work, although not with great speed. We do not have this same problem on Opalis 3 on an older box. But on the older configuration, the app and database are on the same server.

    We have played around with the timeout parameter in SQL but it doesn't help.

    • Changed type Robert_Hearn Monday, May 3, 2010 4:53 PM corrected type
    Saturday, April 17, 2010 6:50 PM


  • Opalis Robot (v4) is designed where objects of the same type are run sequentially even across multiple workflows (some objects were updated during Opalis Robot lifecycle to run asynchronously but most do not with Query Database being one object that was not updated).  As a result, running multiple ETL type jobs as described is going to result in the first job executing while the other two queue up behind it.  This time spent “in queue” will count against the timeout period configured.


    Opalis Integration Server does not have this problem – it will run objects from multiple workflows concurrently, however it will still error out if the configured timeout value is exceeded which is expected behavior.

    Robert Hearn • Sr. Program Manager
    Customer & Partner Community
    System Center Cross Platform & Interop

    Read the Cross Platform & Interop team blog | Become a Fan on Facebook | Follow us on Twitter | Read my blog

    • Proposed as answer by Robert_Hearn Wednesday, May 5, 2010 12:53 AM
    • Marked as answer by Robert_Hearn Wednesday, May 12, 2010 6:45 PM
    Wednesday, May 5, 2010 12:53 AM