Error -1073807339 Hex 0xBFFF0015 Timeout expired before operation completed

Hi,
I am getting the Error -1073807339 Hex 0xBFFF0015 Timeout expired before operation completed message box but unlike many users that seemed to have a similar problem, it doesn't happened systematically... I am getting the message box error at random on a measurement and then it just works back fine, until the next time it happens again during a continuous measurement acquisiton.
I am working with a HP 34970A, plugged to the pc with a Agilent 82357A USB to GPIB and LabVIEW 2012 sp1. MAX is up to date, so is the I/0 Libraries of Keysight. Drivers are all installed and updated, Communication with IEEE 488 is enable in the I/0 Libraries, passport tullip also in NI VISA through MAX. I run a small VI that should make a continuous acquisition of four temperature using PT strobes plugged to the HP 34970A and graph them, also writting them on a Excel like document. The waiting time between two measurement is set at first by users. To take the measurment, I am runing an adaptated VI from the HP 34970A drivers. I think the problem comes from my VI's structures but I can't find it myself. I am also very surprised that it actually does work fine most of the time and just randomly crash in a loop...
I attached the VIs if needed.
I hope I was clear enough and that you might have an idea to help me fix this problem.
Thank you in advance.
Attachments:
Main_VI.vi ‏17 KB
Agilent 34970 Temp Scan.vi ‏36 KB

Is there someone here to help me?

Similar Messages

KE6485 Initialize.vi ERR Driver Status: (Hex 0xBFFF0015) Timeout expired before operation completed.

I am trying to get a reading from the KE6487, but I am receiving the following error.
"KE6485 Initialize.vi<ERR> Driver Status: (Hex 0xBFFF0015) Timeout expired before operation completed."
The driver I download for this device is KE6485, but is also compatible for KE6487. Therefore I think it should not be a problem.
I have attached the VI I'm using for your consideration.
Please advice, thank you for your time
Attachments:
Capture.PNG ‏5 KB
Capture 1.PNG ‏21 KB
KE6485_ZeroChk_LV6.vi ‏45 KB

How are you communicating? GPIB? Are you sure you have the correct address. Can you send an IDN command with MAX? Does MAX see the instrument?
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

VISA: (Hex 0xBFFF001D) The specified attribute is not defined or supported by the referenced resource and VISA: (Hex 0xBFFF0015) Timeout expired before operation completed signal recovery

I am trying to control an HP 8350B sweep oscillator. I have an Agilent PCI-GPIB card installed on my computer and have set it up to run with labview. I installed NI VISA, followed by Agilent IO libraries and activated the Tulip passport in NI MAX.
I tried turning on the "enable agilent GPIB cards for 488 programs" in Agilent IO libraries and checking the VISA test panel for WRITE and READ, but I get the timeout error: (Hex 0xBFFF0015) Timeout expired before operation completed signal recovery
On moving to labview, when I configure the VISA Serial it gives me this error
Error -1073807331 occurred at Property Node (arg 2) in VISA Configure Serial Port (Instr).vi->8350_VISA.vi
and the possible reason is
VISA: (Hex 0xBFFF001D) The specified attribute is not defined or supported by the referenced resource.
Subsequently on removing the VISA Serial, I get errors in Write and Read with the possible reason being
VISA: (Hex 0xBFFF0015) Timeout expired before operation completed.
Help !!
Attachments:
HP-8350B_VISA.vi ‏16 KB

Moving to LabVIEW makes no sense if you get a timeout error in the VISA test panel and doing any sort of serial configuration makes even less sense. What query did you use with the test panel? Did you confirm it exists in the manual? Did you enable GPIB on the instrument?

Reading COM : VISA: (Hex 0xBFFF0015) Timeout expired, before timeout (10 Sec) is over!

I read ASCII data from COM1 all day long, 4 string sections within 34 Char, write to an ASCII-CSV-file and if app is started read old data to display in variable time resolutions the data.
Is there any example-app near to this?
I am completely new to LabView.
I started with Basic2Port serial read write, getting above timeout message before specified timeout is over.
Usually my data comes every 5-8 seconds from an oil quality measuring sensor.
best regards
Frank from Achenbach Buschhütten GmbH, manufacturer of rolling mills

Hello Frank,
Here are some further examples you might test with:
Serial Communication - Advanced Serial Write and Read
Sending and Receiving Serial Commands using VISA
Serial Communication for LabVIEW 6.1
Most of all serial communication problems are due to wrong port settings, so pleasedoublecheck cour serial configuration.
Here is a good knowledge base for troubleshooting serial communications:
Ingo Schumacher
Systems Engineer Sound&VibrationNational Instruments Germany

Timout expired before operation completed VI_ERROR_TMO

Hi everybody,
My code is in Vb .Net and i use VISA COM Lib 3.0 to communicate with GPIB instruments.
But sometimes when i write some string on gpib, i've got the VI_ERROR_TMO error, whereas before the write operation was successfull !
any ideas ?
Thanks for your ask !

Hey PyroaLAT,
I have a few thoughts on why this might be happening. If you changed to a different computer it might take longer to get the information or if there is additional traffic. I would suggest changing the VISA timeout to a larger value to see if that fixes the problem.
As a side note, I would not recommend using VISA COM with .NET. NI has a native .NET class for VISA that doesn't use COM. The .NET assemblies for VISA are much better and faster in .NET then using COM.
The VISA for .NET is included with Measurement Studio 7.0 or on the recent Driver CD.
I hope this helps out.
JoshuaP
National Instruments

ERR Driver Status: (Hex 0xBFFA2003) Max Time exceeded before operation completed. (TEK DPO2014)

Hi NI.
I'm trying to aquire signals from an Tektronix DPO2014 oscilloscope using Labview SignalExpress.
I have downloaded and installed the appropriate driver (at least I think )) : tkdpo2k using NI download station.
I run an ethernet connection and I do see the device in MAX, however im not quite sure if I have configured the IVI driver sessions correctly.
Anyway, when I open Signal Express, and select "IVI scope aquire" I can select my device under "resource descriptor" and the appropriate driver under "Instrument driver". I then turn on my Oscilloscope, tune in the machines tachogenerator, which is the signal the oscilloscope is to measure, and then select "autosetup" The sinosoidal waweform shows up on the oscilloscope and in SignalExpress, it is only done once. I then try and run the program and the error message accurs:
Timeout.
<ERR>Driver Status: (Hex 0xBFFA2003) Max Time exceeded before operation completed.
Is the problem regarding problems with triggertime or write/read problems with the TCP/IP connection?
What can I do to fix this problem?
Best Regards
Danny Joergensen
University of Aalborg Denmark
Attachments:
MAXscreenshot.png ‏265 KB
device.png ‏320 KB

How are you communicating? GPIB? Are you sure you have the correct address. Can you send an IDN command with MAX? Does MAX see the instrument?
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

2008 r2 Copy Database Wizard Error code 0x80004005 (login timeout expired).

While on copy database wizard, step Configure the package I
get this error:
while trying to find a folder on sql an ole db error was encountered with error code 0x80004005 (login timeout expired).
If I try to run it any way, I got the following in the Execute stage:
the job failed. check the event log on the destination server for details
In the destination server, job history:
Message
Executed as user: WORKGROUP\servername$. Microsoft (R) SQL Server Execute Package Utility Version 10.50.1600.1
for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 3:26:57 PM Could not load package "package name omitted" because of error 0xC0014062. Description: The LoadFromSQLServer method
has encountered OLE DB error code 0x80004005 (Login timeout expired). The SQL statement that was issued has failed. Source: Started: 3:26:57 PM Finished: 3:27:44 PM Elapsed: 47.83 seconds. The package could
not be loaded. The step failed.
I check the job permission with the integration service connection. try with default and with db_ssisadmin.
other info:
Source: Other SQL Server Version, Microsoft SQL Server Enterprise Edition , Build 1617, Microsoft Windows NT 6.0 (6002) NT INTEL X86
Destination: Other SQL Server Version, Microsoft SQL Server Data Center Edition (64-bit) , Build 1600, Microsoft Windows NT 6.1 (7601) NT
x64 Using SMO online transfer

Hi kexinger,
This issue might be caused by the insufficient permission for the SQL Agent account, please check the SQL Agent service account has sufficient permissions to the various folders. For detail information, please take a look at the following article:
http://mattsql.wordpress.com/2014/01/06/quick-tip-could-not-load-package-xxx-because-of-error-0xc0014062/
If you have any feedback on our support, please click
here.
Elvis Long
TechNet Community Support

Error -1073807339 when using IVI (setup in MAX) to initialize instrument

I'm using LabVIEW 2014 and the most recent version of the Measurement & Automation Expert (MAX) to communicate with an Agilent 33500B series function generator with IVI drivers on a Windows 8.1 computer. (I also see this problem when trying to communicate with an Agilent oscilloscope). I've used the MAX to create an IVI logical name and tied the name to the appropriate driver session following the instructions in: http://www.ni.com/white-paper/4594/en/. In LabVIEW, I have created the IVI instrument, tied it to the appropriate logical name, initialize the instrument, and then close the session. When I run this program, the Initialization block runs (resetting the parameters on the function generator) AND THEN I get the following error:
"Error -1073807339 occurred at IviFgen Initialize With Options.vi
Possible reason(s):
Primary Error: (HEX 0xBFFF0015) TImeout expired before operation completed.
Complete call chain:
IviFgen Initialize With Options.vi
IviFgen Initialize.vi
<myfilename>.vi
I read in the documentation that I should not simultaneously initialize with options in LabVIEW and in MAX, so I am using the Initialize block which still calls Initialize With Options. The same error occurs when I:
1. Uncheck all the options in MAX and run the code
2. Uncheck all the options in MAX and replace the LabVIEW Initialize block with Initialize With Options and run the code
3. Add a Wait block between the initialization and the close blocks and run the code.
However, I am able to communicate with the function generator when I use the VISA Test Panel (opened in the MAX) and send it a VISA command. I am also able to communicate with the function generator if I use the VISA I/O blocks instead of the IVI blocks in LabVIEW.
Is it really a timeout issue? If so, how do I change the timing? If not, what is going on?
Thanks.

sagha wrote:
According to the MAX they are correct (IVI driver for the Agilent 33519B downloaded from the NI website). When I run the IVI Initialize block any frequency, amplitude, offset, etc. settings on the function generator are reset to the default values. So, something is being sent to the instrument.
However, I've also tried adding the General Error Handler block right after the Initializaiton block to cancel the -1073807339 error. Then, I add the IviFgen Configure Standard Waveform [STD] block to set the function generator frequency. The program throws an error that looks like a resource problem:
"Error -1074130544 occurred at IviFgen IVI Error Converter.vi
Possible reason(s):
The session handle is not valid.
Complete call chain:
IviFgen IVI Error Converter.vi
IviFgen Configure Standard Waveform [STD].vi
<myViName.vi>
What could be the reason for an invalid session handle? I've followed the NI tutorials on setting up IVI instruments in MAX and in LabVIEW.
Okay, this is new information. Nothing in your previous posts mention that the initialztion did anything at all besides return the timeout error. The invalid session handle is because you closed the session.
I'm having trouble following your descriptions.
Bill
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

Error -1073807339

Hello,
I am new with Labview and I am currently trying to connect a Lecroy HDO6034 oscilloscope via USB to perform a data acquisition using a NI driver.
I can see in NI MAX that the scope is connected to the computer but when I try to use a driver I get this error message :
Error -1073807339 occurred at VISA Clear in LeCroy Wave Series.lvlib:Initialize.vi->LeCroy Wave Series Acquire Waveform.vi
Possible reason(s):
VISA: (Hex 0xBFFF0015) Timeout expired before operation completed.
I looked it up online but it did not help me to resolve the problem.
Also when I go in the Visa Test Panel in the USB Control (input/output) I get this in return data :
USB Control In
wIndex: 0x0
wValue: 0x0
bmRequestType: 0x80
bRequest: 0x0
wLength: 0x0
Error
VISA: (Hex 0xBFFF0078) La valeur de certains paramètres n'est pas valide (ces paramètres ne sont pas connus).
Is someone capable of helping me resolve this ?
Thank you..

