You might encounter the following issues when you attempt to deploy jobs for scheduling:

• If errors occur during the deployment process, the job code might get generated in the target location; however, the metadata reference to the deployed job code will not be created. Without the metadata reference, there is no way to schedule the job for execution via Schedule Manager in SAS^® Management Console.
• If you receive a blank results window after attempting to deploy one or more jobs, then get returned to the Scheduling window after selecting OK, the deployment process has failed. The cause of failure is most likely a Java Stack Overflow. Confirm this by viewing the contents of the following file:

  C:\Documents and Settings\userid\errorLog_SAS_Data_Integration_Studio_3.4.txt

  where userid is the system ID that you use to log on to the Windows client machine.

  You might be able to circumvent this error by adding the -Xss java invocation option to the etlstudio.ini file. This file is located in the product installation folder, which is typically:

  C:\Program Files\SAS\SASETLStudio\9.1\etlstudio.ini

  Edit this file, add the argument -Xss2m to the CommandLineArgs= string, save the file, and then try performing the deployment again.

• After a successful deployment, you might experience a significant delay when you attempt to perform another task within SAS Data Integration Studio that requires retrieval of metadata from the server. Some sites have reported that the client remains locked for 20 minutes, or more. If you experience this behavior, you can avoid this delay by exiting and reentering the product.

Select the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for this issue for SAS Data Integration Studio 3.4 is available at: