Random Internal Query Processor Error

Question

Post reply

Random Internal Query Processor Error

Kyle Schlapkohl

SSCrazy

Points: 2463
More actions
August 24, 2007 at 2:38 pm

#180414

Application folks experiencing recurrence of problem previously reported. This is causing delays with multiple projects. Errors below are occuring when attempting to run a DTS package that will refresh data from prod to pilot.
Exception Details: System.Data.SqlClient.SqlException: Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Another example reads:
Step Error Source: Microsoft Data Transformation Services (DTS) Package
Step Error Description:The task reported failure on execution. (Microsoft OLE DB Provider for SQL Server (80004005): Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services.)
Step Error code: 8004043B
Step Error Help FileTongue Tiedqldts80.hlp
Step Error Help Context ID:1100

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply

Kyle Schlapkohl SSCrazy Points: 2463 More actions · Answer 1

I actually have a second error that could be somewhat related to the first...

Step Error Source: Microsoft Data Transformation Services (DTS) Package

Step Error Description:The task reported failure on execution. (Microsoft OLE DB Provider for SQL Server (80004005): IDENTITY_INSERT is already ON for table '

.dbo.'. Cannot perform SET operation for table '

.dbo.'.)

Step Error code: 8004043B

Step Error Help File:sqldts80.hlp

Step Error Help Context ID:1100

We hit this error awhile back, but got around it by creating an unnattended process account (account_name) and granting it DDL admin. That however isn't working anymore. Can someone please help with this.

These errors have started to pop up after my team upgraded a clustered SQL 2000 server to a clustered SQL Server 2005. The SQL Server 2005 server is on SP2.