Applicable versions and levels
Windows versions: V5.0L10 or later
Action
Points to check
Has the job that handles Microsoft Office products such as Excel or Access been executed on the server, and not the client?
Cause
If the job that handles Excel or Access has the following states, it may have been affected by the behavioral specification for the Microsoft Office products:
It does not end.
It ends normally, but the result is unintended.
It ends abnormally, and the result is unintended.
Microsoft does not recommend Office server-side automation, nor does it provide support. Refer to Microsoft Knowledge Base Article 257757 for details.
Action method
Use the Task Link client application startup command to execute the job. Refer to the Reference Guide for information on Task Link.
Information
This case has been reported in jobs in which Excel and Access have been started as follows:
Using the DCOM (distributed COM) mechanism.
Using the VBScript CreateObject.
