Query timeout expired and Invalid object name

I have a program that processes data (dequeues) and polls about every 2.5 seconds - normally there are several records to process per second - it does this constantly 24/7. The program runs fine at about 100 sites. At 2 sites the following error occurs
about once per day. Typically the table has less than 10 records that get processed ie read then deleted. DataObjects are used ie the data is read, connection closed, processed, deleted using T-SQL from ADO - ie transactions are as short as possible.
Error#-2147217871 Query timeout expired. SQL:SELECT RealID, RxerID, PhoneID, Min(ServerDtTm), min(ID) FROM dbo.tblPreReceiver GROUP BY RealID, RxerID, PhoneID ORDER BY Min(ServerDtTm), min(ID)
Inner exception Error No. -2147217865. Error Desc:Invalid object name 'dbo.tblPreReceiver'.. Native Error:208 Source:Microsoft OLE DB Provider for SQL Server SQL State:42S02.
SQL Server 2008R2 (Express at one site and Standard another).
The program then runs again 2.5 seconds later without error.
Can anyone explain why?
I suspect it is a blocking error but the error message does not suggest this at all. There is another application which writes to this queue, this does not report the error.

Yes, blocking can be the cause. The default command timeout is 30 sec and if the table is locked by an other process, the command waits until the table is accessable ... or the timeout raises. You could increase the timeout value or you could perform "dirty
read" = ignoring lock, but I don't want to suggest to do it.
Olaf Helper
[ Blog] [ Xing] [ MVP]

Similar Messages

SSRS Error : Query execution failed for dataset 'dataSet'. (rsErrorExecutingCommand) Semantic query execution failed. Invalid object name 'RPT.*********'. (rsSemanticQueryEngineError)

I am new to SSRS and I am trying to migrate reports from 2008 to 2012. As I have so many reports to migrate, I simply got the back up of ReportServer,
ReportServerTempDB, and Encryption Key and restored them to test environment. I made necessary configuration from RS configuration tool. I am able to see the reports now when I browse //hostname/reports. But when I open any particular report I am getting some
error.
· An error has occurred during report processing.
(rsProcessingAborted)
Query execution       failed for dataset 'dataSet'.
      (rsErrorExecutingCommand
Semantic query        execution failed. Invalid object name
       'RPT. ******'. (rsSemanticQueryEngineError)
****** - I am assuming this is a custom data class.
Does anyone have insight on this? or any better way that I can migrate the reports to new server with less efforts.
I don’t have the reports solution file to deploy the reports, so I have followed backup and restore process.

Hi Kishore237,
According to your description, you migrated some reports from Reporting Services (SSRS) 2008 to 2012. Now you get error when accessing the reports on SSRS 2012. Right?
In this scenario, did you modify the report data source in database after migration? You can try to open the report in Report Builder or Report designer and check the report dataset. If you can preview the report in Report builder or Report designer,
please try to redeploy the report to Report Server. If it is still not working, please try to restore the database from backup. And for migrating reports, please follow the "Content-Only Migration" in the link below:
http://msdn.microsoft.com/en-us/library/ms143724(v=sql.110).aspx
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

: "Invalid object name '#Temp'.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

Hi   .
    I was creating the pass the values t in temp tables though s sis package vs2012 .
  First I was taken on executive SQL TASK.
IN EXCUTIVE SQL TASK . I was write the stored proce:
Sp;
reate procedure USP_GETEMP2333
AS
begin
Select eid,ename,dept,salary from emp
end;
create table #temp(eid int,ename varchar(20),dept varchar(20),salary int)
insert into #temp
   exec USP_GETMP02333
   go.
It was executive correctly.
I was taken another sequence container. In the sequence container iam creating one   executive sql
In 2<sup>nd</sup> excutive sql task: sql statements is
if object_id('emp_fact_sal') is not null
drop table emp_fact_sal
select eid,ename as emp_name,sal_bar=
case when salary<=5000 then 'l'
when salary >5000 and salary<=7000 then 'm'
else
'h'
end
into emp_fact_sal from #temp.
and one falt flies it was taken to designation .
iam changing all connection properties:
in oldeb connection:
in excutive sal task properties .
delay validation is true,
and retain connection maner is also true,
and package mode is 64 bit is false.
But iwas excutive in 2<sup>nd</sup> excutive ql task .
Iam getting this type of errors,
                [Execute SQL Task] Error: Executing the query " if object_id('emp_fact_sal') is not null
drop ta..." failed with the following error: "Invalid object name '#Temp'.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established
correctly.
Please help me

Arthur suggestion works but you shouldnt even be doing this on a SQL Task.
Use a data flow task. You'll have better control over the data that is being transfered and get better performance because no staging table will be used.
Just because there are clouds in the sky it doesn't mean it isn't blue. But someone will come and argue that in addition to clouds, birds, airplanes, pollution, sunsets, daltonism and nuclear bombs, all adding different colours to the sky, this
is an undocumented behavior and should not be relied upon.

Report error, Invalid object name 'v_lu_cpu'

Hi
I have a report that I have imported from another SCCM server that has it working. I have changed the datasources after the import but when I try to run the report I get this error message:
An error has occurred during report processing. (rsProcessingAborted)
Query execution failed for dataset 'DataSet0'. (rsErrorExecutingCommand)
Invalid object name 'v_lu_cpu'.
Does anybody know what this means?

Ok, then I understand.
I'm not that good at reporting so if anybody can help out with replacing the code that uses v_lu_cpu with
something else, it would be very kind. Thank you
SELECT DISTINCT
v_r_system.netbios_name0 AS "Computer Name",
v_r_system.Description0 AS "Description",
v_gs_system_console_usage.topconsoleuser0 AS "Top Console User",
v_GS_PC_BIOS.serialnumber0 AS "PC Bios Serial Number",
v_gs_computer_system.manufacturer0 AS "Computer Manufacturer",
v_gs_computer_system.model0 AS "Computer Model",
CASE
WHEN v_gs_computer_system.manufacturer0 LIKE 'Dell%'
THEN 'http://support.dell.com/support/topics/global.aspx/support/my_systems_info/details?servicetag=' + v_gs_system_enclosure.serialnumber0
WHEN v_gs_computer_system.manufacturer0 LIKE 'Hewlett%'
THEN 'http://h20000.www2.hp.com/bizsupport/TechSupport/WarrantyResults.jsp?sn=' + v_gs_system_enclosure.serialnumber0 + '&country=US'
WHEN v_gs_computer_system.manufacturer0 LIKE 'HP%'
THEN 'http://h20000.www2.hp.com/bizsupport/TechSupport/WarrantyResults.jsp?sn=' + v_gs_system_enclosure.serialnumber0 + '&country=US'
ELSE '(Not available)'
END AS "Warranty Information"
FROM v_gs_processor
INNER JOIN v_r_system
ON v_gs_processor.resourceid = v_r_system.resourceid
INNER JOIN v_gs_system_enclosure
ON v_gs_system_enclosure.resourceid = v_r_system.resourceid
INNER JOIN v_GS_PC_BIOS
ON v_GS_PC_BIOS.resourceid = v_r_system.resourceid
INNER JOIN v_gs_computer_system
ON (v_gs_computer_system.resourceid = v_r_system.resourceid)
LEFT JOIN v_gs_system_console_usage
ON v_gs_system_console_usage.resourceid = v_r_system.resourceid
LEFT JOIN v_lu_cpu
ON Lower(v_lu_cpu.cpuhash) = Lower(v_gs_processor.cpuhash0)
WHERE v_GS_SYSTEM_ENCLOSURE.ChassisTypes0 <> 12
AND
v_gs_computer_system.manufacturer0 NOT LIKE 'VMware%'
AND
v_gs_computer_system.model0 NOT LIKE 'Virtual Machine'
AND
v_R_System.Operating_System_Name_and0 LIKE 'Microsoft Windows NT Workstation%'

Invalid object name 'dbo.v_R_System'

Hi,
About six months ago I implemented SCCM in our domain and it's been working great. This morning, when I attempted to run one of the Asset Intelligence reports in the console, I received the following error...
An error has occurred during report processing. (rsProcessingAborted)
...uh oh! So I logged onto our SQL database server, opened up the Report Manager in IE and attempted to run the same report. This time I got a bit more...
An error has occurred during report processing. (rsProcessingAborted)
Query execution failed for dataset 'DataSet0'. (rsErrorExecutingCommand)
Invalid object name 'dbo.v_R_System'. Could not use view or function 'fn_rbac_R_System_Valid' because of binding errors.
...I'm no SQL admin, so time to ask Mr Internet. The only related post I could find was the first one you get when you search "dbo.v_R_System missing" on any search engine (the ones I tried anyway).
...which wasn't particularly helpful.
One thing I did try, which I thought was worth a shot, was to create a new database in Reporting Services Configuration Manager. After a few minutes that populated nicely with all the reports,
but I'm still getting the same problem.
We've got a really simple environment. Two Windows Server 2008 R2 servers for SCCM,
one running the site database and reporting server and the other doing everything else. Database is running on Microsoft SQL Server 2012.
Any ideas?
Cheers,
Dave

I was also missing that same view. I can't believe it. In production and in my test environment we are on ConfigMgr 2012 SP1 CU3. I started the upgrade on my test environment and it failed saying that it couldn't find that view.
I went to our production environment and the view existed. I scripted the creation of the view and then created the view in our test environment. The upgrade successfully completed after that. Thanks for leading me in the right direction!

Invalid Object Name When Executing from Report Manager

I ran some code to create a modified view of ExecutionLog3 on a SQL Server 2012 instance. The ReportServer and ReportServerTempDB were transferred from a 2005 instance and are still on that compatibility level. After creating the new view, I
created a report in SSDT and it runs fine. I deployed the dataset followed by the report. I went to Report Manager to test it and the report fails with the following:
An error has occurred during report processing. (rsProcessingAborted)
The execution failed for the shared data set
'ExecutionLog'. (rsDataSetExecutionError)
Query execution failed for dataset ''. (rsErrorExecutingCommand)
Invalid object name 'ExecutionLog3_Modified'.
The code for the view is below and it came from MSSQLTips. Why does the report run fine from SSDT and fail in Report Manager?
USE [ReportServer]
GO
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
CREATE VIEW [dbo].[ExecutionLog3_Modified]
AS
SELECT
EL.InstanceName,
COALESCE(C.Path, 'Unknown') AS ItemPath,
EL.UserName,
EL.ExecutionId,
CASE(EL.RequestType)
WHEN 0 THEN 'Interactive'
WHEN 1 THEN 'Subscription'
WHEN 2 THEN 'Refresh Cache'
ELSE 'Unknown'
END AS RequestType,
-- SubscriptionId,
EL.Format,
Parameters,
CASE(EL.ReportAction)
WHEN 1 THEN 'Render'
WHEN 2 THEN 'BookmarkNavigation'
WHEN 3 THEN 'DocumentMapNavigation'
WHEN 4 THEN 'DrillThrough'
WHEN 5 THEN 'FindString'
WHEN 6 THEN 'GetDocumentMap'
WHEN 7 THEN 'Toggle'
WHEN 8 THEN 'Sort'
WHEN 9 THEN 'Execute'
ELSE 'Unknown'
END AS ItemAction,
EL.TimeStart,
YEAR(EL.TimeStart) AS Start_Year,
MONTH(EL.TimeStart) AS Start_Month,
DATENAME(MONTH,EL.TimeStart) AS Start_Month_Name,
DATENAME(DW,EL.TimeStart) AS Start_Day_Of_Week,
DATEPART(WEEKDAY,EL.TimeStart) AS Start_Day_Number_of_Week,
EL.TimeEnd,
EL.TimeDataRetrieval,
EL.TimeProcessing,
EL.TimeRendering,
CASE(EL.Source)
WHEN 1 THEN 'Live'
WHEN 2 THEN 'Cache'
WHEN 3 THEN 'Snapshot'
WHEN 4 THEN 'History'
WHEN 5 THEN 'AdHoc'
WHEN 6 THEN 'Session'
WHEN 7 THEN 'Rdce'
ELSE 'Unknown'
END AS Source,
EL.Status,
EL.ByteCount,
EL.[RowCount],
EL.AdditionalInfo,
C.Name,
C.CreatedByID,
C.ModifiedByID,
C.Description,
C.CreationDate,
C.ModifiedDate,
CASE
WHEN C.TYPE=1 THEN 'Folder'
WHEN C.TYPE=2 THEN 'Report'
WHEN C.TYPE=3 THEN 'XML'
WHEN C.TYPE=4 THEN 'Linked Report'
WHEN C.TYPE=5 THEN 'Data Source'
WHEN C.TYPE=6 THEN 'Model'
WHEN C.TYPE=8 THEN 'Shared Dataset'
WHEN C.TYPE=9 THEN 'Report Part'
END AS Type_Description
FROM
ExecutionLogStorage AS EL
LEFT OUTER JOIN Catalog AS C ON (EL.ReportID = C.ItemID)
GO
Lee Markum

Hi Lee,
According to your description, you can't process the dataset when viewing the report on report server. Right?
In this scenario, as you can see the dataset name in error message is empty, and it says "Invalid Object Name". Because you have already created a view in your database. When you run this report again, this query be executed again so that you can
not create another view with same name. So you just need to query the view directly when creating dataset.
Select * from ExecutionLog3_Modify
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

MBAM 2.5 Reports Fail with "Invalid object name 'v_GS_MBAM_POLICY'."

Utilizing the SSRS Reports for MBAM 2.5 Integrated into Configuration Manager 2012 R2 Cu3, when I run the reports it states that the view
'v_GS_MBAM_POLICY' does not exist.
The complexing thing though is that there are computers that are reporting the HINV Class called 'Win32Reg_MBAMPolicy' So I would think this view would have been created.
Does anyone know the process by which the view gets generated since my HINV is reporting back the information, yet the view has not been created in the DB yet... It makes no sense.
The error is:
Microsoft.Reporting.WinForms.ReportServerException
An error has occurred during report processing. (rsProcessingAborted)
Stack Trace:
   at Microsoft.Reporting.WinForms.ServerReport.ServerUrlRequest(Boolean isAbortable, String url, Stream outputStream, String& mimeType, String& fileNameExtension)
   at Microsoft.Reporting.WinForms.ServerReport.InternalRender(Boolean isAbortable, String format, String deviceInfo, NameValueCollection urlAccessParameters, Stream reportStream, String& mimeType, String& fileNameExtension)
   at Microsoft.Reporting.WinForms.AsyncMainStreamRenderingOperation.RenderServerReport(ServerReport report)
   at Microsoft.Reporting.WinForms.AsyncRenderingOperation.PerformOperation()
   at Microsoft.Reporting.WinForms.ReportViewer.AsyncReportOperationWrapper.PerformOperation()
   at Microsoft.Reporting.WinForms.ProcessingThread.ProcessThreadMain(Object arg)
Microsoft.Reporting.WinForms.ReportServerException
Query execution failed for dataset 'ComplianceDetails'. (rsErrorExecutingCommand)
Stack Trace:
   at Microsoft.Reporting.WinForms.ServerReport.ServerUrlRequest(Boolean isAbortable, String url, Stream outputStream, String& mimeType, String& fileNameExtension)
   at Microsoft.Reporting.WinForms.ServerReport.InternalRender(Boolean isAbortable, String format, String deviceInfo, NameValueCollection urlAccessParameters, Stream reportStream, String& mimeType, String& fileNameExtension)
   at Microsoft.Reporting.WinForms.AsyncMainStreamRenderingOperation.RenderServerReport(ServerReport report)
   at Microsoft.Reporting.WinForms.AsyncRenderingOperation.PerformOperation()
   at Microsoft.Reporting.WinForms.ReportViewer.AsyncReportOperationWrapper.PerformOperation()
   at Microsoft.Reporting.WinForms.ProcessingThread.ProcessThreadMain(Object arg)
Microsoft.Reporting.WinForms.ReportServerException
Invalid object name 'v_GS_MBAM_POLICY'.
Stack Trace:
   at Microsoft.Reporting.WinForms.ServerReport.ServerUrlRequest(Boolean isAbortable, String url, Stream outputStream, String& mimeType, String& fileNameExtension)
   at Microsoft.Reporting.WinForms.ServerReport.InternalRender(Boolean isAbortable, String format, String deviceInfo, NameValueCollection urlAccessParameters, Stream reportStream, String& mimeType, String& fileNameExtension)
   at Microsoft.Reporting.WinForms.AsyncMainStreamRenderingOperation.RenderServerReport(ServerReport report)
   at Microsoft.Reporting.WinForms.AsyncRenderingOperation.PerformOperation()
   at Microsoft.Reporting.WinForms.ReportViewer.AsyncReportOperationWrapper.PerformOperation()
   at Microsoft.Reporting.WinForms.ProcessingThread.ProcessThreadMain(Object arg)
David Baur

We ran into this error as well. Turns out that MBAM-provided reports to SCCM 2012 fail with an error unless the Win32Reg_MBAMPolicy class is added to SCCM, which also updates the SCCM SQL with required Views, including "v_GS_MBAM_POLICY".
The solution that we finally came up with was to import an updated MOF file to include the BitLocker Policy (Win32Reg_MBAMPolicy) class into the "Hardware Inventory" section of the Default Client Policy. Once the import is complete SQL also gets
the appropriate view created.
The instructions on how to create and import the MOF file can be found in the link below.
http://technet.microsoft.com/en-US/library/dn237295.aspx
Chris Keene
Product Specialist at Wave.

Sender CC for MS SQL 2005 Driver error invalid object name

Hello people,
can some one help me with the following problem?
I'm trying to implement a JDBC to IDoc XI/PI scenario with PI 7.1.
In RWB CC monitor i'm getting the following error : "Database-level error reported by JDBC driver while executing statement 'SELECT * FROM SAP_SALES_TRANS_PAYMENTS WHERE TRANSFERRED_FLAG='0''. The JDBC driver returned the following error message: 'com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'SAP_SALES_TRANS_PAYMENTS'.'. For details, contact your database server vendor".
Communication channel configuration:
JDBC Driver: com.microsoft.sqlserver.jdbc.SQLServerDriver
Connection: jdbc:sqlserver://<IP>:1433;databaseName=<DB Name>
Query SQL Statement is : "SELECT * FROM SAP_SALES_TRANS_PAYMENTS WHERE TRANSFERRED_FLAG='0'"
Update SQL Statement: "UPDATE SAP_SALES_TRANS_PAYMENTS SET TRANSFERRED_FLAG='1' WHERE TRANSFERRED_FLAG='0'"
The name of the database is 'SAP_SALES_TRANS_PAYMENTS', is checked. Are the table name and/or table fields names key sensitive?
The MT definition is identical with the data base table.
Thanks Stefanos

Hello,
this issue is solved now.
The problem was in the name of the database table. The Database was created for more then one
company codes (by an other partner company ) and the full/right name in the query is
SELECT * FROM dbo.<company_code>$SAP_SALES_TRANS_PAYMENTS WHERE TRANSFERRED_FLAG='0'
Best regards
Stefanos

Transport user error: invalid object name while starting CMS in CCM

Hi Experts,
        I'm not able to start the CMS in CCM.It was working fine. Suddenly it went down due to some data base access failure. After that Iu2019m not able to start the CMS.
Kindly find the event viewer error and information.
Error: The root server reported an error Initialization Failure.
Error: Failed to register object..   Reason: Transport user error: invalid object name..
Information: Central Management Server stopped
      Could you please tell me how to start the CMS in CCM? Since I can able to setup CMS Database and audit database successfully.
Regards,
Sridharan

Hi ,
        Thanks for the response.I have trace the CMS.I found some error in log file.any idea on the following errors,
trace message: CNSClientManager::VerifyConnection() : search fails(37) - Transport user error: object with the specified name not found.
trace message: CNSClientManager::VerifyConnection() : Failed to query for APSs. Empty cluster list returned.
trace message: TheAPSServer::RegisterApsInNameServer: Fail to register the current APS(Transport user error: invalid object name.)
trace message: CNSClientManager::ClusterInfo::InvalidateAPS: Removing APS from m_ActiveMembers and adding to m_InactiveMembers
trace message: SIServerController:run: Fail to initialize or uninitialize. Reason is The root server reported an error Initialization Failure.:
Regards,
Sridharan

Profiler bug? (Invalid object name '#Results'.)

Hi. I've been using SQL Server Profiler to look for any "Exception" events, across any databases, etc.
Despite no issues from SSMS, I notice that the error message "Invalid object name '#Results'." shows up in Profiler when I run the following example queries (either ad-hoc or stored procedure):
CREATE TABLE #Results (myDate datetime)
INSERT INTO #Results(myDate) SELECT getdate()
SELECT * FROM #Results
DROP TABLE #Results
or
SELECT getdate() AS myDate INTO #Results
SELECT * FROM #Results
DROP TABLE #Results;
I'm all for standards... is there a way to re-write the query to prevent Profiler from catching a false-positive Exception?

To add on Stefan's comment about deferred name resolution, remember that Profiler/SQL Trace (as well as Extended Events) expose internals of SQL Server operation that are not otherwise visible. An understanding of SQL Server architecture and internals
is sometimes needed to properly interpret the results.
Dan Guzman, SQL Server MVP, http://www.dbdelta.com

Extended Events exceptions: Invalid object name '#x'

We have recently begun using Extended Events in SQL Server 2012. I noticed something that I don't understand and haven't found an explanation for. There seem to be a lot of exceptions logged for "Invalid object name '#x'", where #x is any temp
table name. This includes ones like "Invalid object name '#tmp_sp_help_category'", which is not even a table in our code.
This does not seem to happen consistently, but I have repro'd it several times. Each time there is no error shown in Management Studio. It happens on alters of stored procedures that use temp tables as well as when they are run. It happens even for a script
as simple as the one below, which logs an exception saying "Invalid object name '#x'" and indicating that it has a severity of 16.
Has anyone run across this? I am guessing these are not exceptions that should actually be logged, but then again there might be times when a temp table really is missing, so we can't just ignore them all.
Thanks,
Ron Rice
create table #x(x1 int)
select * from #x
Ron Rice

The #tmp_sp_help_category table is associated with SSMS Activity Monitor:
http://blogs.msdn.com/b/grahamk/archive/2009/10/20/troubleshooting-sql-server-management-studio-with-sql-profiler-and-debugging-tools-part-1.aspx
You may consider to report at Connect:
https://connect.microsoft.com/SQLServer
I am moving it to Tools.
Kalman Toth Database & OLAP Architect
SELECT Video Tutorials 4 Hours
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

Unable to access the data from Data Management Gateway: Query timeout expired

Hi,
Since 2-3 days the data refresh is failing on our PowerBI site. I checked below:
1. The gateway is in running status.
2. Data source is also in ready status and test connection worked fine too.
3. Below is the error in System Health -
Failed to refresh the data source. An internal service error has occurred. Retry the operation at a later time. If the problem persists, contact Microsoft support for further assistance.
Error code: 4025
4. Below is the error in Event Viewer.
Unable to access the data from Data Management Gateway: Query timeout expired. Please check 1) whether the data source is available 2) whether the gateway on-premises service is running using Windows Event Logs.
5. This is the correlational id for latest refresh failure
is
f9030dd8-af4c-4225-8674-50ce85a770d0
6.
Refresh History error is –
Errors in the high-level relational engine. The following exception occurred while the managed IDataReader interface was being used: The operation has timed out. Errors in the high-level relational engine. The following exception occurred while the
managed IDataReader interface was being used: Query timeout expired.
Any idea what could have went wrong suddenly, everything was working fine from last 1 month.
Thanks,
Richa

