Ntbackup problem on 2003 running on esxi

Global description

After virtualisation of a 2003 SBS server we have the following error on the tape backup

Het apparaat heeft een fout gerapporteerd bij deze aanvraag: gegevens naar medium schrijven. Fout: Ongeldige opdracht. er is mogelijk een hardware- of mediumprobleem opgetreden. Controleer het logbestand voor systeemgebeurtenissen voor relevante fouten.

This is the dutch error for the following English error

Error: The device reported an error on a request to write data to media.
Error reported: Invalid command.
There may be a hardware or media problem.
Please check the system event log for relevant failures.

This error is popup as soon as the tape is being written.

The backup log looks like something like this

========================================================
Error: The device reported an error on a request to write data to media.
Error reported: Invalid command.
There may be a hardware or media problem.
Please check the system event log for relevant failures.
The operation was ended.

Error: C: is not a valid drive, or you do not have access.

The operation was ended.

———————-

The operation did not successfully complete.

———————-
=========================================================

How did we narrow down this problem?

First we created a virtual XP machine and attach the tapedive to this machine
This test results in a working tapebackup. So we where 100% sure that this problem was not related to the device, or the tape

Then we re attach the tapedevice back to the 2003 server, and the problem was returning

Somehow the disc can’t be accessed when the tapedevice is starting

How did we solve this problem?

We created a extra scsi adapter in the ESXI environment. First we could not find a way to insert a extra scsi adapter, but after some search we find out to simply select device (1:0) on the tapedevice, and a 2e scsi adapter will appear on the ESXI config.
I changed the device to a buslogic parallel, so i would still know the difference between the virtual scsi controller for the discs, and for the tapedevice

After this change the problem was solved.

 

Service not started message on console

You get this error on the server console, but you cant find any services who is failing to start.

Ten minste een service is bij het starten van het systeem niet gestart. Raadpleeg het logboek voor informatie.

The English error is:


At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details

You will find this error on you system log


Application Popup system-id 26

The way we solved this:

There are 2 type of services
You have the normal service, and you have the devicedrivers who are also some kind of service

If you download serviwin from nirsoft you can see all the device services who are not running
http://www.nirsoft.net/utils/serviwin.html

Here you have a view how to find the responsible service

I did sort the list on startup type, and you see the service streamdispatcher not running, but because the startup type is automatic, its the cause of the error.
after some research this failing device was the result of a leftover rootkit. The rootkit itself was intercepted by the virus scan, but the service was still present.

Of course its possible that in other situations, its a other service
A common service who can fail is the parport service. If your hardware don’t have a parallel port, this service will fail, because the default startuptype is automatic

How to delete/control a deviceservice from the commandline

In the above situation you can use the following command

how to stop a service
C:\>sc stop “StreamDispatcher”
[SC] ControlService MISLUKT 1062:

De service is niet gestart.

how to change the staruptype
C:\>sc config “StreamDispatcher” start= disabled
[SC] ChangeServiceConfig VOLTOOID

how to delete a service
C:\>sc delete “StreamDispatcher”
[SC] DeleteService VOLTOOID

After changing the serviceconfig the problem is solved