Jan 11, 2005

Problem starting Server and Workstation services after installing Great Plains

Edit : August 2011 - This post is over 6 years old and it's the most popular post I've ever made. Still going strong! It's one of the top Google results for this type of error.   Still getting dozens of hits per day. Nearly 100 comments! I'm glad I could give something back to my fellow IT pros. I know I spend most of MY day researching errors on Google as well.   (PS - why not throw me a bone and click an ad on my site, like one of the banners up top? I might earn a penny or two. hehe  Thanks!!)
--


I've stumbled across a rather odd issue the past few weeks. At first I just thought it was a typical Windows problem but when it started turning up on more than one machine, i figured there had to be a common thread.

Here is the problem. Your XP machine can't browse the network. You can get the internet just fine but can't connect to any servers. As you are troubleshooting the problem, you discover that several Windows services are not running - Server, Workstation, Computer Browser, Net Logon, among others. These services not running will definitely prevent you from browsing your network and connecting to other machines.

So you try to start Computer Browser manually - it tells you it can't start the service because it has a dependency on another service - which turns out to be Server and/or Workstation service.

So now you try to start Server or Workstation service and you get the same error message on both of them - "The system cannot find the file specified". It also registers an Event 7023 in the event log and says "The system cannot find the file specified." This was happening on my laptop for a few days and i wasn't having much luck finding a solution. In fact, i was getting ready to re-install Windows XP.

But then i ran into the exact same problem on a few workstations at a clients site that i was just working on. They were going thru an upgrade to Great Plains 8.0. So i decided to look a little bit on PartnerSource, which i hadn't checked before since i didn't think it was a GP related issue. I did find an article that talks about this problem. Here is the link for CustomerSource or ParterSource users.

The title is - Error 1068 "The specified file cannot be found" and the Workstation Service Does Not Start After Installing or Updating Great Plains (869971).

What seems to be happening is the installation, update or maybe uninstall of Great Plains is wiping out some registry entries that point to the location of the .dll files that run the Server and Workstation services. So you need to edit the registry and put these keys back in place.

Here are the steps from the TK article:

WARNING If a mistake is made on any of the instructions listed below, you may not be able to restart your system. If you are not familiar with the Registry, please seek assistance from Microsoft or your local Microsoft support representative. Microsoft can be reached at 1-800-426-9400.

1. IMPORTANT - Back up your system before making these changes. It is also important to create a new Emergency Repair Disk.

2. Verify that ServiceDll is stored in the registry at HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services lanmanworkstation Parameters

3. You should see an entry with the Name of ServiceDll, Type REG_EXPAND_SZ and Data value of %systemroot%\system32\wkssvc.dll.

4. If this entry does not exist, you can add it with the following steps: a. Choose Edit-New-Expandable String Value. b. Name the new value ServiceDll (it is case sensitive). c. Double-click on this new value and specify Value data: %systemroot%\system32\wkssvc.dll. You could also copy the reg key from a working workstation.

5. After the entry is added to the registry you should be able to start the Workstation Service. NOTE - The uninstall/install of Great Plains does not remove this registry entry.

Ok, so those steps tell you how to get the location of the Workstation service dll back into the registry. You may find that the last key "Parameters" is missing all together. If that is the case, then right click on LanManWorkstation and select New->Key and name this Parameters. Then continue with step 3.

But in my experience, i was missing both Workstation and Server dlls and all of the machines that had the problem. So here are my additional notes on how to get the Server service running again.

The Registry location is HKEY_LOCAL_MACHINE SYSTEM - CurrentControlSet - Services - LanManServer - Parameters. Again, i was missing "Parameters" key all together so right-click on LanManServer and select New->Key and name it "Parameters". Then in this folder, create a new entry named ServiceDll, of type Reg_Expand_SZ (Expandable String Value) and a data value of %systemroot%\system32\srvsvc.dll. This is the dll for Server service. With this new entry in place, you should now be able to start the Service service as well.

With Server and Workstation service both running, you should now be able to start Computer Browser and any other services that were dependent on them. This should get you properly connected back to the network.

So i've seen this happen on 3-4 different machines now. The one thing in common would be that they previously had Great Plains Dynamics 6.0 un-installed and then Great Plains 8.0 installed. Must be something to do with the Great Plains 8.0 installation since i've un-installed Dynamics 6.0 a million times and have never seen this problem. I'll definitely be keeping an eye on this situation with my other upcoming Great Plains upgrades. I hope this can help someone else and save you from re-installing Windows like I was about to do.

Update : I seem to be getting lots of hits from Google searches concerning this problem. If you've run into this situation and my article helped you, please click down below on the comments link and leave a note, or shoot me an email - TechRoundup@jasonhartman.net. If this looks like a wide spread issue, i can pass the info along to my contacts at Microsoft and see how we can get this taken care of or at least publish some better TechKnowledge articles about it. Thanks for your help!

87 comments:

Beth said...

Thank you SO MUCH. We just did a GP 6.0 to GP 8.0 upgrade and I had this same problem. Your post cut the time it would have taken me to resolve this by days, I am sure.

Jason Hartman said...

Hi Beth,
Thanks for leaving a comment. I'm glad i could help! I figured someone else would run into this problem. And i seem to be getting alot of Google hits on this particular error message/situation.

If anyone else finds this useful, please let me know and i'll pass this info along to Microsoft.

Thanks!

Jason

Anonymous said...

Thanks it has worked with a similar problem generated by exact dental software v8!

Gary

Andy said...

Jason - I just ran into this for the second time. In both instances I was upgrading clients from Dynamics 6 to Great Plains 8, both on SQL. The first time I removed all of the network components and reinstalled them to fix. The registry fix was a bit easier.

Jeff Neumann said...

Had similar issue, but I was missing only the %systemroot%\system32\srvsvc.dll from LanManServer. Have no idea what caused it, we don't use Great Plains, and this laptop's load of XP is only a couple months old.

Anonymous said...

This client originally had GP 7.0, then 7.5 and now 8.0. I always completely uninstall previous version of GP prior to applying new versions. Thanks to your help I was able to only put in a 12 hour day as opposed to the usual 18.

Anonymous said...

Thanks for you precious instructions. My Windows 2003 server had 4 of those services corrupted by "Great Pain Dynamic"!!! If great plains dynamic is my only choice to install on this machine, any work around to prevent that problem happen again?

Tom Garth said...

Hi Jason,

Just finished a 7.5 to 8.0 upgrade and lost some sleep over the same problem. We had already diagnosed the problem and the found KB869971 through Google for the solution.

The disappointment was that MBS had not sent a bulletin out on this. I noticed that the KB piece said it applied to 7.0 and 7.5. I rated the article as poor in their Feedback area yesterday (3/24/2005) evening, noting that it also applies to 8.0. To their credit 8.0 has been added to the list as of this morning.

I believe the 7.5 uninstall was the culprit.

bob muir said...

Had this problem and couldnt think what I had in common with the other guys until I noticed the comment about Exact Dental Software. I had removed that recently. I was missing the server parameter reg entry. All ok now. thanks a lot.

Eddy said...

Your directions were right on the money!! Thank you very much for posting this article - as others have noted, your tips saved me a lot of support time, and kept my customer's downtime to a minimum.

For the record, my customer's problem was caused by the GP7.5 to GP8.0 upgrade. After the upg, some users could not share resources from their workstations, and others did not get a network printer list after a reboot. And I could not connect remotely to their 'Computer Management' consoles. Verifying/setting the registry entries you described resolved all of the above - thanks again!

Anonymous said...

Thank you so much, it worked after spending so many days trying to resolve this, your site helped me and saved me from reinstalling xp.
Note : I was also missing wkssvc.dll file; I have copied this file from another xp workstation.

Anonymous said...

Man... this really works!
Thank you very much for the solution!

Anonymous said...

Jason -

I think I may have possibly figured out why you’re getting so many Google hits, as that is what led me to you site! I consider myself fairly knowledgeable and I'm in the tech industry - but I was stumped on this for a few hours. (After my explanation, others may disagree with my assessment of myself! :) )

I was installing a program that required 'workstation' service to be running. After looking at 3 other XP machines all of which had workstation service running; I began to investigate why it was NOT running on my home machine. Google led me to you at this point, but I had no clue as to the software you were using, or referring to.

After hitting a few more sites, and some Microsoft KB articles, I took a look at what network protocols, clients, and services where running. What I found was that when using XP's network wizard, to set up your home network, if you choose NOT to install file and printer sharing, all it installs is TCP/IP which by itself works fine for web browsing, e-mail, gaming, IM, almost anything. Originally I felt was a security issue, and chose not to install it and if I decided I would need it in the future, I would enable it at that time.

So after adding file and printer sharing - BINGO - server, and workstation services now are running as they should.

Maybe this will help someone in the future.

Anonymous said...

I, too, had the Client for MS Networks and File and Printer Sharing deinstalled for security reasons.

When I tried to access the "Member Of" tab for my user account (using Administrative Tools->Computer Management), Windows would not let me do that because the Workstation service was not running. Neither was the Server service.

Reinstalled File and Printer Sharing and erverything works now as supposed.

Thank you!

Martin

^.^Funny_Monkey^.^ said...

Wow!~ This was great help to me! Thanks lots!

My computer suddenly couldn't access my home network computers one day and I had been scratching my head for about two weeks trying to solve the problem. I gave up and was about to reinstall windows when my gf's brother took a look at my computer and pointed out that my Computer Browser Service could not be started 'cause it was missing some files.

Went to Google, and ta~daa~!! Your article came up and I tried it out... magic! All is good and spiffy! ^.^

Again thanks!!

Anonymous said...

Try this winsock fix which resolved a problem with networking after virus spyware removal.

http://www.spychecker.com/download/download_winsockxpfix.html

Anonymous said...

Upgraded from Great Plains v6.0 to 8.0. Just uninstalled v6.0 from this workstation and then couldn’t browse the network. Your page nailed the problem and the solution.

Thanks for your help.

Microsoft definitely needs to be aware of this problem.

Anonymous said...

Wow - great post, Jason - Thank you very much!

One of Ten said...

Am I ever glad I found this Blog! I've been trying to figure out what was wrong with my LanmanWorkstation service, on Win2000, for at least three weeks! Granted, this didn't completely resolve my issue... But, it's a step in the right direction! Before I found this information, I had absolutely no clue as to what, why, how, ... I had tried repair installing Win2000 twice without success.

I still have no clue what happened to cause this. And, as I mentioned before, it's still not completely resolved. I still get errors in Event Viewer that say the following:
- "Could not load Rdbss device driver."
- "Could not load RDR device driver."

Then there's my favourite error from trying to start LanmanWorkstation:
"The system cannot find message text for message number 0x%1 in the message file for %2."

The reason that's my favourite is because when I see it in Event Viewer, it's repeated, I believe, up to the maximum possible length for an error message! It looks like this:
"The Workstation service terminated with the following error:
The system cannot find message text for message number 0xWorkstation in the message file for The system cannot find message text for message number 0xWorkstation in the message file for The system cannot find message text for message number 0xWorkstation in the message file for The system cannot find message text for message number 0x..."

If anyone's got any theories, I'd love to hear them!
I likely won't get back here anytime soon, as I am EXTREMELY busy with work. Both as an employee for a company and attempting to get my own business up and running. Many weeks, I only get 3 chances to sleep!

I can be reached at 1of10 (AT) 1of10 (DOT) net.

Anonymous said...

For one of ten.

If you still have this problem reinstall only the Rdbss.sys file.

hertbertx said...

jeezz.....thank god for this article. we uninstalled great plains from an nt4.0 terminal server cuz it wasnt needed anymore and ..poof! there goes the workstation service without any clue as to what went wrong. this is the solution exactly...thank you god

Anonymous said...

Thanks. I made the mistake of using a registry cleaner which killed these services. I realized my mistake when MS's Baseline Security Analyser began giving me various errors. Now everything is back to normal.

Great work,
Mike

Anonymous said...

Thanks, this has been very helpful. The computer that experienced this was an RMS install.

soulassassin547 said...

This is the best fix for the problem that's plaguing some of my XP machines! Now I can get back to the network!

Thank you and belated Merry Christmas! :D

Allen said...

Thank you for the information in this artical. I had the problem of not being able to share anything on my network. From your information here, I found I was missing the srvsvc.dll file in the system32 directory. Never had GP or the Dental software, so something else had deleted this file. Maybe it was PC Anywhere? Found the file elsewhere and copied it to system32 and all is fine.

Thanks,

Sunny Miss said...

Here's a bizarre one. I don't know for certain if the effect is related to the cause necessarily but... Workstation service was starting fine prior to the removal of Norton Antivirus. After the removal of said program, the wkssvc.dll file and the corresponding registry entry disappeared completely. Hmmmmmm... =)

Bless you for your timely and extremely useful article.

=)
Sunny

Anonymous said...

Dude u saved a life. Months of mind boggling was saved.

Anonymous said...

I uninstalled Norton AntiVirus 2005 and encountered this problem. After trying all the fixes on this blog i uninstalled the networking component 'Client for Microsoft Networks', rebooted then reinstalled the component.

This worked for me.

casp said...

thanks so much for posting this fix. I was working on a "no network provider accepted the given path" error message and none of the other fixes helped. i was ready to pull out my hair and toss the laptop. but your solution pointed me in the right direction. my registry entries were correct but the dll for lanmanworkstation was missing. i just grabbed it from another system and voila. the problem started after norton av detected a virus running as a service. the name of the service was the same as the dll for lanmanworkstation. in removing the virus it removed the dll and once the comp was restarted no workstation service no network browsing. once again a big THANK YOU

Anonymous said...

Thank You
This fxed the problem.
Great Plains 8 stopped working (and local network access) when version 5.5 was uninstalled from the computer. I would think it was the uninstall that caused the problem, but not sure.
Again, thanks for the great info.

Anonymous said...

Just a warning - if you install that service manually you also need to check the security permissions in the registry.

Its safer to add file and printer sharing via the control panel, then the permissions will be set correctly for you (at least in Windows SP2).

Anonymous said...

The previous poster mentioned installing File and print sharing from the control panel....in the Great Plains situation I have yet to have this work. I've uninstalled File and Print sharing and rebooted then reinstalled, the workstation service still was not properly in the registry. This problem also caused a logon issue for the machine.
The netlogon service requires the workstation service to be running therefore if a user's password has changed or they have not logged into that machine previously they will not be able to log on. Luckily the administrator credentials were cached on the machine I needed to fix and Jason's registry fix did the trick and made me the hero for the day.
Thanks.

Jasen Webster said...

I had a similar problem where the Server Service (lanmanserver) would hang at startup. It would eventually start after 15-20 minutes then everything would be fine until you rebooted the computer again. My problem had nothing to do with the dll's. There were in the registry and on the hard drive.

I followed the advice from one of the posts on here and it worked. Basically, I uninstalled File and Printer Sharing then reinstalled it. Worked great.

murcekim said...

Thanks for the info. I dont use great plains software, but some how lost the server key in the registry. The only software I loaded in the last couple of days was ZoneAlarm Security Suite. After loadng that I lost my ability to VPN and noticed I was getting errors about the server service. Thanks again...big help.

