web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / Microsoft.Dynamics.SL....
Finance | Project Operations, Human Resources, ...
Suggested Answer

Microsoft.Dynamics.SL.AS.DevObj Timeout Error

(0) ShareShare
ReportReport
Posted on by Mark E 6,451

Created a new SL 2015 CU2 server installation for a client to replace their existing one.  Basically replicated the old environment on the new one (not an upgrade).  Installed all the same CU2 build and Hot Fixes as on the old environment.

New server runs Application Server (as does the old one) for Quick Send.  At times, the new server build experiences the following error:

Microsoft.Dynamics.SL.AS.DevObj

Error refreshing Application Servers: Connection Timeout Expired.

If we click the OK button, AS resumes it processing of QS jobs.  But someone has to monitor the AS job to make sure there are no errors, and QS jobs get backed up until OK is clicked.

Not sure what to check to determine the cause of the timeout.

I have the same question (0)
  • Suggested answer
    CFROTON Profile Picture
    CFROTON 4,710 on at

    Hello Mark,

    Actually, there is a solomon.ini setting for this one.

    ConnectionTimeout

    Lets the user set a time-out value for database connections

    DEFAULT: 30

    VALID ENTRIES: 1-3000

    CREATED BY: None

    READ BY: Microsoft Dynamics SL Login (98.000.00), all screens, and Application Server Development

    Objects

    UPDATED BY: None

    -----------------------------------------------------------------------------------------

    [Database Runtime]

    ConnectionTimeout=xx

    Best Regards,

    Jana MacDonald

    MSDSL Support

  • Mark E Profile Picture
    Mark E 6,451 on at

    Below is the Solomon.ini settings that appear on both server environments:

    [Database Runtime]

    BusyRetrySeconds=600

    ROIBusyRetrySeconds=20

    AutoRetry=1000

    RetryWaitTime=3000

    Is the ConnectionTimeout an additional setting that can be added?  Interesting that the original server does not have this setting (not getting the errors), but the new server would need this setting to resolve the issue.

  • Suggested answer
    CFROTON Profile Picture
    CFROTON 4,710 on at

    Dear Mark,

    yes the ConnectionTimeout is an additional setting, go ahead and add it.  

    Are you running a standalone server for the application server?  Whats the difference between the old and new servers?

    The setting was added with the release of 2011 (there were probably other changes with code)

    Best Regards,

    Jana MacDonald

  • Pbrunelle Profile Picture
    Pbrunelle 10 on at

    Wondering if this ConnectionTimeout should really be under [AppServer] section of the solomon.ini instead of [Database Runtime]?  As well as what is the suggested settings for this between 0 and 99?

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 449 Super User 2025 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 422 Most Valuable Professional

#3
BillurSamdancioglu Profile Picture

BillurSamdancioglu 239 Most Valuable Professional

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans