The environment scripts are located with the SERL files. For example, on Windows, in %SOAM_HOME%\work\serl\appName\serviceName.
An easy way to set the environment is to copy the base file name from the service instance manager log that you were viewing in "Determining the problem". Change .serl in the file name to .env.bat, .env.profile, or .env.cshrc as required.
On Windows, another easy way is to first navigate to the %SOAM_HOME%\work\serl\appName\serviceName directory using Windows Explorer, then drag the icon of the environment script into the command prompt, and press Enter.
/usr/bin/gdb
devenv C:\mydirectory\mysolution_vc71.sln
or, if your Visual Studio environment is not set in the command prompt:
"C:\Program Files\Microsoft Visual Studio.NET 2003\Common7\IDE\devenv.com" \mydirectory\mysolution_vc71.sln
For example, if you already know that the problem is in CreateService, put a breakpoint at the beginning of the CreateService method. Otherwise, if you do not know where the problem is, put breakpoints at the beginning of each method.
If there are multiple problems in a particular method, you should be able to catch them using one iteration of service replay debugging. If, however, there are problems in other methods that were not yet invoked when the service was run, no replay data exists for these methods. Actions cannot be replayed until they are played once through Symphony or Symphony DE.