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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics SL (Archived)

Unable to launch Solomon SL (6.5)

(0) ShareShare
ReportReport
Posted on by 50

We've got a problem starting up Solomon (v6.5).  

It began with the mapped drive not working. For some reason, we can no longer map a drive to our Solomon server using \\ServerName\DynamicsSL.  

We've remapped the drive using the ip address.  However, this gives error: Automation error Logon Failure:The target name is incorrect (win7) or Automation error The specified module could not be found (winXP).

Thanks for any help or suggestions you can offer.

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Butch Adams Profile Picture
    4,763 on at

    Is this from any workstation or just one?

    The fact that you can no longer map via the host name means the server or workstation might have lost contact with your Active Directory's DNS server.

    To test this, go to C:\Windows\System32\drivers\etc on a workstation and add a line to lmhosts (If there is just a lmhosts.sam then either rename it without the .sam or create a new file named "lmhosts)

    add to it a line with the ip address and server name of your SL installation in the form of

    xxx.xxx.xxx.xxx Servername

    and see if you can map a drive in the proper \\servername\share form.

    See if this then solves the rest of the issues.

    if it does, then you need to figure out what is not connecting to the DNS server.

  • rwaite Profile Picture
    50 on at

    It is happening on 3 out of 4 workstations with SL installs.

    Adding the lmhosts file solved the problem.

    Thanks!

  • Butch Adams Profile Picture
    4,763 on at

    Glad that got you going.

    Just to reiterate, the lmhosts part is just temporary, Since that fixed your problem, you have a name resolution problem that needs to be looked at. It probably has to do with the workstations not seeing the DNS server in your domain.

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…

Leaderboard > 🔒一 Microsoft Dynamics SL (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans