Welcome Guest ( Log In | Join )

Discover the best free computer help!
Learn more about Geeks to Go by taking the tour. Spyware, virus, trojan, fake security or privacy alerts? Read the malware cleaning guide. Want to reply to a topic, start a new one, or remove the advertising? Join today (always free).
      
 
Reply to this topicStart new topic
Lexbce Server, conflict
dc56
post May 29 2005, 01:43 PM
Post #1


New Member
*
Posts: 5
OS: XP



My computer a Dell 4600, was purchased last August slong with a Dell printer A920. Recently, I have not been able to connect to the internet without the computer freezing. Ctrl, Alt, Del has no impact. It must be rebooted.

I determined, through the process of elimination, that Lexbce Server shown in services via msconfig, must be disabled to allow me to connect.

If I disable it, I no longer have any printers, not the A920, fax, image writer, etc.

I've uninstalled the printer, restarted in safe mode and attempted to delete the offending file. Didn't work.

Any suggestions are appreciated. I've spent way too much time on this already!
Go to the top of the page
 
+Quote Post
Keith
post May 29 2005, 02:25 PM
Post #2


Philanthropical Physiognomist
Group Icon
Posts: 20,563
OS: Windows 98 Second Edition - XP Professional - Office 2003 Professional - XP Home Edition - Office XP Professional - Vista Home Premium - Vista Ultimate



Try here

http://support.microsoft.com/default.aspx?...kb;en-us;155516

http://support.microsoft.com/default.aspx?...kb;en-us;319127

LexBce Server LEXBCES.EXE Y This is installed by Lexmark printers, and some Dell printers which are made by Lexmark, to configure the onboard network print server. Disabling this service will make it so that print spooler service will no longer startup, which effectively disables printing on your computer.

This can be fixed by removing the LexBceS dependency. To remove the dependency you should use the following command and start the print spooler service:

sc config spooler depend= RPCSS

Note: Notice the space after depend= . This is necessary.
Go to the top of the page
 
+Quote Post
dc56
post May 29 2005, 02:43 PM
Post #3


New Member
*
Posts: 5
OS: XP



I'm not sure I understand when or where I should enter that command. Could you provide some more detail?

Thank you!
Go to the top of the page
 
+Quote Post
Keith
post May 29 2005, 02:50 PM
Post #4


Philanthropical Physiognomist
Group Icon
Posts: 20,563
OS: Windows 98 Second Edition - XP Professional - Office 2003 Professional - XP Home Edition - Office XP Professional - Vista Home Premium - Vista Ultimate



Click start then all programmes, accessories, command prompt, type it then press enter you should get SUCCESS
Go to the top of the page
 
+Quote Post
dc56
post May 29 2005, 06:29 PM
Post #5


New Member
*
Posts: 5
OS: XP



Thank you! I'll give it a try
Go to the top of the page
 
+Quote Post
dc56
post May 29 2005, 07:28 PM
Post #6


New Member
*
Posts: 5
OS: XP



I tried your suggestion Keith and now, with the Lexbce Server disabled I can , of course, connect and when I look into the control panel, I can now see the printers but nothing will print citing failed communication.
Go to the top of the page
 
+Quote Post
Keith
post May 29 2005, 07:58 PM
Post #7


Philanthropical Physiognomist
Group Icon
Posts: 20,563
OS: Windows 98 Second Edition - XP Professional - Office 2003 Professional - XP Home Edition - Office XP Professional - Vista Home Premium - Vista Ultimate



Click start then run then type services.msc then press enter, look for print spooler to check it is set to automatic, if not, double click it then change start up type to automatic, click start then apply. Then check remote procedure call, top of two, check this is set to automatic, if not, change same way.

Do you get any other error message
Go to the top of the page
 
+Quote Post
dc56
post May 30 2005, 06:05 PM
Post #8


New Member
*
Posts: 5
OS: XP



Both of those services were already set to automatic and had started.
I have not seen any other error messages other than the one saying that I can't print due to not communicating.
Go to the top of the page
 
+Quote Post
Keith
post May 31 2005, 12:07 AM
Post #9


Philanthropical Physiognomist
Group Icon
Posts: 20,563
OS: Windows 98 Second Edition - XP Professional - Office 2003 Professional - XP Home Edition - Office XP Professional - Vista Home Premium - Vista Ultimate



Dell say, hold the printer power button for 10 seconds to reset, make sure the printers are not on the same port, re-install the software.

If you re-install the software, run tune up between uninstall and reinstall

http://www.tune-up.com

Run disc clean up then registry clean up
Go to the top of the page
 
+Quote Post
affordable
post Jun 1 2005, 04:13 PM
Post #10


New Member
*
Posts: 9
OS: windows xp



i'm having a very similar prob so i tried the sc config spooler depend= RPCSS
well it worked my spooler works now but still no printer. if you figure it out let me know plzzz!!
Go to the top of the page
 
+Quote Post
Rabid™
post Jun 18 2005, 04:05 PM
Post #11


New Member
*
Posts: 1
OS: xp pro



you need to start the remote procedure call locator service
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 

Collapse

> Similar Topics

    Topic Title Replies / Views Topic Information
No New Posts   1 / 2,671 21st March 2005 - 08:27 PM
steveraygriffin started - last by ukbiker
No New Posts   3 / 178 22nd November 2008 - 04:21 PM
Tjvelcro started - last by Tjvelcro
No New Posts   1 / 46 29th November 2008 - 03:20 PM
Diego8 started - last by Diego8
No New Posts   0 / 7 Yesterday, 07:16 PM
thilton19 started - last by thilton19

RSS Time is now: 3rd December 2008 - 12:46 AM
Advertisements do not imply our endorsement of that product or service. The forum is run by volunteers who donate their time and expertise. We make every attempt to ensure that the help and advice posted is accurate and will not cause harm to your computer. However, we do not guarantee that they are accurate and they are to be used at your own risk.