NOTICE: Our Community is moving. Get more information. Updated information on a New Login Process
Generating Classic Agent log files
Flagnames:QAP_DEBUG_AGENT - overall/general. If this fails use QAP_DEBUG only.QAP_DEBUG_DOTNET - for .NetQAP_DEBUG_MEMORY - For memory usageQAP_DEBUG_CLOSE - for WND CloseQAP_DEBUG_HOOKS - For hookingQAP_DEBUG_AXEXT - for ActiveXQAP_DEBUG_HLPR - For QaphlprQAP_DEBUG_JAVACON - java connectorQAP_DEBUG_NETWORK - network protocolQAP_DEBUG_UPLOADPLAN - uploading a plan to SCTMHow to create a Classic Agent log file:-
1. First, make sure that no SilkTest or Agent processes are running.2. Then from a DOS prompt window do the following:
Delete or rename c:\[flagname].log if the file exists.Change your working directory to your SilkTest installation directory.Set the required environment variable:set [flagname]=1
3. Start the Agent manually.
start .\agent4. Start SilkTest manually.
Go through the scenario to reproduce the problem. The file c:\[flagname].log file should be created.
Vista / Windows 7 / Windows 2008 problems with the Classic Agent
However, attempting to generate a Classic Agent debug log file in Windows Vista sometimes results in no file being created because it doesn't like you writing to the root of the C:\ drive. If this is the case;-
1. Check UAC (User Account Control) and ensure that itis turned off. If UAC is turned on, this prevents SilkTest from generating the debug log file.
2. If UAC is turned off and SilkTest still fails to generate a logfile, although a local user may be a member of the Administrators group, that administrator will not have the elevated permissions required to write to the root of the C:\ drive. Effectively this administrator role is more akin to the 'Power User' role in the older Windows operating systems. To generate a debug.log file you may need to be logged in as the root administrator. To force the appearance of the root administrator on the login screen do the following:
1. Go to Start | Run and enter 'secpol.msc'.2. Dismiss the UAC if challenged.3. Within the Security Policy console locate Local Policies | Security Options4. Enable 'Accounts: Administrator Account Status' policy.5. Click OK and dismiss the Policy console.
The root administrator should now be visible in Control Panel | User Accounts. If you now login as the root administrator the debug.log file should be created successfully.
Logfiles are generated automatically for the Open Agent. Depending on the operating system they can be found in one of two places:-- WindowsXP: C:\Documents and Settings\[username]\Application Data\Silk\SilkTest\logs- Windows Vista/7: C:\Users\[username]\AppData\Roaming\Silk\SilkTest\logs
1. Navigate to the ...\SilkTest\logs directory. This may have one or more xml files in it named "SilkTest_OpenAgent_Log.xml.1" (.2, .3, .etc)2. Delete all of these xml files.3. Go to ...\SilkTest\ng\controlcenter\FASTxd\configuration4. Rename log4j.properties to log4j.properties.old5. Rename log4j.full.properties to log4j.properties6. Record/execute against the Flex application as necessary7. Zip the xml files in the C:\Documents and Settings\Application Data\Borland\SilkTest\logs. Depending on the length of recording/execution there may be more than one of these files8. Rename log4j.properties to log4j.full.properties9. Rename log4j.properties.old to log4j.properties.
The reason for the renaming of the properties files is as follows: when the Open Agent starts it reads the log4j.properties file which instructs the agent what events to log. The normal log4j.properties file only contains minimal logging instructions (for performance reasons). Therefore we ship another one (log4j.full.properties) which instructs the agent to log much more. This file is normally never read by the agent because it just searches the log4j.properties file, so in order to make the agent log almost all events we need to rename the log4j.full.properties file to log4j.properties.
Generating Dr.Watson dump files
To install Dr.Watson you can either change a registry value
or run the command "drwtsn32 -i" from a cmd prompt. The latter is preferable as it is easiest.
1. To start Dr. Watson, click Start, click Run, and then type drwtsn32.
2. Ensure the following options are selected:
Make a note of the paths to the Log & Crash dump files as this is where the files will be generated.3. Navigate to the above paths and remove any old log files. 4. Close the Dr Watson via the Ok button.
The next application crash will be logged within the Dr. Watson Log Files.