Hello,
A time out error is saying the scope did not respond to something. (Or, you have tried to read something from it when there is nothing there to read).
The error you are getting from the VISA tool is because you are not using it correctly.
Go to the "Basic I/O" tab and hit the "Query" button and you will see the scope respond to the "*IDN?" query that is there by default:
i.e. Not this:
Instead, use this:
Regards,
Leonard Brown
Applications Engineer
Teledyne LeCroy
1-800-553-2769

Wavetek 9100 - Error 1073807339

Hi my name is Said and I work in the National Institute of Industrial Technology of Argentina, in a calibration lab. We have a Wavetek 9100 Calibrator, Agilent 34401A Digital Multimeter and a NI GPIB IEEE-488-2 board. I have a problem with the Calibrator driver, in the transition from 90 V to 110 V in the DC and AC Voltage the instrument starts to ring an alarm and the program shows me the follow message: "Error -1073807339 occurred at VISA Read in wt9100 Error Query.vi->wt9100 Configure Output State.vi->wavetek multipoint VCC con array desde txt modificado 1.vi" and "Possible reason(s):
VISA: (Hex 0xBFFF0015) Timeout expired before operation completed."
Can you help me?
Thanks.
Attachments:
wavetek multipoint VCC con array desde txt modificado 1.vi ‏161 KB

Hi Sirs,
Please anyone can help me regarding error message on WAVETEK 9100; The unit is in stock for almost 2 years and it was owned by my company before, and it was closed now, and then when i started to operate the unit, the unit display reads "Selected test has failed number of failures 8" then all keyboard or button are all in active or not functioning and nothing happens on the display, it always hanged. What will i do, the manual says no detailed. Please help me on my problem.
Thanks and Regard to everyone.
Thanks and regards,
JOHN MARK

What causes the VISA timeout error 1073807339?

I'm getting this error while using a HP audio analyzer. The error also says "Timeout expired before operation completed." Can anyone give me any info on this?

Hi
Try increasing your timeout value. Check this link too: http://www.ni.com/support/labview/visa/verr2.htm
Hope this helps
Regards,
Luca

VISA: (Hex 0xBFFF003E) Could not perform operation because of I/O error

Hello
I'm trying to communicate with a device which have to be tested with my application. So I send it a command to initiate the device to send me back some values. This values are sended continously with a baud rate of 57600.
I create a VI to test this communication but I always get the error:
VISA: (Hex 0xBFFF003E) Could not perform operation because of I/O error
I have googled for this thread, but all the described solutions didn't solve my problem (ex. Set Buffer Size to 48, Various Byte Count Values for the VISA Read function, etc.).
Note: the VI works properly in the LabView 6.1! I have tested. I also tried to receive the Data with a Termial programm (works fine). But another COM Port (on an USB Serial converter) shows me the same Error.
I just updated to Visa 3.4.1, but no success
LabView 8.0.1

Yeah it works
of course buffer to 4096 and mask to 48
I added a Flush I/O buffer (mask 16) before reading from Visa (problem was to read data).
And suddenly it works fine.
I can't reproduce where the error exactly was. Could it be possible that the RX buffer was already full
at the time I would to read from Visa or at the time the COM port received data? There are some questions to find out:
how does LV handle the buffers? will the buffers be cleared if LV starts? when does LV flushes the
buffers?
thx

Prevent a rs232 crash when "operation completed succesfully"

Dear all,
A certain test set-up should run for long times (months) and makes good use of RS232 comunication (over USB). Data rates are not high, but frequent, to four different devices.
Very occasionally the application crashes (in debug mode, running from CVI, not as stand-alone application).
It crashes in the ComWrtByte function, with error code -1, and CVI reports:
NON-FATAL RUN-TIME ERROR: "c:\FlexHeadControl\Relay_RLY08.c", line 105, col 9, thread id 0x00000ABC, function id 1: Library function error (return value == -1 [0xffffffff]). The operation completed successfully.
Well, if it completed succesfully anyway, why doesn't it continue to run?
I wonder if there is a way to handle this very occasional error, such that the application can continue (after some apropriate error handling) without manual interruption.
The program crashed on the first of the following two lines (which have been executed before hunderds of times):
ComWrtByte(device[iB], byte);
ComWrtByte(device[iB],13);
How does error handling work? Will it prevent crashes if I follow the error handling suggestions by CVI-help:
int ret = 0;
ComWrtByte(device[iB], byte);
ret = GetRS232Err();
if (ret<0)
//error handling (for example resending, or reconnecting)
Will running in normal mode (as a .exe) instead of debug mode, outside of CVI SDK work?
I ask this since the error occurs very infrequent but may still ruin an experiment of months...
Many thanks for any explanations, tips and programming examples!
Karel

First of all, a return value of -1 means "Unknown system error". The operation completed with errors, so it's good to have a warning. A negative value always indicates an error, as you can see in the help.
Dealing with the popup error message is wuite simple: go to Run >> Break On menu item and deselect "Library errors" item. With this, the popup message won't show any more, but you will need to add the proper error handling based on the return code from the function like you have already shown in your post.
Proud to use LW/CVI from 3.1 on.
My contributions to the Developer Zone Community
If I have helped you, why not giving me a kudos?

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.

Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. This failure occured while attempting to connect to the Principle server.

We are using SQL Server 2012.
Every now and then, when we execute the below stored procedure INSERT_INTO_MYTBL, we got the below error, and it returned @ID = 0.
"Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
This failure occured while attempting to connect to the Principle server."
What causes this error, and how can we fix it ?
Thank you.
create procedure INSERT_INTO_MYTBL
@ID int output,
@Order varchar(50) = NULL,
@ACCOUNT varchar(20) = NULL
AS
DECLARE @Success int, @TryNr int, @ErrMsg varchar(500), @ErrNumber int, @expected_id int;
SET @Success = 0;
SET @TryNr = 1;
SET @ErrMsg = ''
WHILE @Success = 0 AND @TryNr <= 3 and @ErrMsg = ''
BEGIN;
BEGIN TRY;
BEGIN TRANSACTION;
retry:
BEGIN TRY;
SELECT @expected_id = ident_current('myTbl') + 1
SELECT @order = @account + '-' + CAST(@expected_id AS varchar(50))
insert into myTbl
([Order],ACCOUNT)
values
(@Order,@ACCOUNT)
END TRY
BEGIN CATCH;
SELECT @ErrNumber = ERROR_NUMBER()
IF @ErrNumber = 2627
BEGIN;
GOTO retry
END;
ELSE
BEGIN;
SET @ErrMsg = '1.' + ERROR_MESSAGE() + ' ' + @order
RAISERROR (@ErrMsg, 16, 1);
END;
END CATCH
select @ID = SCOPE_IDENTITY()
IF @id <> @expected_id
BEGIN
UPDATE myTbl
SET [Order] = @ACCOUNT + '-' + CAST(@ID AS varchar(50))
WHERE ID = @ID
END
SET @Success = 1
COMMIT TRANSACTION;
END TRY
BEGIN CATCH;
ROLLBACK TRANSACTION;
SELECT @ErrNumber = ERROR_NUMBER()
IF @ErrNumber = 1205
BEGIN;
SET @TryNr = @TryNr + 1;
IF @TryNr > 3
RAISERROR ('Giving up after 3 consecutive deadlocks for %s', 16, 1,@ACCOUNT);
END;
ELSE
BEGIN;
SET @ErrMsg = '2.' + ERROR_MESSAGE() + ' ' + @order
RAISERROR (@ErrMsg, 16, 1);
END;
END CATCH;
END;

When the problem occurs, the stored procedure returns @ID = 0, which I think means the query
When the problem occurs, the procedure does not return anything. SQL Server was told to stop executing. Furthermore, unless you issue the command SET XACT_ABORT ON, SQL Server will not roll back any open transaction. Which is one more reason you should not
permit command timeouts.
As for why this procedure sometimes take a long time, I would primarily suspect locking. When this occurs (but before the timeout elapses!), you could use my beta_lockinfo to see if there is any blocking going on. You find it here:
http://www.sommarskog.se/sqlutil/beta_lockinfo.html
Erland Sommarskog, SQL Server MVP, [email protected]

Error -1073807339 Hex 0xBFFF0015 Timeout expired before operation completed

Similar Messages

Maybe you are looking for