Never mind, figured out there was a lock on SQL table which caused all the problems. Once I released the lock it PowerPivot refresh started working fine.
Thanks.

Powerpivot Report 2010 - OLE DB or ODBC error: Query timeout expired; HYT00

0
I have report already developed by someone in powerpivot 2010 and deployed to sharepoint in powerpivot gallery library. The data source for this report is SQL Server 2008 r2. I have set the refresh options in sharepoint to run after business hours during
week end. When I check the refresh history it shows this error message "OLE DB or ODBC error: Query timeout expired; HYT00. An error occurred while processing the 'xxx' table. The current operation was cancelled because another operation in the
transaction failed..
I have tried to run the "Also refresh as soon as possible " just to check but same error message is shown.
This is the detailed error message details:
03/02/2014 21:06:55 03/02/2014 22:08:15 01:01:20 Failed
OLE DB or ODBC error: Query timeout expired; HYT00. An error occurred while processing the 'xxx' table. The current operation was cancelled because another operation in the transaction failed
Could anyone guide me on this issue? Truly appreciate your help in advance.

Hi asritha,
I would suggest you take a look at the following articles regarding how to configure PowerPivot data refresh in SharePoint Server:
Configure and Use Stored Credentials for PowerPivot Data Refresh:
http://technet.microsoft.com/en-us/library/ee210671(v=sql.105).aspx
Configure and Use the PowerPivot Unattended Data Refresh Account:
http://technet.microsoft.com/en-us/library/ff773327(v=sql.105).aspx
Note: Please ensure that the account have sufficient permission access to your data source.
In addition, please elaborate your PowerPivot data soure with more detail. If you are using SSAS cube, please try to increase "ExternalConnectionTimeout" property default value to see if this helps. Here is the similar thread for your reference,
please see:
http://social.technet.microsoft.com/Forums/en-US/35b26c06-9e6d-41e5-ae44-bfb1233510ac/ssas2008-ole-db-error-ole-db-or-odbc-error-query-timeout-expired-hyt00?forum=sqldatamining
Regards,
Elvis Long
TechNet Community Support

Unknown SQL Exception 208 occurred. Additional error information from SQL Server is included below.Invalid object name 'Webs'.

SP 2013 Server + Dec 2013 CU. Upgrading from SharePoint 2010.
We have a web application that is distributed over 7-8 content databases from SharePoint 2010. All but one database are upgradable. However, one database gives:
Invalid object name 'Webs'.
while running Test-SPContentDatabase or Mount-SPContentDatabase.
EventViewer has the following reporting 5586 event Id:
Unknown SQL Exception 208 occurred. Additional error information from SQL Server is included below.Invalid object name 'Webs'.
After searching a bit, these links do not help:
http://social.technet.microsoft.com/Forums/sharepoint/en-US/fd020a41-51e6-4a89-9d16-38bff9201241/invalid-object-name-webs?forum=sharepointadmin
we are trying PowerShell only.
http://blog.thefullcircle.com/2013/06/mount-spcontentdatabase-and-test-spcontentdatabase-fail-with-either-invalid-object-name-sites-or-webs/
In our case, these are content databases. This is validated from Central Admin.
http://sharepointjotter.blogspot.com/2012/08/sharepoint-2010-exception-invalid.html
Our's is SharePoint 2013
http://zimmergren.net/technical/findbestcontentdatabaseforsitecreation-problem-after-upgrading-to-sharepoint-2013-solution
Does not seem like the same exact problem.
Any additional input?
Thanks, Soumya | MCITP, SharePoint 2010

