The server service was unable to map error code 1722. - Windows 20

Hi

I have the above error in my event logs on one of our servers, all the
information i can find relates to hp webjetadmin issues, the puzzling thing
is the server is a file server and has never been a print server or had hp
webjetadmin installed. It does have hp insight manager tho ??

Im scratching my head with this one

any ideas ?

Thanks
Matt

You post is lacking much info. When did this start? What was change
recently? Check Event Viewer for errors. When you view the logged events in
Event Viewer (double-click them in the right-hand pane) in the upper right
corner, third button down is a copy to clipboard, then you can paste in the
body of a reply message.

Please do so for each of the different System Log events (that are a Type:
'Error' or 'Warning') since last boot so we can see all of the event detail.

Also check Device Manager for error codes and or non-starting devices.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Mattc" wrote:
| Anyone ?

Thanks Dave

Event Type: Error
Event Source: Server
Event Category: None
Event ID: 2510
Date: 11/07/2006
Time: 6:11:34 a.m.
User: N/A
Computer: DATA2K
Description:
The server service was unable to map error code 1722.

the problem tarted on the 11/07/06 - there have been no changes to the
system, nothing in device manager is showing an error. , there are no other
alerts or warnings i can find in the event logs . im scratching my head

Thanks for your help

Matt

One of these articles may help.

http://support.microsoft.com/default...b;en-us;888206
http://support.microsoft.com/default...b;en-us;822219

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Mattc" wrote:
| Thanks Dave
|
| Event Type: Error
| Event Source: Server
| Event Category: None
| Event ID: 2510
| Date: 11/07/2006
| Time: 6:11:34 a.m.
| User: N/A
| Computer: DATA2K
| Description:
| The server service was unable to map error code 1722.
|
| the problem tarted on the 11/07/06 - there have been no changes to the
| system, nothing in device manager is showing an error. , there are no
other
| alerts or warnings i can find in the event logs . im scratching my head
|
| Thanks for your help
|
| Matt
|

Thanks Dave

Funny thing is the print spooler does not stop like reffered to in the first
article, and the second article referes to loss of performance, but we are
not experiencing this . I will check to make sure RPC is running as 1722
seems to point to RPC being unavailable

Ok.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Mattc" wrote:
| Thanks Dave
|
| Funny thing is the print spooler does not stop like reffered to in the
first
| article, and the second article referes to loss of performance, but we are
| not experiencing this . I will check to make sure RPC is running as 1722
| seems to point to RPC being unavailable
|

Rpc locator was stopped ! Now to sit back and watch the logs to see if
starting it resolved the problem

'Remote Procedure Call (RPC)' should be set to 'Automatic' startup type and
should indicate 'Started'

'Remote Procedure Call (RPC) Locator' should be set to 'Manual' startup type
and will only start when needed


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Mattc" wrote:
| Rpc locator was stopped ! Now to sit back and watch the logs to see if
| starting it resolved the problem

well so far its been three days since this error has appeared..... so fingers
crossed !! :)

Good to hear.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Mattc" wrote:
| well so far its been three days since this error has appeared..... so
fingers
| crossed !! :)