When troubleshooting Sybase WorkSpace deployment errors, keep in mind that the deployment services are implemented in an intermediate layer between the GUI and the application server. The GUI remotely invokes the deployment services which in turn remotely invoke application server components.
Also remember that the Sybase WorkSpace deployment service maintains its own repository of deployed packages. Any attempt to undeploy a service package with Jagtool or EAServer Manager will result in an improper undeployment.
Problem: Errors occur when deploying a packaged service.
Solution: Use the following sequence to troubleshoot errors during deployment:
Save a copy of the <service package name>.svcpkg file Sybase Tech Support may request it.
Closely examine the causal chain of com.sybase.uo.management.ManagementException stack traces displayed in the Sybase WorkSpace or the mtool command line utility.
Review the following log files:
<installation directory>\Sybase\WorkSpace\Eclipse\workspace\.metadata\.log
<installation directory>\Sybase\WorkSpace\DevRuntimes\EAServer\SysMgmt\agent.log
<installation directory>\Sybase\WorkSpace\DevRuntimes\EAServer\bin\Jaguar.log
Enable the agent.log debug messages to obtain package deployment information in greater detail. Edit the <installation directory>\Sybase\WorkSpace \DevRuntimes\EAServer\SysMgmt\agent.cmd file, stop and restart the server, then redeploy the service package.
If you use long names for service files and the services package file, deployment may fail when the path to an intermediate generated file exceeds operating system limits. In this case, try repackaging the services with a package that uses a shorter file name.
Troubleshooting Service Packaging Errors
Send your feedback on this help topic to Sybase Tech Pubs: pubs@sybase.com