Deployment Job failed with "Incorrect function"

Products

• Ghost Solution Suite

Issue/Introduction

Deploying image or changing configuration of a Window machine failed with "Incorrect function" during configuration stage.

<Dagent.log>
[08/26/2010 05:30:4.676 3916 2] configbuilder.cpp:202: The error caught was not 'NIC_NOT_ASSOCIATED'. Re-throw the error.
[08/26/2010 05:30:4.676 3916 0] internal/Configure.cpp:755 Configure::HandleMessage(): caught win32 error
 SetStaticRouteWmi.cpp:142 - Failed to add static route
 Value=5, SystemError=0x00000001
<Dagent.log>

Cause

As per Microsoft TechNote the static route cost metric must be between 1 and 9999 but Windows allows/sets a -ve value.
We have confirmed, in Windows at least following two steps set a -ve value. 

1.  Configuring network parameters setting using "netsh" allows a -ve value in Static Route cost metric.
2.  Configuring default gateway in Internet Protocol (TCP/IP) -> dialog-box,  sets Static Route cost metric to -1 .

Example: 
c:\ netsh interface ipv4 set address "Local Area Connection" static 192.168.1.90 255.255.255.0 192.168.1.100 -1

 

Resolution

Check current PersistentRoutes 
Example:
 c:\reg query HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\PersistentRoutes
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\PersistentRoutes
    0.0.0.0,0.0.0.0,192.168.1.1,-1    REG_SZ

Manually configuring TCP/IP parameters using netsh command without any cost metric value or a +ve value or
entering appropirate value (between 1 and 9999) in "Automatic metric" under TCP/IP -> Advanced dialog-box
will solve the issue.

Example:
c:\ netsh interface ipv4 set address "Local Area Connection" static 192.168.1.90 255.255.255.0 192.168.1.100
c:\ netsh interface ipv4 set address "Local Area Connection" static 192.168.1.90 255.255.255.0 192.168.1.100 1

 

 

Note:
As it is a none-Symantec  issue, please inquire Microsoft.  

Applies To

Windows Operating Systemes