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

Similar Messages

OLE DB or ODBC error: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied

Hi,
I have one client and one server. In both hosts I created an OS-user named User1.
The user have been given various role under the prefix SQLServer2005.
The default instance of SQL Server and instance (background-process) of
Analysis Service are also run under User1.
I connected via Management Studio to Analysis Service directly in the
server. I set the permission to access Analysis Service to Everyone.
This means everyone should be able to use Analysis Service. I have set
ODBC data source to the server. Testing was successful.
I created a project to create a cube. The tables are fairly small (total 300 MB, biggest one 290).
On project setting (created at client) I set the server host as
deployment target. I managed to deploy project when all I have are Data
Source and Data Source Views.
But on deployment I always failed. The errors remain the same, begins with
OLE DB error: OLE DB or ODBC error: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.; 08001.
I have tried 4 combinations of Impersonation :
(A) Use a specific username and password
* in which I supply User1 and the password of User1
(B) Use the service account
(C) Use the credentials of the current user
(D) Default
Why is this? The server does certainly exist. I think the error message is wrong.
I have seen 3 posting that seems related. One of them say the solution is giving the right impersonation, but gave no detail. About the privilege, User1 are granted the role of
SQLServer2005MSOLAP. What is the solution?
Thank you,
Bernaridho

I just had this problem and solved it by creating an alias in SQL Server Configuration Manager, as below:
Scenario: My SQL server is accessible from the internet under my.domain.com, and from itself at ServerName. But the local network can't see itself through the router at my.domain.com, so the deployed project is unable to process the cube, since that would
require Analysis Services to be able to see the SQL Server at my.domain.com, which it can't do.
So I changed the server in my project from my.domain.com to ServerName, and I created a local alias to ServerName in SQL Server Configuration Manager, under SQL Native Client 11.0 Configuration, Aliases. In my case, I pointed it to localhost port 1333, and
used SSH -L 1333:my.domain.com:1433, but I could have pointed the alias directly to the server, just as well. (Verifying... yes, that worked too, so you can forget SSH if you have no interest in it.)

OLE DB error: OLE DB or ODBC error: %1 is not a valid Win32 application

Hi,
I am creating the Cubes with couple of dimensions. My backend is Oracle. I can able to deploy the cube in my local machine which is running 32 Bit Windoes 7 OS. But when I try to deploy the cube in another server which is running Windows 2003 R2 64 bit OS,
returns "OLE DB error: OLE DB or ODBC error: %1 is not a valid Win32 application" this error. The driver whic I am using to connect the Oracel DB is "Native OLE DB\Oracle Provider for OLE DB". I have also installed the Oracle 10g 32 bit client in my machine.
Any solution for this issue?
Thanks,
Jeen

Hi Jeen,
What's the specific version of your SQL Server? Please try to install the latest Service Pack on 64bit box to see if this help.
How to obtain the latest service pack for SQL Server 2005:
http://support.microsoft.com/kb/913089
If you have any feedback on our support, please click
here.
Regards,
Elvis Long
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]

"....(-2147217871) Query timeout expired" -- Error in MS Dynamics RMS HQ Manager

When I go into the reports section of HQ Manager, then Quotes/Orders to search a purchase
order, once I start the search it times out with an error,
“The report data could not be loaded due to the following error (-2147217871) Query timeout
expired”
Is this due to .NET 30 second default timeout?
Thanks in advance - Roxy

How is this SSIS related?
Arthur
MyBlog
Twitter

SSAS Tabular : OLE DB or ODBC error : The Microsoft Access database engine cannot open or write to the file. It is already opened exclusively by another user, or you need permission to view and write it's data.; 3051.

Hi all, i'm trying to import a spreadsheet into a tabular model and getting this stupid error even though the impersonation account i'm using is an admin account with full access to the file. ANY IDEAS? I hate these stupid permission related issues!!!
Thanks for your help.

Hi, I know the post is old, but I'm having this problem and maybe you could eleborate a bit.
What are the steps to get this done?
What worked for me is to go to the Excel file, right click and add the MSOLAP user. But this is a manual process, I have many excel files. I don't want to do this to each one. Is there a way to do this in one go?
Thank you
Try creating a folder for all the files you want to import. Give the MSOLAP user permission to read that folder then copy your excel files in there.
However apart from prototypes I rarely do direct imports of Excel files. For any ongoing project I always stage them in a SQL Server table using SSIS. There are just too many things that can go wrong with Excel files, like people locking the file by leaving
it open. Or changing the file by adding extra columns or putting string values in numeric columns. I find that in SSIS I can build a lot more robust data flows to handle this sort of thing.
http://darren.gosbell.com - please mark correct answers

Odbc error in answer

Hi All,
I am unable to solve this issue for a week now.I am using oracle 11.2.0 client for 64 bit . I could import the tables and view data from rpd.The problem comes when I run the report from answer.I get ODBC error. I am accessing the obiee server and oracle client through remote desktop connection from my local machine and the database is located in different server. The obiee configuration is fine since I am able to view records from rpd(Obiee Admin).
When I run the report from Obiee 11g answer , I get the following error:
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 17003] Oracle gateway error: OCIEnvNlsCreate or OCIEnvInit failed to initialize environment. Please check your Oracle Client installation and make sure the correct version of OCI libraries are in the library path. (HY000)
I did copy tnsnames.ora to {Oracle_BI1}\network\admin directory & {oracle_common}\network\admin directory and Set up TNS_ADMIN to C:\OracleBI\Oracle_BI1\network\admin .I have checked the environment variables and it is correct. This issue is killing me. I have reinstalled oracle client too. Is it the obiee issue or any firewall or it is because I am using remote desktop??
Thanks,
Virat

ORACLE_HOME =C:/app/us1/product/11.2.0/client_1
PATH=C:/app/us1/product/11.2.0/client_1/bin
TNS_ADMIN=C:/app/us1/product/11.2.0/client_1/network/admin
CLASSPATH do not have the path
The result of TNSPINg
TNS Ping Utility for 64-bit Windows: Version 11.2.0.1.0 - Production on 16-AUG-2
012 16:48:09
Copyright (c) 1997, 2010, Oracle. All rights reserved.
Used parameter files:
C:\OracleClient11\product\11.2.0\client_1\network\admin\sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)
(HOST = 192.168.10.74)(PORT = 1521))) (CONNECT_DATA = (SID = nadev)))
OK (80 msec)
I used (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.10.74)(PORT=1521)))(CONNECT_DATA=(SID=nadev))) in connectionpool
How to create soft link (ln -s) ? I am not able to use this command cd /u10/app/orcladmin/oracle/OracleBI/server/Bin
ln -s $ORACLE_HOME/lib32/libclntsh.so.10.1 libclntsh.so.10.1
Thanks,
Virat

Query Timeout on stored procedure executed from Access 2010

I am trying to delete old jobs from a SQL 2008 R2 database. I created a stored procedure on the server that deletes all Jobs over 1 year old. The delete can take several minutes to run as it deletes record on several related tables. I am getting a error
"2147217871 - [Microsoft][ODBC SQL Server Driver]Query timeout expired". The query runs fine on the Server. I have tried setting Client timeout to 300 sec but it times out way before 5 min. I am not sure what else I
can do to fix this problem. I am hoping someone has seen this and figured out a fix.
Here is there code
Public Sub Cleanup_Database()
On Error GoTo CleanUp_Err
    Dim cmd As ADODB.Command
    Set cmd = New ADODB.Command
    ODBC_conn = "ODBC;Description=testbox2;DRIVER=SQL Server;" & _
                "SERVER=O2GMSAPPTEST\SQL122DEVL;Trusted_Connection=Yes;" & _
                "APP=Microsoft Office 2010;DATABASE=IMB_TraceData;StatsLog_On=Yes"
    cmd.ActiveConnection = ODBC_conn
    cmd.CommandType = adCmdStoredProc
    cmd.CommandText = "DataBase_Cleanup"
    cmd.Execute
CleanUp_Err:
    Dim i As Long
    Dim str As String
    str = ""
    For i = 0 To Errors.Count - 1
        str = str & Errors(i).Number & "-" & Errors(i).Description & " " & vbNewLine
    Next i
    If str = "" Then
        str = Err.Number & " - " & Err.Description
    End If
    MsgBox str, , "Trace Update"
End Sub


You didn't say how you were setting the client timeout, but this has worked for me in an adp.
'Temporarily increase query timeout, which is an application-wide setting
'CurrentProject.Connection.CommandTimeout = 60 'Too late to change this setting- no effect
Const cstrTimeoutOptionName As String = "OLE/DDE Timeout (Sec)"
Const clngTimeoutSecondsForQuery As Long = 300
strQueryTimeOutOriginal = Application.GetOption(OptionName:=cstrTimeoutOptionName)
Application.SetOption cstrTimeoutOptionName, CStr(clngTimeoutSecondsForQuery)
Paul

Dataset Timeout expired error in SSRS

I am pulling my hair out over these timeout errors in SSRS.
I am running SSRS 2012 in native mode on a Windows 2012 server. When I try to run and embedded dataset in my report it will continually timeout after 90 seconds no matter what I have the timeouts in the report or on the servers rsreportserver.config
file or the web.config file set to.
If I run Query Designer in the report and run the query all fields and the subset of data is returned without an issue in about 45 seconds. As soon as it tries to update the fields then it times out after 90 seconds.
What else can I check to get this working.
Below is what I am getting each time.
"Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding."

Hi Ronald,
According to your description, after you update the data in base tables, the error message "Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding." is thrown out when you run query
designer.
In rsreportserver.config file, the value of “DatabaseQueryTimeout” is passed to the System.Data.SQLClient.SQLCommand.CommandTimeout property. The value specifies the number of seconds after which a connection to the report server database times out. It works
on report server side.
Query time-out values are specified during report authoring when you define an embedded dataset. The time-out value is stored with the report, in the Timeout element of the report definition. So in your scenario, you should set the value of Time out in Dataset
Properties. Please refer to the screenshot below:
Reference:
Setting Time-out Values for Report and Shared Dataset Processing (SSRS).
If you have any question, please feel free to ask.
Best regards,
Qiuyun Yu

SCOM 2012 R2 installing on SQL 2012 SP1 - Error Code: 0x80131904, Exception.Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