Anonymous said...

Just did an installation of 8 computers from GP 7.5 to 9.0. Five out of those computers had this problem. These had Great Plains uninstalled from Add/Remove programs BEFORE istalling the new version

Anonymous said...

We also don't use GreatPlains, but found this EXACT problem on a laptop that just came in from a remote user who had it for approx. 6 months - not sure what they might've installed or removed (but them leaving Limewire on it is a good indication that it wasn't treated with the love and care it deserves ;)), but this cleaned it right up! Thanks!

Anonymous said...

Many Thanks,

You have saved my day, i was also on the verge of installing windows back but your article has solved my problem.

Thanks again and keepup the good work,

Raj

Anonymous said...

I had the same problem a few months ago and I believe the "workstation" service works when "client for microsoft network" is installed and the "server" service works when "file and print sharing for microsoft networks" is installed... or is it the other way around? :-) Anyway, they ONLY work when the appropriate network component is installed. It's really that simple. On the other hand, if you don't use those network components don't bother if "server" or "workstation" doesn't show in the services' list. Best regards from pt.

Cividan said...

Hi, I came up to your site using google search with "workstation service missing" I wanted to try your solution but I had windows 2000 instead of XP so it didn't worked for me but I found on some other site that these service are related to network properties, workstation is "microsoft network client" (if in a windows network) and server service is "file and printer sharing" what I did is re-install them to fix my problem, I also had to get the machine out of the domain and then back in to complete the repair. I'm letting you know in case this might help someone else.

Anonymous said...

hey all,

many thanks for this help, though it wasnt exactly this that solved the problem, it led me to finding the actual solution.

here is what worked for me:

run ->

Anonymous said...

hey all,

many thanks for this help, though it wasnt exactly this that solved the problem, it led me to finding the actual solution.

here is what worked for me:

run -> services.msc -> server -> properties and changing the startup type to automatic. now the "start" button is highlighted and everything works fine!

i still have no idea why it was disabled in the first place... :s

Anonymous said...

THANKS ! for a completely different reason I had lost my server service, but your fix was exactly the reason.. missing parameter key ..

Bill Scala said...

I discovered that somehow my wkssvc.dll file had a size of 0 in the c:\windows\system32 folder. This is what caused the problem for me. I deleted the zero length file from that location and copied the wkssvc.dll file from the C:\Windows\ServicePackFiles\i386 folder into the C:\windows\system32 folder. After that I was able to start the Workstation service. Then I could finally once again browse the other computers in my workgroup.

Anonymous said...

Hi, Thanx for pointing me in the right direction. I had the same problem where the workstation service would not start. The registry was showing the correct information and the dll's were still in the system32 folder. What my problem turned out to be was the rdbss.sys was missing from the system32\drivers folder . I don't know what caused the initial problem, possibly a disk error whilst the PC was doing a Microsoft update. However copying the rdbss.sys file for the i386 folder cured the problem. Once again thank you.

Chris said...

Thank you. We just did a GP 7.0 to GP 9.0 upgrade and I had this same problem. It was only 1 PC out of 20 PC's upgraded.
Thanks Again
Chris

Anonymous said...

Thanks, another for the fix list.

Travis said...

Just adding my big ol' "Thank You!" to all the others here.
After spending over 20 hours and 2 days beating my brains out over this nightmare, you helped me greatly.
That having been said, another Forum also gave me what proved to be the ultimate solution, so I wanted to share that with everybody here, too, as the scenario appears to be related.
I uninstalled Norton SystemWorks and Personal Firewall prior to installing Windows OneCare Live, but who knows if that really had anything to do with it or not?
All I know is that I had no such problems beforehand.
Between these two articles just about any aspect of this real pain-in-the-neck glitch should be able to be resolved.
The other Website is:

http://www.pcreview.co.uk/forums/showthread.php?p=9252870#post9252870

