Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Microsoft Dynamics SL (Archived) / Error 5003 on a Win7 w...
Microsoft Dynamics SL (Archived)

Error 5003 on a Win7 workstation but not when the client runs on the server.

(0) ShareShare
ReportReport
Posted on by MBrown0629 85

We've just done a clean install of Server 2008 R2, SQL 2008, SL 2011 and are trying to access an imported data base using a Win7 Pro machine. Client side install went correctly on both the Win7 box and on the server itself.

On the server we can access the data base using the SL client and it appears we can do any 'task' we would like at the server.

On the Win7 box we can launch the client, 'see' the both old and new servers, select the new one, 'see' 2 DB's offered after selecting the appropriate SYS data base we receive an error 5003. Ours also show a (66) right after the name of the DB we are attempting to connect to. I have attempted this from 2 different Win7 machines. We are in a domain and from the Win7 box we can browse to the directory that contains the DB's on the server. The users have Admin rights on the local machine and user rights in AD and SL.

BTW the Win7 boxes are also 'out of the box' and only have been run through Windows updates and have Office 2010 installed.

*This post is locked for comments

  • marsha e. Profile Picture
    marsha e. 165 on at
    RE: Error 5003 on a Win7 workstation but not when the client runs on the server.

    Please note:  I also had a problem relating to SQL Server user permissions.  An administrator user was able to sign onto a new SL2011 workstation, but the particular user was not.  When logged into Windows as her, we also got SYSTEM MESSAGE 5003 after right after selecting or entering the Server name, with the text as described above, INCLUDING the number 66 in parentheses following the Server Name.

    Dear MSFT:  WHY IS THE SYSTEM MESSAGE 5003 THREAD NOT IN PARTNERSOURCE?   IT IS STILL RELEVANT TO SL2011.  PUT IT BACK.

  • Verified answer
    MBrown0629 Profile Picture
    MBrown0629 85 on at
    Re: Error 5003 on a Win7 workstation but not when the client runs on the server.

    Thanks Jeff but here is what I and an MS - SL Tech discovered. After importing an existing DB from the old system and updating to SL2011, although the Users were created the rights within SQL did not follow. SL could see the DB's but the Users (without Sysadmin rights) could not connect to them. This was resolved by using SQL Mgt Studio and verifying that the individual user(s) had the correct access to the DB(s).

  • Jeff Trotman Profile Picture
    Jeff Trotman 275 on at
    Re: Error 5003 on a Win7 workstation but not when the client runs on the server.

    This sounds very similar to an issue I just ran into (although I'm not sure what's going on with the 66). I believe the Windows Firewall on the new Server isn't allowing SQL connections by default, which would explain why it works locally.

    Take a look at this article which explains how to configure the firewall to allow access to SQL Server.  msdn.microsoft.com/.../ms175043.aspx

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,269 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,198 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans