Discussion Locked

transport "ddetrdll"failed to initialize

0 helpful
14 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have an entry in my event log, that I have no clue what it originates from, I'm sure something simple and stupid (always is), anyone else ever had
Source:Win32rap
Event 9
Failed to initialize transport "ddetrdll"

and what I can do to stop it?
Thanks in advance

14 replies

by syscokid

This is all I could find on the subject:

From
http://www.intel.cl/support/motherboards/server/isc/err23.htm

The win32rap service reports several error messages if NetWare* services are not installed.

Problem: If ISC is installed on a console or server without installing the NetWare services, then win32rap may report the following error messages in the application event log:

"failed to initialize transport 'ddetrdll'"
"failed to initialize transport 'ipx'
"initializing winsock for ipx failed (winsock error 0x0000273f)"
Implication: These messages simply indicate that win32rap attempted to start the NetWare services. If you are using tcp/ip for server communication then they are not a concern.

Workaround: You can ignore the error if your network only supports tcp/ip.

Status: Intel is not investigating this erratum.

(Sometimes when I cut and paste URL's it looks ok to me but once the answer is posted, an extraneous space will have crept in. Make sure you delete any extraneous spaces if you paste that url in your browser).

by michael roark - ccna/da mcp 3csa

I realize that's what it is, but it stops me from running winproxy as a service. Winproxy starts up, then the error, then Winproxy stops responding, and the serial port gets locked up, and the server has to be rebooted again. I need to find some wayto take off the stupid ICS program, that doesn't really help me anyways.
Any ideas?

by james_randy

Greetings Michael,

A single occurrence of "Event 9" may not indicate a problem, but repetitive occurrences may warrant investigation. When you are troubleshooting these events, bear in mind that these events are issued by the
device driver for the attached storage devices. These events are not caused by
or issued from the cluster software. The events may indicate the need to examine
or troubleshoot attached storage devices.

Event ID: 9
Source: [scsi miniport driver]
Description: The device,
\Device\ScsiPort1, did not respond
within the timeout period.

Event ID 9 indicates that an I/O time-out has occurred within the storage system,
as detected from the driver for the controller. This time-out does not involve
the cluster software in any way. The I/O request made to the device was not
completed within a reasonable amount of time. When the I/O request expires
(times out), the driver resets the SCSI bus. Although this could indicate other
problems, this couldalso be caused in some configurations by powering on or off
devices on the shared bus, if the bus is differential. Time-out events could
indicate cabling, termination, or SCSI hardware configuration problems.

Source: MS KB Q259237

You're welcome,

jr

by james_randy

OR:

To improve the ability to troubleshoot SNA Server Event 9 (subcode 1117) and
Event 12 errors, these events have been enhanced to include the following
additional information:

- Client Domain

- Client User (name)

- LU name (3270 LU)

- FMI Sense Code

Event ID: 9
Source: SNA Server
Description:
() A protocol error occurred due
to a message sent by a 3270 emulator or
link service

EXPLANATION
A protocol error occurred due to a message
sent by a 3270 emulator or link service.

SUBCODE INFORMATION
X'1117' A 3270 emulator used by the
following user caused an error, though the
user's 3270 session was not interrupted:

Client Domain:
Client User:
LU name:
FMI Sense Code:

Source: MS KB Q181121

by james_randy

OR:
There are many ways a SCSI controller can fail. Typical signs of imminent SCSI
controller failure can be seen by monitoring the System Event Log for Event ID: 11 and Event ID: 9. For additional information on these events, please see the following articles in the Microsoft Knowledge Base:
ARTICLE-ID: Q153128
TITLE : Event IDs 9 and 11: SCSI Controller/Device Errors

ARTICLE-ID: Q154690
TITLE : How to Troubleshoot Event 9

When you replace the failed SCSI controller, make sure the new controller has the same firmware as the working controller in the other node. Follow these steps to replace the failed or failing SCSI controller:

1. Power off the node with failed or failing adapter. If possible, manually move all groupsto another node using Cluster Administrator.

2. Verify that all groups and resources are online on the functioning node.

3. Remove and replace SCSI controller in failed node.

4. Power on the node and log on normally.

5. Check the event log for any unusual errors.

6. Start Cluster Administrator and verify groups and resources are online and have failed back if so configured.

NOTE: After replacing the controller, set the SCSI ID for the new controller to
be the same as the old one. Microsoft Cluster Server should start and function
normally. If your configuration does not use SCSI Y cables or specialized cables, you may have to shut down both nodes. SCSI Y cables allow termination of the bus regardless of connectionto the controller. With standard SCSI cables, termination may be lost when you disconnect the faulty controller.

You may have successfully repaired the problem if:

There are no unusual event messages in the event viewer.

Cluster Administrator starts and allows you to view the cluster.

Groups and resources may be moved successfully to the node with the new

Source: MS KB Q175275

by james_randy

OR:

Status:

Intel is investigating the possibility of fixing this erratum. The win32rap service reports several error messages if NetWare* services are not installed.

Problem:
If ISC is installed on a console or server without installing the NetWare services, then win32rap may report the following error messages in the application event log:

"failed to initialize transport 'ddetrdll' "
"failed to initialize transport 'ipx'
"initializing winsock for ipx failed (winsock error 0x0000273f)"
Implication: These messages simply indicate that win32rap attempted to start the NetWare services. If you are using tcp/ip for server communication then they are not a concern.

Workaround:
You can ignore the error if your network only supports tcp/ip.

by james_randy

OR:

In almost all cases, these messages are being posted due to hardware problems with either the controller or, more likely, a device that is attached to the controller in question. The hardware problems can be associated with poor cabling, incorrect termination or transfer rate settings, lazy or slow device responses to relinquish the SCSI bus, a faulty device or, in very rare cases, a poorly written device driver.

MORE INFORMATION
The following are some troubleshooting tips to helpdiagnose and pinpoint the problem:

Read the SCSI controller manufacturer's technical manual to determine the termination requirements. Many modern SCSI controllers require active terminators (at least one of the devices on the bus must provide termination power). Proper termination involves both a terminator (resistor) and a device that supplies a signal to the bus for termination power. The SCSI-2 standard specifies that a controller (initiator) must supply termination power. Therefore, any controller that claims to be SCSI-2 compatible probably does supply termination power, but you should check if you are unsure. Also, many devices, especially drives, give you the option of providing termination power; if you have a jumper on the drive that reads Trmpwr, you should enable this jumper.

If both internal and external SCSI devices are attached, make sure the last device on each SCSI chain is terminated, and that intermediary devices are not.

If only a single SCSI chain is used (either all internal or external), ensure the last device of the SCSI chain is terminated and the SCSI controller itself is terminated. This is usually a BIOS setting.

Check for loose or poor quality SCSI cabling. When you have a long chain of cables with mixed internal and external cabling, you run the risk of degrading the signal. Even though the SCSI specification may specify a long distance, the specification assume

by james_randy

OR:

In almost all cases, these messages are being posted due to hardware problems with either the controller or, more likely, a device that is attached to the controller in question. The hardware problems can be associated with poor cabling, incorrect termination or transfer rate settings, lazy or slow device responses to relinquish the SCSI bus, a faulty device or, in very rare cases, a poorly written device driver.

MORE INFORMATION
The following are some troubleshooting tips to helpdiagnose and pinpoint the problem:

Read the SCSI controller manufacturer's technical manual to determine the termination requirements. Many modern SCSI controllers require active terminators (at least one of the devices on the bus must provide termination power). Proper termination involves both a terminator (resistor) and a device that supplies a signal to the bus for termination power. The SCSI-2 standard specifies that a controller (initiator) must supply termination power. Therefore, any controller that claims to be SCSI-2 compatible probably does supply termination power, but you should check if you are unsure. Also, many devices, especially drives, give you the option of providing termination power; if you have a jumper on the drive that reads Trmpwr, you should enable this jumper.

If both internal and external SCSI devices are attached, make sure the last device on each SCSI chain is terminated, and that intermediary devices are not.

If only a single SCSI chain is used (either all internal or external), ensure the last device of the SCSI chain is terminated and the SCSI controller itself is terminated. This is usually a BIOS setting.

Check for loose or poor quality SCSI cabling. When you have a long chain of cables with mixed internal and external cabling, you run the risk of degrading the signal. Even though the SCSI specification may specify a long distance, the specification assume

by james_randy

Conclusion:

It sounds like there may be a problem with an attached SCSI device, but one that you could certainly ignore if you don't notice any performance issues.

However, if none of that helps, try calling your local super-hero.

Regards,

jr

by michael roark - ccna/da mcp 3csa

Intel does not have any support for this ISC program, there is no uninstall program, and I'm not about to attack our proxy server's registry to find entries I'm not familiar with. We are getting a new server next week, and I will just keep in mind not to install and Intel software from now on. You would think they would know how to write software, wouldn't you.
There's no way I would ever put an IPX network on our LAN here, and I can't take the error messages popping up interupting other processes and services trying to start.
After we get another server, I'll just reformat everything and start afresh. Just pass it on not to install Intel Server Control.

This discussion is closed to new replies.