You may experience difficulties when running the SQL-RT Knowledge Scripts. This section covers the following types of AppManager error message:
Problem: The Knowledge Script job fails with the following error:
Invalid or misspelled authentication parameter.
Solution: The ResponseTime managed objects validate the Run As Username/Domain Knowledge Script parameters, and start the ResponseTime managed object process as that user. If the client cannot access the Domain Controller for the domain listed for the Run As Domain parameter, the process cannot be started, and the transaction fails.
Review the following error message table:
|
Error Message |
Likely Cause |
|---|---|
|
Unable to validate domain user. |
Invalid Run As Username or SQL Logon Username. This is often caused by an invalid username. It may also be caused by trust relationship failure between the primary domain and the trusted domain. |
|
The server process could not be started because the configured identity is incorrect. Check the username and password. |
Server execution failed. Invalid Run As Password or SQL Logon Password parameter. |
|
The xxx ResponseTime Managed Object's RunTransaction method returned –2147024809 Could not find the domain controller for the domain. |
Invalid Run As Domain or SQL Logon Domain parameter |
|
The specified local group does not exist. |
Invalid value for Administrators group on managed client parameter |
Problem: The ResponseTime for SQL managed object’s RunTransaction method returned the following message:
The "NetIQ AppManager Client Resource Monitor" service (netiqmc.exe) user account is currently set as “xyz”. It must run as “Local System” account in order to use this ResponseTime module.
Solution: The netiqmc service must run as Local System. This is required for most AppManager ResponseTime modules. For more information, see Section 2.4, Permissions for Running Knowledge Scripts.
Then try running the job again.
Problem: The ResponseTime for SQL managed object’s RunTransaction method returned the following message:
Could not find the domain controller for the domain.
Solution: One cause of this problem is that the value you supplied for the Run As Domain Knowledge Script parameter is misspelled or does not exist.
The ResponseTime for SQL managed object validates the values supplied for the Run As Username and Domain parameters, and starts the ResponseTime for SQL managed object process under that user account. If the client cannot access the Domain Controller for the domain listed as the Run As Domain parameter, the process cannot be started, and the transaction fails.
Ensure the domain supplied for the Run As Domain parameter is valid and is typed properly. Verify that the Domain Controller is active and that there are no networking problems between the client and the Domain Controller. If the problem persists, contact the domain administrator.
Problem: The following error occurred while a Knowledge Script was running:
Unable to validate the local group member. Problems with operating system.
NOTE: It is normal to see this error during network maintenance.
Solution: This message means that the operating system cannot provide information about a local group at that moment. This error may occur during a network outage or system maintenance.
If the problem persists, contact your network administrator.
Problem: The following error occurred while a Knowledge Script was running:
Unable to validate Domain User. Problems contacting the domain controller while validating domain name and user account.
NOTE:Solution: This error may occur during network outage or system maintenance. It may also occur if the Domain Controller is shut down or reboots during an AppManager ResponseTime for SQL Server operation.
If the problem persists, contact your network administrator.
The RunTransaction method of the ResponseTime for SQL Server module returned the following message:
A member could not be added to or removed from the local group because the member does not exist.
Solution: The computer is not part of a domain (it cannot be in a Workgroup), or it is not part of the domain (or a trusted domain) specified for the Run As Domain parameter in the Knowledge Script.
Problem: The ResponseTime for SQL managed object’s RunTransaction method returned the following:
-2146959355 Server execution failed
Solution: The transaction may have failed due to network or server problems. Verify that there are no networking problems between the client and SQL Server, and that SQL Server is up and running.
Problem: The RunTransaction method of the ResponseTime for SQL Server module returned the following message:
–2147024809, The RPC server is unavailable.
Solution: Increase the schedule time of the SQL-RT jobs you are running, and reduce the number of jobs running on the computer.
When the SQL-RT Knowledge Scripts raise events stating that a “Transaction Failure” occurred, the cause is related either to the connection to the network or server or to the transaction that the Knowledge Script is attempting to perform. The SQL Server driver returns the specific error.
With any Transaction Failure event, the event details include information to help you understand why the failure occurred. Use this information to isolate the problem. The event details will point toward one of the following:
errors returned by the driver.
values you entered in the Knowledge Script.
Or you may want to look more closely at the “Job progress” section of the event detail message, which denotes the place in the transaction where the failure occurred. For example, the “Job progress” may indicate that the job proceeded no farther than “Connecting to database server.”
Problem: The job fails with a Transaction Failure. The event details include additional information to help you determine the reason for the failure.
Solution: Use the following information in the event details to isolate the problem:
errors returned by the SQL driver
transaction configuration settings you entered in the Knowledge Script
the Job Progress, which denotes where in the transaction that the failure occurred
Example 1:
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'test'.
Solution: You probably entered an invalid Run As Username or SQL Logon Username, or an invalid password.
Near the bottom of the event details, the “Job progress” section indicates that the job failed while “Connecting to database server.”
Example 2:
Microsoft OLE DB Provider for SQL Server: Invalid object name 'xxxxx'.
Solution: You probably entered an invalid name in your SQL statement.
Near the bottom of the event details, the “Job progress” section indicates that the job failed while “Execut[ing] SQL statement.”
Transaction initialization failures indicate that a failure occurred in the network authentication procedure.
The ResponseTime for SQL Server module validates the values you enter for the SQL Logon and Run As User ID/Domain Knowledge Script parameters. The managed object then connects to the SQL Server Database server to run the test as that “run as” user. If the client cannot access the SQL Server server using the information provided, the process cannot be started, and the transaction fails. Event details vary depending on the cause of the failure.
Problem: The job fails with a Transaction Initialization Failure. The following are examples of what the event details might include:
Example 1:
Knowledge Script Error 0x803CF007: SQL-RT cannot be initialized Error Code: 0x80070057 Error Message: Unable to validate Domain User. The UserName is not a valid user on the domain.
Solution: This error was a “transaction initialization failure” because the transaction itself was never performed. As you can see from the event details, an invalid username, domain, or password was supplied for one of the SQL Logon parameters in the Knowledge Script. The transaction was never initialized because the user could not be validated by the domain controller.
If you ran the job as “interactive user,” ensure a user was logged onto the computer.
Example 2:
Knowledge Script Error 0x803CF007: SQL-RT cannot be initialized Error Code: 0x80080005 Error Message: Server execution failed
Solution: You may see this error if you run many simultaneous SQL-RT Knowledge Script jobs. However, the real problem is not the number of jobs you are running. If you see this error, upgrade your AppManager agents the latest version. For information about the latest version, see the NetIQ Web site: www.netiq.com/support/am/extended/upgrade/default.asp.
Example 3:
Event: Transaction initialization failure Event Details: Knowledge Script Error 0x803CF007: SQL-RT cannot be initialized Error Code: 0x803CF004 Error Message: The module requested has been uninstalled or is outdated. Please install the latest version of the module.
Solution: The latest versions of the SQL-RT Knowledge Scripts are installed on the repository, but you are attempting to run them on a backlevel version of the AppManager ResponseTime for SQL Server module. You may have installed the most recent version of another AppManager ResponseTime module, but you are missing the latest engines needed to run this Knowledge Script job.
Install the latest version of AppManager ResponseTime for SQL Server on the client computer, re-run the Discovery Knowledge Script, and then restart this job. For more information about the latest version of the module, see the NetIQ Web site: www.netiq.com/support/am/extended/modules.asp.
Problem: The job fails with a transaction initialization failure. The event details include the following:
Knowledge Script Error 0x803CF007: SQL-RT cannot be initialized. Error Code: 0x8000401A Error Message: The server process could not be started because the configured identity is incorrect. Check the username and password.
Solution: Verify that the Run As Username, Password, and Domain are correct. If running as “Interactive User”, ensure a user is logged onto the computer.
Problem: The Knowledge Script job failed with the following error message:
The Knowledge Script's ConfigJob method failed Knowledge Script Error 0x803CF003: ConfigJob failed unexpectedly. The Knowledge Script may have been modified manually. Error Message: The remote server machine does not exist or is unavailable.
The error code associated with this failure is one of the following: 0x1CE, 0x800706BE, or 0x800706BF.
Solution: You may see this error if you run many simultaneous SQL-RT Knowledge Script jobs. However, the real problem is not the number of jobs you are running. If you see this error, upgrade your AppManager agents the latest version. For information about the latest version, see the NetIQ Web site: www.netiq.com/support/am/extended/upgrade/default.asp.
Problem: When you ran a Knowledge Script job, you received the following error message:
Error Code: 0x8000401A Error Message: The server process could not be started because the configured identity is incorrect. Check the username and password.
Solution: This error indicates that you entered incorrect security credentials for the Knowledge Script parameters.
Check the values you entered for the SQL Logon Username, Password, and Domain parameters. One of them is probably invalid or mistyped.
Problem: The Knowledge Script job failed with the following message:
Knowledge Script Error 0x803CF004: SQL-RT module has been uninstalled or is outdated. Please install the latest version of the module. Error Code: 0x1AD Error Message: ActiveX component can't create object
Solution: The latest versions of the SQL-RT Knowledge Scripts are installed on the repository, but you are attempting to run them on a backlevel version of AppManager ResponseTime for SQL Server.
Install the latest version of AppManager ResponseTime for SQL Server on the client computer, re-run the Discovery Knowledge Script, and then restart this job. For more information about the latest version of the module, see the NetIQ Web site: www.netiq.com/support/am/extended/modules.asp.