Hope that helps y'all as much as all of this did me. Good luck!

judith said...

And another big 'thank-you' - lets keep this at the top of the Google rankings.
I don't have 'Great Plains' or Norton antivirus but for some mysterious reason my 'server' service would hang at start up which messed up other software (notably Acrobat Reader) but luckily not Firefox. After 5-10 mins the service would suddenly start up (hard disc suddenly thrashing when I'm not doing anything) and everything would work properly again.
Checked registry keys and all files mentioned in the various posts and all OK.
So followed advice of jasen webster (post from 3/07/2006) and uninstalled File and Printer Sharing and also Client for Microsoft Networks for good measure, re-booted and re-installed and everything is OK.
Thanks once again to everyone for all I've learn't through this episode and from this blog.

Anonymous said...

That did it, thanks!

Eric E

Anonymous said...

Thanks for pointing me in the right direction. None of the steps to resolve worked in my case but, without your guidance it would have taken much longer to resolve cleanly, muc less have to deal with a wipe and reload. I was able to resolve for good by removing and reinstall the Microsoft Client for Networking and I was back in business. It logged into the domain as if it had never left the builing.

GWF

Anonymous said...

Awesome you have saved me hours!

I think a few files got corrupted in an overnight windows update followed your doc through put the DLL's back and the registry in lan man workstaion and hey presto my services all work!

YOU ARE SUPERB!

Thanks

James tcp said...

Hello Jason

Another guy who hit your page from Google. My colleagues PC also experienced that problems with workstation, server and some other services being stopped automatically. manual starting of those services will be killed several minutes after.

Scanning with AV and spyspot did conclude any problems. And your post helped me a lot. I just reinstall that two components mentioned and that PC is working properly with the required services.

Thx very much !

Anonymous said...

Man I was driven MAD with this - endless google searches left me going round in f%^%$^g circles.
thank you soooooooo much for solution
. By the way - this problem was caused for me by exact dental V8 also

John said...

Fantastic - saved me hours if not days - nothing to do with Great Plains here but exactly the same problem.
Thanks
j

Will Knapman said...

Just found your site after having the Server Service problem on two 2003 Server servers at dental practices. Both times the latest version of Exact stopped the Server Service starting, but only after a reboot. It did the same if I uninstalled Exact. The work around was to uninstall and re-install all the networking components. The Lanman registry ebtry was not removed or obviously corrupted at any time. Meanwhile, I am trying to determine what in Exact is causing the issue so I can tackle SOE who make Exact on behalf of my customer. Interesting reading though.

Karl said...

Great page, was pulling my hair out when upgrading Exact on a 2003 SBS server. Your page helped get the server to boot and run properly. Thanks

Anonymous said...

I had a similar problem, although it was only the workstation service that was missing. I encountered the problem on a fairly fresh w2k install, but i did uninstall and then reinstall file and print sharing previously, which may have something to do with it.

Anyway, I followed you directions, but the workstation service is still missing from the service console.

Squid said...

Hello.

I'm another one from Google.

My problem is slightly different, but your post has set me on the right direction.

Neither the workstation, net logon or computer browser services existed. It's a fresh XP home install from last night. I fully updated Windows, and installed AVG Free.

But thanks for your post. Very helpful. =)

Darrell said...

well - I don't know what triggered it, but my one system was sharing files as of yesterday but it stopped today - thanks for the tips, your hints managed to get me restored.

Paul said...

I am having a similar situation in that the server service, workstation service, and computer browser service will not start. I am using windows vista, and when i check the registry the values are there. any further suggestions?

Paul said...

I am having a similar situation in that the server service, workstation service, and computer browser service will not start. I am using windows vista, and when i check the registry the values are there. any further suggestions?

Mumzies said...

I have also had a similar problem with my workstation and computer browser services not loading. I came across this site somehow and am glad I did.