Hi,
I am getting an issue during a SCOM 2012 R2 installation while creating the SCOM DataWarehouse database. Setup seems to timeout during creating the datawarehouse database. I can see all database files created in windows explorer on the SQL server before
setup rolls the SCOM install back.
Has anyone seen this issue before or know how to help resolve it?
Appreciate your help, below is the SCOM installation log:
Thanks
Marc
[13:27:27]: Always: :Creating Database: OperationsManagerDW
[13:35:28]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[13:43:28]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[13:51:29]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[13:59:30]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:07:30]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:15:31]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:23:31]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:31:32]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:39:32]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:47:33]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:55:33]: Error: :DB operations failed with SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:55:33]: Error: :StackTrace:   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.ExecuteNonQuery(SqlCommand sqlCommand, Int32& result)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.Execute[T](SqlCommand sqlCommand, SqlRetryPolicy retryPolicy, GenericExecute`1 genericExecute)
[14:55:33]: Error: :Inner Exception.Type: System.ComponentModel.Win32Exception, Exception Error Code: 0x80131904, Exception.Message: The wait operation timed out
[14:55:33]: Error: :InnerException.StackTrace:
[14:55:33]: Error: :Error:Failed to execute sql command. Setup has reached maximum retry limit.
[14:55:33]: Warn: :Sql error: 11. Error: -2. Error Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:55:33]: Error: :Exception running sql string
DECLARE @sql NVARCHAR(MAX);
SET @sql = 'CREATE DATABASE ' + QUOTENAME(@DatabaseName) + '
    ON PRIMARY(NAME=MOM_DATA,FILENAME=''' + REPLACE(@Filename, '''', '''''') + ''',SIZE=' + CAST(@Size AS VARCHAR) + 'MB,MAXSIZE=UNLIMITED,FILEGROWTH=' + CAST(@FileGrowth AS VARCHAR) + 'MB)
    LOG ON(NAME=MOM_LOG, FILENAME=''' + REPLACE(@LogFilename, '''', '''''') + ''',SIZE=' + CAST(@LogSize AS VARCHAR) + 'MB,MAXSIZE=UNLIMITED,FILEGROWTH=' + CAST(@LogFileGrowth AS VARCHAR) + 'MB)';
EXEC(@sql);: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:55:33]: Error: :StackTrace:   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.ExecuteNonQuery(SqlCommand sqlCommand, Int32& result)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.Execute[T](SqlCommand sqlCommand, SqlRetryPolicy retryPolicy, GenericExecute`1 genericExecute)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DBConfigurationHelper.DBConfiguration.RunSqlCommandsList(IEnumerable`1 sqlCommands)
[14:55:33]: Error: :Inner Exception.Type: System.ComponentModel.Win32Exception, Exception Error Code: 0x80131904, Exception.Message: The wait operation timed out
[14:55:33]: Error: :InnerException.StackTrace:
[14:55:33]: Always: :Failed to create and configure the DB with exception.: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Timeout expired. The timeout period elapsed prior to completion
of the operation or the server is not responding.
[14:55:33]: Always: :StackTrace:   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.ExecuteNonQuery(SqlCommand sqlCommand, Int32& result)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.Execute[T](SqlCommand sqlCommand, SqlRetryPolicy retryPolicy, GenericExecute`1 genericExecute)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DBConfigurationHelper.DBConfiguration.RunSqlCommandsList(IEnumerable`1 sqlCommands)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DWConfigurationHelper.DWConfigurationProcessor.RunAdminScripts(String sqlServerInstance, Nullable`1 port, String databaseName, Int64 dbSize, Int64 logSize, String dbPath, String logPath)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DWConfigurationHelper.DWConfigurationProcessor.ConfigureDataWarehouseDatabase(String sqlServerInstance, Nullable`1 port, String databaseName, Int64 dbSize, Int64 logSize, String dbPath,
String logPath)
[14:55:33]: Always: :Inner Exception.Type: System.ComponentModel.Win32Exception, Exception Error Code: 0x80131904, Exception.Message: The wait operation timed out
[14:55:33]: Always: :InnerException.StackTrace:
[14:55:33]: Error: :CreateDataWarehouse failed: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Timeout expired. The timeout period elapsed prior to completion of the operation or
the server is not responding.
[14:55:33]: Error: :StackTrace:   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.ExecuteNonQuery(SqlCommand sqlCommand, Int32& result)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.Execute[T](SqlCommand sqlCommand, SqlRetryPolicy retryPolicy, GenericExecute`1 genericExecute)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DBConfigurationHelper.DBConfiguration.RunSqlCommandsList(IEnumerable`1 sqlCommands)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DWConfigurationHelper.DWConfigurationProcessor.RunAdminScripts(String sqlServerInstance, Nullable`1 port, String databaseName, Int64 dbSize, Int64 logSize, String dbPath, String logPath)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DWConfigurationHelper.DWConfigurationProcessor.ConfigureDataWarehouseDatabase(String sqlServerInstance, Nullable`1 port, String databaseName, Int64 dbSize, Int64 logSize, String dbPath,
String logPath)
   at Microsoft.SystemCenter.Essentials.SetupFramework.InstallItemsDelegates.OMDataWarehouseProcessor.CreateDataWarehouse()
[14:55:33]: Error: :Inner Exception.Type: System.ComponentModel.Win32Exception, Exception Error Code: 0x80131904, Exception.Message: The wait operation timed out
[14:55:33]: Error: :InnerException.StackTrace:
[14:55:33]: Error: :FATAL ACTION: CreateDataWarehouse
[14:55:33]: Error: :FATAL ACTION: DWInstallActionsPostProcessor
[14:55:33]: Error: :ProcessInstalls: Running the PostProcessDelegate returned false.
[14:55:33]: Always: :SetErrorType: Setting VitalFailure. currentInstallItem: Data Warehouse Configuration
[14:55:33]: Error: :ProcessInstalls: Running the PostProcessDelegate for OMDATAWAREHOUSE failed.... This is a fatal item. Setting rollback.
marc nalder

Hi,
Based on the log, I recommend you use the following way to test SQL connectivity.
You can use a UDL file to test various connectivity scenarios, create a simple text file, rename the extension from TXT to UDL, fill out the necessary information on the connection tab then test the connection, and troubleshoot as necessary
if it fails to connect.
For more information, please review the link below:
The easy way to test SQL connectivity
http://blogs.technet.com/b/michaelgriswold/archive/2014/01/06/the-easy-way-to-test-sql-connectivity.aspx
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Crystal Reports 2010 shows error on 64 bit vista/7 machines

Hello,
 
I search the threads before posting my problem. I saw number of threads similar to this but none of them is pointing towards solutions to my problem. Thus decided to create new one. I tried various things listed in old post to solve my problem but no solution. I am listing below what I have already tried.
 
Following is my development environment: 
- OS windows XP 32 bit 
- MS Visual Studio 2010 
- Crystal Reports 2010 
- windows application with target framework 3.0 
- when i build solution for client i change target platform to x86 
 
My client machine 
1) 
- OS windows vista 64 bit 
- Crystal Reports for VS2010 Redist 64 bit 
2) 
- OS windows 7 64 bit 
- Crystal Reports for VS2010 Redist 64 bit 
 
On my development machine everything works fine. Only client machines having problem opening reports. I am having problem opening reports on client machines. I shows following error. My windows application runs fine but when we try to open reports it shows log4net error.
 
 
start error text----
 
 
The type initializer for 'CrystalDecisions.ReportSource.ReportSourceFactory' threw an exception. 
 
See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box. 
 
Exception Text ************** 
System.TypeInitializationException: The type initializer for 'CrystalDecisions.ReportSource.ReportSourceFactory' threw an exception. ---> System.TypeInitializationException: The type initializer for 'CrystalDecisions.Shared.SharedUtils' threw an exception. ---> System.IO.FileNotFoundException: Could not load file or assembly 'log4net, Version=1.2.10.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The system cannot find the file specified. 
File name: 'log4net, Version=1.2.10.0, Culture=neutral, PublicKeyToken=692fbea5521e1304'
 at CrystalDecisions.Shared.SharedUtils..cctor() 
 
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
 
 --- End of inner exception stack trace ---
 at CrystalDecisions.Shared.SharedUtils.GetFullTypeName(Type type)
 at CrystalDecisions.ReportSource.ReportSourceFactory..cctor()
 --- End of inner exception stack trace ---
 at CrystalDecisions.Windows.Forms.CrystalReportViewer..ctor()
 at BackOffice.frmReportViewer.InitializeComponent()
 at BackOffice.frmReportViewer..ctor()
 at BackOffice.mdiMain.vendorsListToolStripMenuItem_Click(Object sender, EventArgs e)
 at BackOffice.mdiMain.vendorsListToolStripMenuItem1_Click(Object sender, EventArgs e)
 at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
 at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
 at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
 at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
 at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
 at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
 at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
 at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
 at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
 at System.Windows.Forms.Control.WndProc(Message& m)
 at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
 at System.Windows.Forms.ToolStrip.WndProc(Message& m)
 at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
 at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
 at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
 at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
 
Loaded Assemblies **************
mscorlib
 Assembly Version: 2.0.0.0
 Win32 Version: 2.0.50727.4952 (win7RTMGDR.050727-4900)
 CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
 
BackOffice
 Assembly Version: 1.0.0.0
 Win32 Version: 1.0.0.0
 CodeBase: file:///C:/BO%20config%20removed/BackOffice.exe
 
System.Windows.Forms
 Assembly Version: 2.0.0.0
 Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
 CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
 
System
 Assembly Version: 2.0.0.0
 Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
 CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
 
System.Drawing
 Assembly Version: 2.0.0.0
 Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
 CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
 
CrystalDecisions.Windows.Forms
 Assembly Version: 13.0.2000.0
 Win32 Version: 13.0.1.220
 CodeBase: file:///C:/Windows/assembly/GAC_MSIL/CrystalDecisions.Windows.Forms/13.0.2000.0__692fbea5521e1304/CrystalDecisions.Windows.Forms.dll
 
CrystalDecisions.Shared
 Assembly Version: 13.0.2000.0
 Win32 Version: 13.0.1.220
 CodeBase: file:///C:/Windows/assembly/GAC_MSIL/CrystalDecisions.Shared/13.0.2000.0__692fbea5521e1304/CrystalDecisions.Shared.dll
 
CrystalDecisions.ReportSource
 Assembly Version: 13.0.2000.0
 Win32 Version: 13.0.1.220
 CodeBase: file:///C:/Windows/assembly/GAC_MSIL/CrystalDecisions.ReportSource/13.0.2000.0__692fbea5521e1304/CrystalDecisions.ReportSource.dll
 
JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
 
configuration 
 system.windows.forms jitDebugging="true" 
configuration 
 
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
 
end error text----
 
I am not using log4net in my windows application. As I know not directly. No log4net tag in config. Not even in publish file listing. 
I have Crystal Decisions.CrystalReports.Engine in my reference. 
 ReportSource 
 Shared 
 Windows.Forms 
 
I tried adding reference of log4net in my app and then tried deploying. slight modified error. Instead of not find the file it says not able to load and rest error part is same.
 
I have excluded all crystal dll from publish file list and tried.
 
I even updated cilent machine with Crystal Reports for VS2010 Redist 64 bit support pack 1.
 
I tried adding following in config but no result 
 startup useLegacyV2RuntimeActivationPolicy="true" 
 supportedRuntime version="v2.0.50727" 
 startup
and
 startup useLegacyV2RuntimeActivationPolicy="true" 
 supportedRuntime version="v4.0" 
 startup 
 
I found related to this in one of the thread. I am not sure but this could be the problem. what is the solution for it? 
In my development machine windows/assembly folder, there exist 2 log4net files 
Assembly Name - version - Processor Architect 
- log4net - 1.2.9.0 - blank 
- log4net - 1.2.10.0 - x86 
But in my client machine, there is only one log4net file. 
Assembly Name - version - Processor Architect 
- log4net - 1.2.10.0 - AMD64 
 
I have spend lot hours on it but no output. Any help or direction is appreciated. 
Thanks,
Edited by: Dhairya Tolat on Mar 21, 2011 8:13 PM

Hi deguri,
1. Are you going to sell the application(which embeds the crystal runtimes) to another company?
2. Is the application intended for users within your company?
If the answer to question 1 is a 'Yes', then you need to purchase the license.
If the answer to question 2 is a 'Yes', then you do not need the license.
Take a look at a question posted in response to the blog i referred to in my previous post. That is a typical scenario where license needs to be purchased.
We are product a client/server application in VS 2010 and would like to include Crystal Reports. The rendering/runtime would be on the server component. Our package is distributed to our clients and runs on their hardware. We would be producing the reports and shipping them with the software (i.e. no embedded designer).
Am I correct in understanding that we would need only a single SAP Developer Advantage license (~$2500 USD) and that would cover redistribution to all our our clients?
Thanks in advance!
CR for VS 2010 on Application Server
2011-06-15 14:18:50 Blair Wheadon Business Card [Reply]
Yes, you are correct.
I hope that clarifies things...
Deepu.

Answers report showing odbc error.

Hi,
We have OBIEE installed on linux. I ftp'd to the rpd from linux to the windows server and created a connectivity to another database and imported those tables and worked on necessary modifications. I ftp'd the modifed rpd back to linux. We stopped and started the services. I am able to see the changes in the rpd with those tables but it shows the following error. What might be the issue.
Odbc driver returned an error (SQLExecDirectW).
Error Details
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 17001] Oracle Error code: 12154, message: ORA-12154: TNS:could not resolve the connect identifier specified at OCI call OCIServerAttach. [nQSError: 17014] Could not connect to Oracle database. (HY000)
SQL Issued: SELECT Item."Brand Name" saw_0 FROM "GTM Reports" ORDER BY saw_0

user4683504 wrote:Odbc driver returned an error (SQLExecDirectW).
Error Details
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 17001] Oracle Error code: 12154, message: ORA-12154: TNS:could not resolve the connect identifier specified at OCI call OCIServerAttach. [nQSError: 17014] Could not connect to Oracle database. (HY000)
SQL Issued: SELECT Item."Brand Name" saw_0 FROM "GTM Reports" ORDER BY saw_0
Since you have created connection in windows machine,i guess you have not put TNS entry on linux box.Put the TNS entry for new database in tnsnames.ora file on linux platform and check the results.
Regards,
SAndeep

Oracle ODBC Error - Option Value Changed - What does it Mean and How to fix

We have an asp web report making calls to an oracle 8i database. It appears that we get the following error on regular basis for one particular report:
Microsoft OLE DB Provider for ODBC Drivers error '80040e31'
[Oracle][ODBC]Option value changed.
/FinalBilling/Report2.asp, line 49
When the web page is refreshed, it appears the error goes away. Any new call to the database from the web page will start with the error again though.
Other web pages seem to work ok with out error.
Did a number of google searches did not find anything definative that seemed to help.

These messages can be ignored. They are common but innocuous. There is nothing you need to fix.

OLE or COM Processing error : Too many fields defined

i have created a excel workbook format in data integrator and defined the fields in it, when i tried to run a simple job extracting data from spreadsheet , i am getting following error OLE or COM Processing error : <Too many fields defined>.
all i have in the spreadsheet is 18 rows and 35 columns of data, can any help how to solve this problem. i have used query transform for extracting and loading the data in to a table
Edited by: Rakesh Chittineni on Apr 1, 2010 3:45 AM

I have Solved the problem my friend suggestion.
The excel file i was trying to access is from WEBI report which was saved as .xls format and then then made some modifications to the spreadsheet.
What i did was i deleted the unused columns, i.e my spread sheet has data upto AQ column so i deleted remaining cells.
and while defining the excel file format i selected the option workbook and selected the proper sheet and in the other options i have chosen column range and also check the box ( extended range) now i could over come the error OLE or COM processing error
Edited by: Rakesh Chittineni on Apr 1, 2010 9:44 PM

PowerPivot report performance problem on Sharepoint

Hi everybody,
I have created a PowerPivot report based on SQL Server tables.
When I use this report on my computer the response time are really good.
I get data from two different table which are linked by an integer key in my model.
It means that in my pivot I chose my fields in two different "tables"
Let say I select 10 fields in one table and 2 in the other one
When I put it on the Sharepoint Server the report is not correctly loaded.
When I put calculated columns into my first table and use lookup to get the 2 fields from my second table the performance are far better and the report works on Sharepoint.
I don't understand why.
Any idea?
Thanks
Pete
P.S: I work on PowerPivot for Excel 2010 and SP 2010 Server

This is an issue my client is having at the moment. As of right now they are going through a MS ticket to resolve it. Will update when I hear more.
-Link

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

Similar Messages

Maybe you are looking for