Hi,
“All but one database are upgradable. However, one database gives:
Invalid object name 'Webs'.”
Did the sentence you mean only one database not upgrade to SharePoint 2013 and given the error?
One or more of the following might be the cause:
Insufficient SQL Server database permissions
SQL Server database is full
Incorrect MDAC version
SQL Server database not found
Incorrect version of SQL Server
SQL Server collation is not supported
Database is read-only
To resolve the issue, you can refer to the following article which contains the causes and resolutions.
http://technet.microsoft.com/en-us/library/ee513056(v=office.14).aspx
Thanks,
Jason
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Jason Guo
TechNet Community Support

Error [hyt00] [microsoft][odbc sql server driver] query timeout expired

I have the below network setup:-
1. Its a simple network at my father's office at a small town called Ichalkaranji (District - Kolhapur, Maharashtra).
2. We are using private network range 192.168.1.xxx with two Windows Server 2003 Enterprise Edition with SP2 licensed copies and 15 local Windows 7 clients who are only using Server A.
3. The network is having a TP-Link Braodband Router Connected to internet with the IP 192.168.1.1.
4. Both there Windows Server 2003 Enterprise Edition with SP2 are running separate SQL Server 2005 Express with Advanced Services, you can treat them as Server A (Problematic Server with IP of 192.168.1.2)
and Server B (this is not having any issue with IP of 192.168.1.3).
5. Server A is also being used by 6 Remote users from our Kolkata office using DDNS facility through the NO IP client software which installed separately on both the servers. Kolkata remote users
do not use OR access the Server B.
6. Server B is being used by only 2 Remote users from our Erode office (Under Salem District, Tamilnadu) using DDNS facility through the NO IP client software which installed separately on both
the servers. Erode remote users do not use OR access the Server A.
7. The front end application which running separately on both the servers have been developed in VB by a local vendor at Ichalkaranji (District - Kolhapur, Maharashtra).
8. Both Servers are having the same database structure in terms of design and tables format. Only difference is that both the servers are being used separately.
9. This error OR problem is only related to Server A, where on the clients we get the message "error [hyt00] [microsoft][odbc sql server driver] query timeout expired" every now and then.
10. We have to frequently reboot the server whenever we get this message on the client machines. May be after rebooting every thing works perfectly for 2 hours / 5 Hours / may be one full day but
the the error will come back for sure.
11. Current Database back up size on Server A is around 35 GB and take around 1 hour 15 minutes daily to take the back up.
12. Current Database back up size on Server B is around 3 GB and take around 5 to 10 minutes daily to take the back up.
13. One thing I have noticed is that when ever we reboot Server A, for some time sqlsrvr.exe file will show memory usage of 200 to 300 MBs but it will start using slowly, what i understand is that
this is the way SQL Server works.
14. Both the Servers are also running Quick heal Antivirus Server Edition separate licensed copies also.
15. Server B is also running Tally ERP 9 Licenses copy which is being used locally by 15 users of Ichalkaranji (District - Kolhapur, Maharashtra) same users
Can any one help to resolve this issue. Any help will be highly appreciated.

The error message "query timeout expired" occurs, because by default many APIs, including ODBC only waits for 30 seconds for SQL Server to send any output. If no data has been seen for this period of time, they tell SQL Server to cancel execution
and return this error to the caller.
This timeout could be seen as a token that the query is taking too long time to execute and this needs to be fixed. But it can also be a pain in the rear parts, if you are content with a report taking five minutes, because you only run it once a day.
The simplest way to get rid of the error is to set the timeout to zero, which means "wait forever". This is something your vendor would have to do. This may, however, not resolve the problem, as the users may just find that the application is hanging.
To wit, there are two reasons why the query takes more than 30 seconds to complete. One is that there is simply that much work to do. This can be reduced by adding indexes or by doing other tuning, if the execution time is not acceptable. The other possibility
is blocking. That is, there is a process blocking this query from completing. This is much more likely to require attention.
It is not clear to me, whether the vendor has developed the database part as well. In this case, you should probably call the vendor's support desk to have them to sort this out.
Finally, I am little puzzled. You say that you are using Express Edition, but one of the databases is 35 GB in size. 35 GB is far above the limit for Express Edition.
Erland Sommarskog, SQL Server MVP, [email protected]

Query timeout expired and Invalid object name

Similar Messages

Maybe you are looking for