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. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
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?
Go into device manager and change LPT3 to be called LPT2 instead, that took care of our event error.
Just switch LPT1 and LPT3 so the PCI Parallel port have assignet LPT1 and onboard parallel port LPT3, that helped in my case.
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.
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.
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.
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.
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.
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 example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
|Custom search for *****: Google - Bing - Microsoft - Yahoo|
Send comments or solutions
- Notify me when updated