SQL Web Assistant: Could not execute the SQL statement.

Details
Product: SQL Server
Event ID: 16805
Source: MSSQLServer
Version: 8.0
Component: SQL Engine
Message: SQL Web Assistant: Could not execute the SQL statement.
   
Explanation
The SQL Web Assistant was unable to execute the specified query or stored procedure. Often, though not always, the reason the query failed will also be reported as an additional error. A common associated error is error 170 “Line %d: Incorrect syntax near ‘%.*ls’.”

If the SQL Server service is started with the local system account, the sp_makewebtask system stored procedure tries to determine what permissions the domain user account has. Because the local Windows NT user account is not permitted to obtain domain permissions, the procedure is not successful, and you receive the error message. For more information about this scenario, see the Microsoft Knowledge Base article, 834116.

If your web task uses a linked server and you see error 7410 along with this error, you may have encountered the side effect of some increased security introduced in SQL Server 2000 SP3. For more information about this scenario, see the Microsoft Knowledge Base article 823429.

   
User Action
If another error is also reported, troubleshoot that error first.

Use SQL Profiler to see if there are any additional errors such as 8198. If other errors show up in the Profiler trace, troubleshoot those errors first.

If you encounter the problem documented in 834116, use one of the following methods to work around this problem:

  • Method 1: Run the SQL Server service under the security context of a domain account that has administrative permissions on the computer that is running SQL Server 2000. Microsoft does not recommend that you run the SQL Server service under the security context of a local administrator account.
  • Method 2: Connect to SQL Server 2000 by using a SQL Server login account that is a member of the sysadmin fixed server role, and then run the sp_makewebtask system stored procedure. Note Microsoft does not recommend that you connect to SQL Server 2000 by using a SQL Server login account that is a member of the sysadmin fixed server role to work around this problem.
  • If you encountered the scenario in 823429, you can use the workaround specified in the article or apply the fix.

Related:

Leave a Reply