My problems were the same as the first post, but my registry and files were all as they should be. However, one poster mentioned the rdbss.sys file not loading, which was an error under my sys events.

The next poster said to replace the file. I actually had a Windows fix with a fairly recent file but that was not the one in my \system32\drivers folder. So after copying the correct file (from the KB914389 fix) my problem was solved. Workstation and Browser loaded and I could finally see my network shares!

Thank you Anonymous on 11/07/2005 6:34 PM

So to the last poster with similar problem, try this, if all your other files and reg entries are as they should be.

Thanks Jason for leaving this up!
Korynn

Anonymous said...

Thank you very much. My problem was the same (no sharing - a missing file in starting server service) but the solution has been different.
In my case this file was missing: srv.sys in ...\windows32\drivers.
I copied that file from a working system and everything went OK!

by

Lorenzo Luciano

Craig said...

Had the same problem - thanks for the help!

Anonymous said...

had the same problem. thanks for the help!

Sunnie said...

Hi,
I'm facing a similar problem. But i'm on Vista Ultimate. And i've check the registries (HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services lanmanworkstation Parameters :: ) ServiceDll is already %systemroot%\system32\wkssvc.dll.

I'm still unable to start Workstation service.. I don't have Great Plains installed..

Any help?

--

::..SUNNIE..::

Jars99 said...

I was having the problems listed above - the Workstation service wouldn't start and neither would the dependent services. My registry appeared to be intact, I turned on File and Printer sharing, and Re-installed the client for Microsoft Networks, but none of them worked.

Finally, I found that I was missing two files: rdbss.sys and mrxsmb.sys both in the C:\Windows\system32\drivers directory. I copied them over from the Windows CD(i.e. expand D:\i386\rdbss.sy_ C:\windows\system32\drivers\rdbss.sys), and was then able to start the Workstation service.

I suspect my problem was caused by some orphaned files lost because the machine lost power during a reboot.

Thanks for the original post, and for all the comments that helped me figure this out!

rr said...

i have never heard of great whatever you talk about i dont have it installed in this laptop

but from yesterday onwards i am facing an acute problem of some exes crashing with access_violation 0xc00000005

which were working properly before

and i tried finding out why they are crashing and it seemed to be related to wkssvc failure

00EFF7E0 00EFF7FC |FileName = "\\.\PIPE\wkssvc"
00EFF7E4 C0000000 |Access = GENERIC_READ|GENERIC_WRITE
00EFF7E8 00000003 |ShareMode = FILE_SHARE_READ|FILE_SHARE_WRITE
00EFF7EC 00000000 |pSecurity = NULL
00EFF7F0 00000003 |Mode = OPEN_EXISTING
00Eur site FF7F4 40150000 |Attributes = OVERLAPPED|150000
00EFF7F8 00000000 \hTemplateFile = NULL

i googled and landed on your site

after reading the article i query for lanman

and i find only one entry

the whole registry key seems to have vanished


C:\>reg query hklm\system\currentcontrolset\services\ | findstr "lan"
HKEY_LOCAL_MACHINE\system\currentcontrolset\services\\lanmanserver

C:\>

no lanman workstation at all

is there some standard reg entries to create the whole lanman workstation

i see there are lots of entries in
lanmanserver

let me read your article thoroghly one more time

thanks for the nice writeup and hitting the problem on head

Mitch said...

Hey this was a big help and can you believe I could not find anything about this reg key at Microsoft. They completely sent me to a bunch of solutions with symptoms that had nothing to do with the original question. Whether I tried using IP addresses or netbios name it would not work and finally I found this article. Thank you man

Anonymous said...

i tried everything mentioned in this article without success. i have found different solution. at first i disabled wifi in device manager and leave onboard realtek NIC enabled, then reboot and worstation service lags about 2 minutes. then i enabled wifi and disabled realtek onboard NIC in device manager, rebooted and worstation starts normally. it means that realtek is the core of problem. i downloaded and installed newest driver from realtek website, and workstation service starts normally.

