KNOWN ISSUE: Status code 1226 error "Network connection was gracefully closed" when installing automation partitions

Products

• Deployment Solution

Issue/Introduction

Getting status code 1226 error, "The network connection was gracefully closed," when installing RapidInstall packages or automation partitions (Linux or WinPE). This problem is inconsistent, sometimes working correctly.

Cause

This error is caused by AClient shutting down before it is ready to do so properly.

Resolution

This is a known limitation. 

The current work around is to create the following type of job:

Job Deploy BootWorks Partition

1. Copy file to... (specify the RapidInstall or BootWorks install package .exe that was created by the Boot Disk Creator).
2. Run script (ping localhost), server or client side.
3. Run script (start c:\bootworks_inst.exe). Specify the .exe copied in step 1. 

Note: On task 3 you must use the "start" command in the script to launch the install. or you will run in to another bug where the client will hang in automation.

Also note, if you need to add additional jobs or tasks to run right after the install, you will need a task 4 Run script (ping localhost) that runs server side. The reason for this is that the install package shuts down the AClient, but the next task will begin to run before the package can shutdown the AClient and, therefore, the AClient terminates midway through a task. This causes synchronization  problems with the server.

Applies To
Deployment Solution 6.8 SP2
Norton AntiVirus 10.1
SQL* 2005