[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1629
  • Last Modified:

How can I find/fix the true error

I have an error coming up on one of my Server 2003 Terminal servers regarding an Image type printer that I cannot track down.
The printer works fine for all users as best I can tell but this error is constantly filling the event log.

The description for Event ID ( 1 ) in Source ( Application ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: DrvStartPage : OpenPrinter ImageRight Printer, failed with dwError=5

I have also attached a screenshot of the event.

Any thoughts?
TS-Event.JPG
0
Everlastinggrin
Asked:
Everlastinggrin
  • 2
  • 2
1 Solution
 
Scott CSenior Systems EnginerCommented:
This article shows how to use the AUXSOURCE to try to make sense out of the error:

http://support.microsoft.com/kb/312216

This might give you something to get you going in the right direction.
0
 
EverlastinggrinAuthor Commented:
Thank you for the reply ScottCha.
I have tried that every way that MS says I can to no avail. (no extra info is presented)

any other thoughts/ideas?
0
 
Scott CSenior Systems EnginerCommented:
Try reading through this thread.  It looks like the person had a similar error message.

It looks like this person had a .NET issue.

http://forums.techguy.org/windows-xp/680624-solved-installer-register-problems.html

Unfortunatley I've never personally come across this before the the information on the web is skimpy at best.
0
 
livanescuCommented:
dwError = 5 'ERROR_ACCESS_DENIED"...
could it be something like this?
0
 
EverlastinggrinAuthor Commented:
Thank you for the help all.
I followed the threads starting at the one ScottCha presented.

Unfortunately, I am not sure what finally fixed the issue for me to report back on. I think it was an old GPO left on the domain that I inherited.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now