Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / The semaphore timeout ...
Microsoft Dynamics GP (Archived)

The semaphore timeout period has expired

(0) ShareShare
ReportReport
Posted on by Community Member Microsoft Employee

Hello:

In GP 2013 R2 (12.00.1920), in a test environment, I ran check links on the largest company and on the Financial series of tables.

Doing so took about 3.50 hours and, at about 8% through "CM Receipt", I got the following error:

The semaphore timeout period has expired.

I clicked out of the error, and check links went to another set of tables.  It "finished", by printing its report to screen.  The report did not indicate anything out of the ordinary, and it did not reference the error message that I just mentioned.

Now, I did some research and one web page indicated that this is due to an issue with a network adapter.

And, my IT department indicated that they were going to apply some network adapter patches to our infrastructure at about the time that I saw this error.  I'm not 100% sure about that.  But, I have a vague memory of their saying so.

Could that be what caused this error?  Otherwise, has anyone out there seen this error, before?

Thanks!

John

*This post is locked for comments

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: The semaphore timeout period has expired

    Thanks, Richard!

    John

  • Verified answer
    Richard Wheeler Profile Picture
    Richard Wheeler 75,730 on at
    RE: The semaphore timeout period has expired

    You can start getting into a gray area here as to exactly what is causing this error. Most likely it is something that made the query execute outside the bounds of the normal connection timeout period. The question is was this caused by slow SQL performance or by a network issue? If you have the time you could do this upgrade again and see if you get the same error message at the same place. You could also perform some SQL maintenance, using DBCC commands, to insure your tables and indexes are physically healthy and then do the upgrade again.

    DBCC CHECKDB(Database Name)

    DBCC CHECKCATALOG(Database Name)

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,235 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans