ndprot62.sys not loading while running Ndis Test 6.5(WLK 1.5) on windows server 2008 R2

Ashish_Purkar · October 25, 2010, 7:19am

*Create binding on the test devices.** *

ProtocolManager::LoadDriver

Driver Name: ndprot62
Driver Path: D:\mak\ndistest.net\bin\protocol\
*Test terminated abnormally with an Exception
NDISTest.NDISTestCore.TestServices.NDISOperationException*
88888 Test terminated abnormally with an Exception
NDISTest.NDISTestCore.TestServices.NDISOperationException

*Exception details*

Type

NDISTest.NDISTestCore.TestServices.NDISOperationException

Message

Unable to start ndprot62 driver serviceNDIS_STATUS (0x00000241)

Source

NDISTest.ScriptLibrary

Stack Trace

at NDISTest.NDISTestCore.TestServices.ProtocolManager.LoadDriver()
at
NDISTest.NDISTestCore.TestServices.ProtocolHelper.GetProtocolManager(IAdapter
adapter, UInt32 protocolType)
at NDISTest.NDISTestCore.TestServices.ProtocolHelper.Bind(IAdapter adapter,
String friendlyProtocolName, OpenType openType, String friendlyOpenName,
UInt32 openSubType, UInt32 bindingMechanism, UInt32* frameTypeArray, UInt32
frameTypeArraySize, UInt32 protocolType, Boolean bPortsEnabled, UInt32
protocolFlags)
at NDISTest.NDISTestCore.TestServices.ProtocolHelper.Bind(IAdapter adapter,
String friendlyProtocolName, OpenType openType, String friendlyOpenName,
UInt32 openSubType, UInt32 bindingMechanism, UInt32* frameTypeArray, UInt32
frameTypeArraySize, UInt32 protocolType, Boolean bPortsEnabled)
at NDISTest.NDISTestCore.TestServices.ProtocolHelper.Bind(IAdapter adapter,
String friendlyProtocolName, OpenType openType, String friendlyOpenName)
at Test_OffloadGSO.Start()
at NDISTest.NDISTestCore.TestServices.TestBase.StartTest()

While runnig NDIS test 6.5 manually(without DTM), I am seeing above problem
on windows server 2008 R2.

In the event logs, I see

The ndprot62 service failed to start due to the following error:
Windows cannot verify the digital signature for this file. A recent hardware
or software change might have installed a file that is signed incorrectly or
damaged, or that might be malicious software from an unknown source.

In the debugger, I see following error:

ClientProtocolManager::CreateRemoteProtocolManager: Failed while sending
command to create remote Protocol Manager
Failed to create remote protocol manager

. Error: 0000001F
Test terminated abnormally with an Exception
NDISTest.NDISTestCore.TestServices.NDISOperationException

Any ideas?

Thanks,
Ashish

Paul_Durrant · October 25, 2010, 8:19am

Enable test signing on your box.

On 25 October 2010 12:18, Ashish Purkar wrote:

> Create binding on the test devices.*
>
> ProtocolManager::LoadDriver
> - Driver Name: ndprot62
> - Driver Path: D:\mak\ndistest.net\bin\protocol<br>> Test terminated abnormally with an Exception
> NDISTest.NDISTestCore.TestServices.NDISOperationException
> 88888 Test terminated abnormally with an Exception
> NDISTest.NDISTestCore.TestServices.NDISOperationException
>
> Exception details
>
> Type
>
> NDISTest.NDISTestCore.TestServices.NDISOperationException
>
> Message
>
> Unable to start ndprot62 driver serviceNDIS_STATUS (0x00000241)
>
> Source
>
> NDISTest.ScriptLibrary
>
> Stack Trace
>
> at NDISTest.NDISTestCore.TestServices.ProtocolManager.LoadDriver()
> at
> NDISTest.NDISTestCore.TestServices.ProtocolHelper.GetProtocolManager(IAdapter
> adapter, UInt32 protocolType)
> at NDISTest.NDISTestCore.TestServices.ProtocolHelper.Bind(IAdapter adapter,
> String friendlyProtocolName, OpenType openType, String friendlyOpenName,
> UInt32 openSubType, UInt32 bindingMechanism, UInt32 frameTypeArray, UInt32
> frameTypeArraySize, UInt32 protocolType, Boolean bPortsEnabled, UInt32
> protocolFlags)
> at NDISTest.NDISTestCore.TestServices.ProtocolHelper.Bind(IAdapter adapter,
> String friendlyProtocolName, OpenType openType, String friendlyOpenName,
> UInt32 openSubType, UInt32 bindingMechanism, UInt32* frameTypeArray, UInt32
> frameTypeArraySize, UInt32 protocolType, Boolean bPortsEnabled)
> at NDISTest.NDISTestCore.TestServices.ProtocolHelper.Bind(IAdapter adapter,
> String friendlyProtocolName, OpenType openType, String friendlyOpenName)
> at Test_OffloadGSO.Start()
> at NDISTest.NDISTestCore.TestServices.TestBase.StartTest()
>
>
> While runnig NDIS test 6.5 manually(without DTM), I am seeing above problem
> on windows server 2008 R2.
>
> In the event logs, I see
>
> The ndprot62 service failed to start due to the following error:
> Windows cannot verify the digital signature for this file. A recent
> hardware or software change might have installed a file that is signed
> incorrectly or damaged, or that might be malicious software from an unknown
> source.
>
> In the debugger, I see following error:
>
> ClientProtocolManager::CreateRemoteProtocolManager: Failed while sending
> command to create remote Protocol Manager
> Failed to create remote protocol manager
>
> . Error: 0000001F
> Test terminated abnormally with an Exception
> NDISTest.NDISTestCore.TestServices.NDISOperationException
>
> Any ideas?
>
> Thanks,
> Ashish
> — NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and
> other seminars visit: http://www.osr.com/seminars To unsubscribe, visit
> the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer

–
Paul Durrant
http://www.linkedin.com/in/pdurrant

Ashish_Purkar · October 25, 2010, 10:49am

Hi Paul,

Even after enabling testsigning using following commands, I see same
failure.

bcdedit -set testsigning ON
bcdedit -set loadoptions DDISABLE_INTERGRITY_CHECKS

Do I have do anything more to enable testsigning like gpedit.msc?

Thanks,
Ashish

On Mon, Oct 25, 2010 at 5:48 PM, Paul Durrant wrote:

> Enable test signing on your box.
>
> On 25 October 2010 12:18, Ashish Purkar wrote:
>
>> Create binding on the test devices.*
>>
>> ProtocolManager::LoadDriver
>> - Driver Name: ndprot62
>> - Driver Path: D:\mak\ndistest.net\bin\protocol<br>>> Test terminated abnormally with an Exception
>> NDISTest.NDISTestCore.TestServices.NDISOperationException
>> 88888 Test terminated abnormally with an Exception
>> NDISTest.NDISTestCore.TestServices.NDISOperationException
>>
>> Exception details
>>
>> Type
>>
>> NDISTest.NDISTestCore.TestServices.NDISOperationException
>>
>> Message
>>
>> Unable to start ndprot62 driver serviceNDIS_STATUS (0x00000241)
>>
>> Source
>>
>> NDISTest.ScriptLibrary
>>
>> Stack Trace
>>
>> at NDISTest.NDISTestCore.TestServices.ProtocolManager.LoadDriver()
>> at
>> NDISTest.NDISTestCore.TestServices.ProtocolHelper.GetProtocolManager(IAdapter
>> adapter, UInt32 protocolType)
>> at NDISTest.NDISTestCore.TestServices.ProtocolHelper.Bind(IAdapter
>> adapter, String friendlyProtocolName, OpenType openType, String
>> friendlyOpenName, UInt32 openSubType, UInt32 bindingMechanism, UInt32
>> frameTypeArray, UInt32 frameTypeArraySize, UInt32 protocolType, Boolean
>> bPortsEnabled, UInt32 protocolFlags)
>> at NDISTest.NDISTestCore.TestServices.ProtocolHelper.Bind(IAdapter
>> adapter, String friendlyProtocolName, OpenType openType, String
>> friendlyOpenName, UInt32 openSubType, UInt32 bindingMechanism, UInt32*
>> frameTypeArray, UInt32 frameTypeArraySize, UInt32 protocolType, Boolean
>> bPortsEnabled)
>> at NDISTest.NDISTestCore.TestServices.ProtocolHelper.Bind(IAdapter
>> adapter, String friendlyProtocolName, OpenType openType, String
>> friendlyOpenName)
>> at Test_OffloadGSO.Start()
>> at NDISTest.NDISTestCore.TestServices.TestBase.StartTest()
>>
>>
>> While runnig NDIS test 6.5 manually(without DTM), I am seeing above
>> problem on windows server 2008 R2.
>>
>> In the event logs, I see
>>
>> The ndprot62 service failed to start due to the following error:
>> Windows cannot verify the digital signature for this file. A recent
>> hardware or software change might have installed a file that is signed
>> incorrectly or damaged, or that might be malicious software from an unknown
>> source.
>>
>> In the debugger, I see following error:
>>
>> ClientProtocolManager::CreateRemoteProtocolManager: Failed while sending
>> command to create remote Protocol Manager
>> Failed to create remote protocol manager
>>
>> . Error: 0000001F
>> Test terminated abnormally with an Exception
>> NDISTest.NDISTestCore.TestServices.NDISOperationException
>>
>> Any ideas?
>>
>> Thanks,
>> Ashish
>> — NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and
>> other seminars visit: http://www.osr.com/seminars To unsubscribe, visit
>> the List Server section of OSR Online at
>> http://www.osronline.com/page.cfm?name=ListServer
>
>
>
>
> –
> Paul Durrant
> http://www.linkedin.com/in/pdurrant
> — NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and
> other seminars visit: http://www.osr.com/seminars To unsubscribe, visit
> the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer

Paul_Durrant · October 25, 2010, 12:41pm

Enabling test signing was always enough to make things work for me.

On 25 October 2010 15:49, Ashish Purkar wrote:

> Hi Paul,
>
> Even after enabling testsigning using following commands, I see same
> failure.
>
> bcdedit -set testsigning ON
> bcdedit -set loadoptions DDISABLE_INTERGRITY_CHECKS
>
> Do I have do anything more to enable testsigning like gpedit.msc?
>
> Thanks,
> Ashish
>
> On Mon, Oct 25, 2010 at 5:48 PM, Paul Durrant wrote:
>
>> Enable test signing on your box.
>>
>> On 25 October 2010 12:18, Ashish Purkar wrote:
>>
>>> Create binding on the test devices.*
>>>
>>> ProtocolManager::LoadDriver
>>> - Driver Name: ndprot62
>>> - Driver Path: D:\mak\ndistest.net\bin\protocol<br>>>> Test terminated abnormally with an Exception
>>> NDISTest.NDISTestCore.TestServices.NDISOperationException
>>> 88888 Test terminated abnormally with an Exception
>>> NDISTest.NDISTestCore.TestServices.NDISOperationException
>>>
>>> Exception details
>>>
>>> Type
>>>
>>> NDISTest.NDISTestCore.TestServices.NDISOperationException
>>>
>>> Message
>>>
>>> Unable to start ndprot62 driver serviceNDIS_STATUS (0x00000241)
>>>
>>> Source
>>>
>>> NDISTest.ScriptLibrary
>>>
>>> Stack Trace
>>>
>>> at NDISTest.NDISTestCore.TestServices.ProtocolManager.LoadDriver()
>>> at
>>> NDISTest.NDISTestCore.TestServices.ProtocolHelper.GetProtocolManager(IAdapter
>>> adapter, UInt32 protocolType)
>>> at NDISTest.NDISTestCore.TestServices.ProtocolHelper.Bind(IAdapter
>>> adapter, String friendlyProtocolName, OpenType openType, String
>>> friendlyOpenName, UInt32 openSubType, UInt32 bindingMechanism, UInt32
>>> frameTypeArray, UInt32 frameTypeArraySize, UInt32 protocolType, Boolean
>>> bPortsEnabled, UInt32 protocolFlags)
>>> at NDISTest.NDISTestCore.TestServices.ProtocolHelper.Bind(IAdapter
>>> adapter, String friendlyProtocolName, OpenType openType, String
>>> friendlyOpenName, UInt32 openSubType, UInt32 bindingMechanism, UInt32*
>>> frameTypeArray, UInt32 frameTypeArraySize, UInt32 protocolType, Boolean
>>> bPortsEnabled)
>>> at NDISTest.NDISTestCore.TestServices.ProtocolHelper.Bind(IAdapter
>>> adapter, String friendlyProtocolName, OpenType openType, String
>>> friendlyOpenName)
>>> at Test_OffloadGSO.Start()
>>> at NDISTest.NDISTestCore.TestServices.TestBase.StartTest()
>>>
>>>
>>> While runnig NDIS test 6.5 manually(without DTM), I am seeing above
>>> problem on windows server 2008 R2.
>>>
>>> In the event logs, I see
>>>
>>> The ndprot62 service failed to start due to the following error:
>>> Windows cannot verify the digital signature for this file. A recent
>>> hardware or software change might have installed a file that is signed
>>> incorrectly or damaged, or that might be malicious software from an unknown
>>> source.
>>>
>>> In the debugger, I see following error:
>>>
>>> ClientProtocolManager::CreateRemoteProtocolManager: Failed while sending
>>> command to create remote Protocol Manager
>>> Failed to create remote protocol manager
>>>
>>> . Error: 0000001F
>>> Test terminated abnormally with an Exception
>>> NDISTest.NDISTestCore.TestServices.NDISOperationException
>>>
>>> Any ideas?
>>>
>>> Thanks,
>>> Ashish
>>> — NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and
>>> other seminars visit: http://www.osr.com/seminars To unsubscribe, visit
>>> the List Server section of OSR Online at
>>> http://www.osronline.com/page.cfm?name=ListServer
>>
>>
>>
>>
>> –
>> Paul Durrant
>> http://www.linkedin.com/in/pdurrant
>> — NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and
>> other seminars visit: http://www.osr.com/seminars To unsubscribe, visit
>> the List Server section of OSR Online at
>> http://www.osronline.com/page.cfm?name=ListServer
>
>
> — NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and
> other seminars visit: http://www.osr.com/seminars To unsubscribe, visit
> the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

–
Paul Durrant
http://www.linkedin.com/in/pdurrant

Ashish_Purkar · October 26, 2010, 2:31am

Enabling testsigning on both server and client, ndis test passed.
Earlier testsinging was not enabled on server side.

Thanks for the advice.

Ashish

On Mon, Oct 25, 2010 at 10:11 PM, Paul Durrant wrote:

> Enabling test signing was always enough to make things work for me.
>
>
> On 25 October 2010 15:49, Ashish Purkar wrote:
>
>> Hi Paul,
>>
>> Even after enabling testsigning using following commands, I see same
>> failure.
>>
>> bcdedit -set testsigning ON
>> bcdedit -set loadoptions DDISABLE_INTERGRITY_CHECKS
>>
>> Do I have do anything more to enable testsigning like gpedit.msc?
>>
>> Thanks,
>> Ashish
>>
>> On Mon, Oct 25, 2010 at 5:48 PM, Paul Durrant wrote:
>>
>>> Enable test signing on your box.
>>>
>>> On 25 October 2010 12:18, Ashish Purkar wrote:
>>>
>>>> Create binding on the test devices.*
>>>>
>>>> ProtocolManager::LoadDriver
>>>> - Driver Name: ndprot62
>>>> - Driver Path: D:\mak\ndistest.net\bin\protocol<br>>>>> Test terminated abnormally with an Exception
>>>> NDISTest.NDISTestCore.TestServices.NDISOperationException
>>>> 88888 Test terminated abnormally with an Exception
>>>> NDISTest.NDISTestCore.TestServices.NDISOperationException
>>>>
>>>> Exception details
>>>>
>>>> Type
>>>>
>>>> NDISTest.NDISTestCore.TestServices.NDISOperationException
>>>>
>>>> Message
>>>>
>>>> Unable to start ndprot62 driver serviceNDIS_STATUS (0x00000241)
>>>>
>>>> Source
>>>>
>>>> NDISTest.ScriptLibrary
>>>>
>>>> Stack Trace
>>>>
>>>> at NDISTest.NDISTestCore.TestServices.ProtocolManager.LoadDriver()
>>>> at
>>>> NDISTest.NDISTestCore.TestServices.ProtocolHelper.GetProtocolManager(IAdapter
>>>> adapter, UInt32 protocolType)
>>>> at NDISTest.NDISTestCore.TestServices.ProtocolHelper.Bind(IAdapter
>>>> adapter, String friendlyProtocolName, OpenType openType, String
>>>> friendlyOpenName, UInt32 openSubType, UInt32 bindingMechanism, UInt32
>>>> frameTypeArray, UInt32 frameTypeArraySize, UInt32 protocolType, Boolean
>>>> bPortsEnabled, UInt32 protocolFlags)
>>>> at NDISTest.NDISTestCore.TestServices.ProtocolHelper.Bind(IAdapter
>>>> adapter, String friendlyProtocolName, OpenType openType, String
>>>> friendlyOpenName, UInt32 openSubType, UInt32 bindingMechanism, UInt32*
>>>> frameTypeArray, UInt32 frameTypeArraySize, UInt32 protocolType, Boolean
>>>> bPortsEnabled)
>>>> at NDISTest.NDISTestCore.TestServices.ProtocolHelper.Bind(IAdapter
>>>> adapter, String friendlyProtocolName, OpenType openType, String
>>>> friendlyOpenName)
>>>> at Test_OffloadGSO.Start()
>>>> at NDISTest.NDISTestCore.TestServices.TestBase.StartTest()
>>>>
>>>>
>>>> While runnig NDIS test 6.5 manually(without DTM), I am seeing above
>>>> problem on windows server 2008 R2.
>>>>
>>>> In the event logs, I see
>>>>
>>>> The ndprot62 service failed to start due to the following error:
>>>> Windows cannot verify the digital signature for this file. A recent
>>>> hardware or software change might have installed a file that is signed
>>>> incorrectly or damaged, or that might be malicious software from an unknown
>>>> source.
>>>>
>>>> In the debugger, I see following error:
>>>>
>>>> ClientProtocolManager::CreateRemoteProtocolManager: Failed while sending
>>>> command to create remote Protocol Manager
>>>> Failed to create remote protocol manager
>>>>
>>>> . Error: 0000001F
>>>> Test terminated abnormally with an Exception
>>>> NDISTest.NDISTestCore.TestServices.NDISOperationException
>>>>
>>>> Any ideas?
>>>>
>>>> Thanks,
>>>> Ashish
>>>> — NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging
>>>> and other seminars visit: http://www.osr.com/seminars To unsubscribe,
>>>> visit the List Server section of OSR Online at
>>>> http://www.osronline.com/page.cfm?name=ListServer
>>>
>>>
>>>
>>>
>>> –
>>> Paul Durrant
>>> http://www.linkedin.com/in/pdurrant
>>> — NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and
>>> other seminars visit: http://www.osr.com/seminars To unsubscribe, visit
>>> the List Server section of OSR Online at
>>> http://www.osronline.com/page.cfm?name=ListServer
>>
>>
>> — NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and
>> other seminars visit: http://www.osr.com/seminars To unsubscribe, visit
>> the List Server section of OSR Online at
>> http://www.osronline.com/page.cfm?name=ListServer
>>
>
>
>
> –
> Paul Durrant
> http://www.linkedin.com/in/pdurrant
> — NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and
> other seminars visit: http://www.osr.com/seminars To unsubscribe, visit
> the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>