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 / Microsoft Dynamics SL (Archived) / Dynamic SL System erro...
Microsoft Dynamics SL (Archived)

Dynamic SL System error message 5003

(0) ShareShare
ReportReport
Posted on by Community Member

Hi, my question is one of employees computer has been working slow so got him for a new laptop.

Installed dynamic SL correctly. Have 10 database profile under the server.

weird thing is some of profile able to connect and some of are not.

old computer and other employees having no problem, working all these profile. only new computers are having issue.

tried install on other computer too, but no luck.

Do i missing something while install?

mapped drive as v:\\servername\sl

install v:\sl\application\wrskstn\setup.exe

installed requirement.

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Community Member Profile Picture
    Community Member on at

    Tae, which version of Dynamics SL are you running (6.5, 7.0, 2011, 2015)?  When you installed the client on a workstation did you do that under the user's credentials?  Is the user a local admin or did you run setup.exe as the administrator?

    Under 6.5 I have seen this issue when CAPICOM.DLL did not register during the client install.  In such cases, manually registering that DLL took care of the issue.  If you are running 2011 and using Windows authentication then the issue could be that the user has no rights to the SQL database.

  • Community Member Profile Picture
    Community Member on at

    Hi Rick,

    its 2011 and I did it with domain administrator credentials, 
    and clients computer is win7 pro + 64bit. 
    tried install local admin credentials, same thing..no error while install,

    and only half of database able to access.

  • Community Member Profile Picture
    Community Member on at

    Not sure if this will help or not but one of the things I try when a workstation will not connect to SQL (the most common reason for the 5003 error) is to try running the SL database maintenance program from the failing workstation and see if that connects.  It has less layers to go through.  I have also used ODBC management to establish an ODBC connection to the database to see if that connects.  Finally, if none of those connect and you cannot still determine the reason, I have install the SQL Management Studio (the Express version is fine) on the workstation and use it to try and open the database.  If that fails, the event information is typically more useful in determining the issue.

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 > 🔒一 Microsoft Dynamics SL (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans