EventID.Net GFI
 
home| search| login| forums| it admin tasks| tcp/ip ports| documents | contributors| about us 
 
Event ID/Source search
Event ID: Event Source:
Keyword search
Example: Windows cannot unload your registry file
 
Event ID: 2 Source: ParVdm
Source: ParVdm
Type: Error
Description:
Unable to get device object pointer for port object.
English: Request a translation of the event description in plain English.
Comments:
Seagate665
Just switch LPT1 and LPT3 so the PCI Parallel port have assignet LPT1 and onboard parallel port LPT3, that helped in my case.
Click if the comment is good! x 9

EventID.Net
As per Microsoft: "ParVdm depends on previous naming conventions for identifying parallel ports, and in this case it cannot find a port with a name that matches". See MSW2KDB for additional information on this event.
Click if the comment is good! x 3

Anonymous
Some ASPI driver I installed mapped the only ECP Printer Port on the machine from LPT1 to LPT3 causing this error. Resetting it back to LPT1 solved the problem.
Click if the comment is good! x 2

Anonymous
I had this problem on a W2K workstation. In the device manager a 2nd parallel port appeared which wasn’t physical present on the machine. After I’ve uninstalled the second port the problem disappeared.
Click if the comment is good! x 2

Jochen Meissner
In my case the same event was as well due to a second parallel port card. I changed the LPT number from 3 to 2. The error message did not show up again.
Click if the comment is good! x 4

Why bother deciphering Event logs when GFI EventsManager can do everything for you? Free trial here!

Anonymous
I had this problem on WinXP Pro SP1 where I have an extra parallel port (PCI-card). In the Device Manager (tab Port settings) I unchecked "Never use an interrupt", and checked "Use any interrupt assigned to the port". After that, the error message disappeared.
Click if the comment is good! x 6

Isaac Koch
This error was noted on a Windows Server 2003, Enterprise Edition machine that had an add-in parallel port (PCI) installed. The operating system detected and installed a driver for this device, but after installing the manufacturer-supplied driver, the Parvdm service started, although it displayed this error multiple times in the event log before starting. Apparently one error message was generated for each port object, e.g. printers, parallel ports. Previously the Parvdm service would not start. After restarting Windows, the Parvdm service started with no errors.
Click if the comment is good! x 2
Private comment: Subscribers only. See example of private comment
Links: MSW2KDB
Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue - More links...
Feedback: Send comments or solutions - Notify me when updated

Printer friendly
  • Subscription
    SubscribeSubscribe to EventID.Net now!
    Already a subscriber? Login here
GFI

 





 

 

Recommend Us


  • Quick Tip
    Connect to EventID.Net directly from the Microsoft Event Viewer!
    Instructions

  • Newest article
    How to Maintain and Monitor a Microsoft SharePoint Server
    Read

Customer services

Contact us
Support
Terms of Use

Help & FAQ

Sales FAQ
EventID.Net FAQ

Articles

Managing logs
Recommended books

Links

Downloads
Firegen Log Analyzers
Link to us


© Copyright 2001 - 2012 EventID.Net