I received a call from a client - he sounded frustrated and couldn't get into Prevail this morning. The Advantage Database Server started earlier than the Wireless network card. So the ADS service apparently runs but doesn't do anything because it doesn't know that there's a network there. Clients are receiving a combination of 6420 and 7707 error messages.
This only seems to affect wireless adapters, the wired lan is initialized as a service earlier than the wireless service.
A simple stop and restart of the ADS service after a reboot restores the service. But in the clients mind this is unacceptable. Of course, his server is wireless which is below Prevail system spec and he recognizes that, but needs this working.
I looked into it, and as this is a Windows XP box there's no ability to delay start a service, however you can alter the ADS service dependencies so that it only starts when other services have been started. I changed the ADS service to wait on 'The Zero Configuration Wireless Service' which I did in the Windows registry.
The registry key is : HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServices
To create a new dependency, select the subkey representing the service you want to delay, click Edit, and then click Add Value. Create a new value name "DependOnService" (without the quotation marks) with a data type of REG_MULTI_SZ, and then click OK. When the Data dialog box appears, type the name or names of the services that you prefer to start before this service with one entry for each line, and then click OK.
The XP Zero Configuration Wireless service has a shortname of WZCSVC |
|
|
|
|
|
| User Opinions |
|
| 0% |
 |
100% |
 |
| 1 total votes. |
|
|
| How would you rate this answer? |
|
|
|
