Problems starting an integrated Windows server

If your integrated server will not start, perform these steps to determine the problem.

1. Check the status of the server. Verify that the current status of the NWSD is VARIED OFF. If it is not, vary off the NWSD; then retry starting the server. See Start and stop an integrated server. If the status of the server is VARY ON PENDING even though the integrated server did not start, there may be a device driver problem.
2. Look for error messages and possible corrective actions in the job log where the vary on of the NWSD was performed.
3. Look in the QSYSOPR message queue for failure messages and possible corrective actions.
4. If you created a server configuration file that might be causing problems, try repairing or resetting the server configuration file. See NWSD configuration file errors.
5. If you initiated a restart from the integrated server, perform these steps.
   1. On i5/OS, enter the command WRKACTJOB SBS(QSYSWRK).
   2. Press Enter.
   3. Locate the job QVNAVARY.
   4. Select option 5 to work with the job.
   5. If the job is active or on the job queue, select option 10 to display the job log. Look for failure messages and possible corrective actions.
   6. If you have ended the job, enter WRKSPLF SELECT(*CURRENT *ALL *ALL QVNAVARY) to display the spooled file.
6. Enter the command WRKPRB to see logged problems.

For IXS or IXA attached xSeries® server, a batch job using the name BTnwsdname is submitted to perform the vary off and vary on needed to 'reboot' the server.

Identify the qualified name of the job that was submitted in the QVNAVARY joblog. Locate the joblog for the submitted 'reboot' job by fully qualifying the jobname using WRKSPLF SELECT(*ALL) JOB(qualjobname).

List all 'reboot' jobs with WRKSPLF SELECT(*ALL) JOB(BTnwsdname) .

Emergency Repair

If the problem persists due to a failing system drive but you have a successful backup of that drive, try this emergency repair. To recover lost data and return the system to a functioning state, follow these steps.

Note:

These examples use the NWSD name ERS with a system drive named ERS1.

1. Unlink the failing system drive (typically the C: drive) by using this command: RMVNWSSTGL NWSSTG(ERS1) NWSD(ERS).
2. Copy the failing system drive to a new name by using this command: CRTNWSSTG NWSSTG(ERSBKP) FROMNWSSTG(ERS1).
3. Restore your latest backup of the system drive.
4. Link in the restored system drive by using this command: ADDNWSSTGL NWSSTG(ERS1) NWSD(ERS).
5. Link in the failing system drive from step 1 by using this command: ADDNWSSTGL NWSSTG(ERS1BKP) NWSD(ERS)
6. Vary on the NWSD by using this command: VRYCFG CFGOBJ(ERS) CFGTYPE(*NWS) STATUS(*ON).
7. Copy any key files, such as data files, from the failing system drive which have changed from the latest backup.
8. Install any applications that you added or upgraded since the latest backup.
9. Vary off the NWSD by using this command: VRYCFG CFGOBJ(ERS1) CFGTYPE(*NWS) STATUS(*OFF).
10. Unlink the failing system drive from step 5 by using this command: RMVNWSSTGL NWSSTG(ERS1BKP) ERS(ERS1).
11. Until you are sure you have removed all data from the failing system drive, you can relink the drive (step 5) and copy additional files to the restored drive. Once you are sure that you have removed all data from the failing system drive, make a new backup of all storage spaces. Refer to Back up predefined disk drives for integrated Windows servers for steps to backup storage spaces. Then delete the failing system drive by using this command: DLTNWSSTG NWSSTG(ERS1BKP).