Event ID: 2 Source: ParVdm

EventID.Net

EvLog Event Analyzer

Monitor unlimited number of servers
Filter log events
Create email and web-based reports

EventID.Net Subscription

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 2 Source: ParVdm

Source

ParVdm

Level

Error

Description

Unable to get device object pointer for port object.

English

This information is only available to subscribers. An example of English, please!

Concepts to understand

What is an object?

Comments

GNT Norway

Go into device manager and change LPT3 to be called LPT2 instead, that took care of our event error.

Seagate665

Just switch LPT1 and LPT3 so the PCI Parallel port have assignet LPT1 and onboard parallel port LPT3, that helped in my case.

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.

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.

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.

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.

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.

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.

Private comment

Subscribers only. See an example of private comment

Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...

Custom search for *****: Google - Bing - Microsoft - Yahoo

Feedback

Send comments or solutions - Notify me when updated

Printer friendly

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net.

Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.