Anonymous said...

A very useful piece of information. Many thanks indeed!

Anonymous said...

Thank goodness for this site. I have been battling like crazy with an XP machine that wouldn't browse the network. The registry settings were there and all files were there too but the workstation service would not start. Event log showed " could not load RDR device driver ".

After reading all the posts I removed the File and Print from the Local Area connection and reinstalled it again.

All is well.

Anonymous said...

Thank you. My issue did not have anything to do with GP - but replacing the mrxsmb.sys file fixed my browsing issue after recovering a bad hard drive. Another post brought me here - but it is working. THANK YOU.

Anonymous said...

After check all above situations that were not my case.
I replace Rdbss.sys and mrxsmb.sys file.

Wow! It works.
Thank alls for your experiences.
I just bookmarked this page for later use.

Lam from Vietnam.

Anonymous said...

Who knows where to download XRumer 5.0 Palladium?
Help, please. All recommend this program to effectively advertise on the Internet, this is the best program!

Zwu said...

thank you so much, i couldn't start my Server service either in windows 7 64bit.

your trick with the registry fixed it!

many thanks!

Zwu

19/04/2010

Computer Servers said...

It worked for us too when we were having problems with one of our servers.

Oros007 said...

After 4 hours of shearching and trining, this solved my issue.

Thx

Dale said...

I think you probably won't avoid issues and problems after installing Great Plains. Thanks for sharing your thoughts about it.

delaware corporation

Anonymous said...

I had the same problem on an XP workstation - Non GP software related. Uninstalling and reinstalling the Client for Microsoft Networks and File and Printer Sharing fixed this issue fairly quickly. Of course it took me hours of other attempts to figure that out, but hopefully this helps others.

Thanks

Anonymous said...

Thank you! Thank you! THANK YOU!!!

mrxsmb.sys missing from %systemroot%\system32\drivers

copied and pasted from: %systemroot%\ServicePackFiles\i386 and then workstation service was finally able to start.

This thread is invaluable in solving this problem. Keep it going!

Anonymous said...

Hi,

amazing, 8 years after you wrote this article it is still relevant. I had this problem on a Windows 7 64 bit laptop - workstation service not starting, error 2. The missing registry key was the problem. After searching for hours I finally found your article, and this was exactly the problem. Thank you. Johnny Sutherland

Linda Bubbers said...

Thank you

Anonymous said...

Thanks. I had the parameters folder on a Win7 box disappear today for an unknown reason. This 10 year old post got me back online (August 2015 now)! Thank you!!!

Mark Gallaher said...

Thanks for sharing. I had similar problem too. Hey, check this out. I 've found not bad website http://fix4dll.com/isdone_dll with missing dll-files library. There also is an installation guide.

Fangyaya said...

oakley vault
supra shoes
kobe shoes
coach factory outlet
michael kors outlet online
louis vuitton handbags
louis vuitton borse
tory burch flats
red bottom shoes
oakley sunglasses wholesale
louis vuitton outlet online
michael kors outlet
ray ban sunglasses
toms wedges
louis vuitton purses
red bottom shoes
polo ralph lauren outlet
polo ralph lauren outlet
ugg sale
replica watches
michael kors outlet
louis vuitton outlet
coach outlet clearance
oakley outlet
michael kors uk
coach outlet canada
canada goose sale
longchamp sac
uggs italia
nfl jerseys wholesale
abercrombie outlet
true religion jeans
polo shirts
polo shirts
cheap oakley sunglasses
polo shirts
adidas outlet store
mont blanc pen
burberry scarf
louis vuitton outlet
20168.11chenjinyan

shengda xu said...

ray ban sunglasses outlet
michael kors uk
coach outlet online
ghd hair
dansko outlet
polo ralph lauren outlet online
longchamp outlet store
mulberry handbags
fendi bags
birkin handbags
xushengda0516