The job was stopped prior to completion by (Unknown)

I'm getting the following intermittent error on a job:
The job was stopped prior to completetion by (unknown)
Any ideas as to what could be causing it?
2008 R2
John Schroeder

If you are running many Agent jobs at the same time, you are probably running into this problem.
http://support.microsoft.com/kb/824422
Tom I think your link is not applicable in this case.Neither version is SQL 2000 nor will be the OS.
So please dont edit the registry
John Can you check sql server errorlog .I agree with Visakh that somebody or some program is manually stopping the job.
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Similar Messages

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]

SSRS Error: The timeout period elapsed prior to completion of the operation or the server is not responding

Hi, I am using SQL Server 2008 R2 Stored Procedure as my dataset and running yearly sales report in SSRS 2008 R2. The weird thing is in SSMS the stored procedure does not take more than 10 seconds to retrieve data and the report also works
fine in BIDS, but from ReportServer if I were to pick an year from 1990 - 2014 they all work fine anything prior to 1990 either shows up fine or throws the below error.
SSRS Error:
An error has occurred during report processing. (rsProcessingAborted)
Query execution failed for dataset 'QueryDS'. (rsErrorExecutingCommand)
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. The statement has been terminated.
I checked ReportServerTemDb tables and no table seems to be really large to cause a problem. This report "KeepTogether" property is TRUE.
Thanks in advance.............
Ione

Was able to fix this with the help of
msdn documentation. The query dataset was set to 5 and this was somebody else's report I was fixing and I usually have my report template set to 0 so it took me a while to get there.
Ione

The import was stopped, an error occurred during the phase DDIC_ACTIVATION

Dear all,
When I import the SAP_BASIS support package SAPKB70019 , it appears the error as below :
The import was stopped, since an error occurred during the phase
DDIC_ACTIVATION, which the Support Package Manager is unable to resolve
without your input.
After you have corrected the cause of the error, continue with the
import by choosing Support Package -> Import queue from the initial
screen of the Support Package Manager.
The following details help you to analyze the problem:
     -   Error in phase: DDIC_ACTIVATION
     -   Reason for error: TP_STEP_FAILURE
     -   Return code: 0008
     -   Error message: OCS Package SAPKB70019, tp step A, return code
         0008
Notes on phase DDIC_ACTIVATION
In this phase the imported Dictionary objects are activated. This phase
can terminate due to the following reasons:
o   TP_INTERFACE_FAILURE: The tp interface could not be called.
o   TP_FAILURE: The program tp could not be executed. For more
     information, see the SLOG or ALOG log file.
o   TP_STEP_FAILURE: The tp step DDIC activation could not be performed
     successfully. To see the cause of the error in the activation log,
     choose Goto -> Log -> Queue.
     If you import two or more Support Packages in one queue, and you do
     not activate them in the correct sequence, activation errors may
     occur. In this case, the activation errors disappear when you repeat
     the activation run. To do this, choose Support Package -> Import
     Support Package Queue.
    A prerequisite of the Support Package Manager is that the Change and
    Transport System (CTS) is configured correctly. For more detailed
    information, read the online documentation available from Help -> SAP
    Library -> mySAP Technology Components -> SAP Web Application Server ->
    Change and Transport System .
    A list of the most important SAP Notes for Online Correction Support
    (OCS) is available in SAP Note 97620, which is updated regularly.
I have used se11 to avtive the domain SEFS_CRAWL_ALGORITHM , but the error still exist.
Hope anyone can help. Thanks!
B.R
Michael

P762713 wrote:>
> Hi ,
>
>     This is general issue now a days occuring in Support Packs .The only solution for this issue is to delete structure ::
>
> these were the structure deleted from system afterwards patches were installed successfully.
>
> /1PYXXFO/SAP_PAYSLIP_____L0001
> /1PYXXFO/SAP_PAYSLIP_____T0001
> /1PYXXFO/SAP_PAYSLIP
>
> /1PYXXFO/SAP_PAYSLIP_____L0020
> /1PYXXFO/SAP_PAYSLIP_____T0020
>
> You can do this via Tcode se11 .give these info in data type & in turn you have to delete 1PYXXFO/SAP_PAYSLIP also.This has solved my issue & after this support pack went fine.
>
> Thanks..
> Mohit
>
> Edited by: mohit gupta on Sep 23, 2009 9:15 AM
Hi, mohit
      I have tried to use the t-code se11 to delete the structures, but the system telled me that they are all not exist .
A part of the queue log as below:
   Field name KEY is reserved (Do not use structure as include in DB table)
   Field name PRIOR is reserved (Do not use structure as include in DB table)
   Field KEY: Component type or domain used not active or does not exist
   Exactly one field SPRAS of type LANG: Selection as text language possible
Nametab for table /1PYXXFO/SAP_PAYSLIP_____L0001 cannot be generated
   Enhancement category for table missing
   Enhancement category for include or subtype missing
   Field name KEY is reserved (Do not use structure as include in DB table)
   Field name PRIOR is reserved (Do not use structure as include in DB table)
   Field KEY: Component type or domain used not active or does not exist
   Nametab for table /1PYXXFO/SAP_PAYSLIP_____L0020 cannot be generated
   Enhancement category for table missing
   Enhancement category for include or subtype missing
   Field name KEY is reserved (Do not use structure as include in DB table)
   Field name PRIOR is reserved (Do not use structure as include in DB table)
   Exactly one field SPRAS of type LANG: Selection as text language possible
   Enhancement category for table missing
who can help me ?
thank you very much
BR.
Michael
Edited by: Michael Hong on Sep 23, 2009 12:36 PM

An unexpected error occurred while the job was running. (ID: 104)

I'm getting this error in the event logs when trying to run a consistency check / sync with one of our file servers.
This server was working fine, but w needed to migrate the data to a new partition (GPT) to allow it to expand past the 2TB limit of MBR partitions. I added a new 3TB disk migrated the data and changed the drive letter to what the old partition was
prior. Since then we seem to get this error.
I have installed the update roll up on both the server and the agent side. I have also removed the server from the protection group then re-added it. I've also removed and reinstalled the agent on the file server.
Any help is appreciated! Here's the full error from the DPM server:
The replica of E:\ on server is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. (ID: 3106)
An unexpected error occurred while the job was running. (ID: 104)

Server Version is Windows 2012 R2 STD. DPM is 4.2.1235.0 (DPM 2012 R2). I expanded the production file server. All that server does is host up file shares.
I suspected the fact that I created a new volume and changed drive letter back to the original to be the source cause of the issue. What I ended up doing is blowing away the backups from this server on disk and re-adding it to the protection group.
It now runs much longer, but still times out at random with the error mentioned above.
Vijay: The error was copied from Event Viewer. Not sure what else you require? Event ID is 3106 from DPM-EM.
The DPM logs say:
Affected area: E:\
Occurred since: 2015-01-05 2:04:38 AM
Description: The replica of Volume E:\ on servername is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing recovery
points, but new recovery points cannot be created until the replica is consistent.
For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency check on the farm. (ID 3106)
An unexpected error occurred while the job was running. (ID 104 Details: The semaphore timeout period has expired (0x80070079))
Date inactivated: 2015-01-05 7:03:04 AM
Recommended action: No action is required because this alert is inactive.
Affected area: E:\
Occurred since: 2015-01-05 2:04:38 AM
Description: The replica of Volume E:\ on servername is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing
recovery points, but new recovery points cannot be created until the replica is consistent.
For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency check on the farm. (ID 3106)
An unexpected error occurred while the job was running. (ID 104 Details: The semaphore timeout period has expired (0x80070079))

Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (Microsoft SQL Server)

I am getting the error message, "Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (Microsoft SQL Server)". I am attaching the stored procedure. Can anyone see where the syntax may
be causing this.
USE [ReportData]
GO
/****** Object: StoredProcedure [PDI].[usp_MJTestTop10_Select] Script Date: 04/23/2015 10:35:43 ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
--USE [ReportData]
--GO
--/****** Object: StoredProcedure [PDI].[usp_MJTestTop10_Select] Script Date: 04/23/2015 08:22:26 ******/
--SET ANSI_NULLS ON
--GO
--SET QUOTED_IDENTIFIER ON
--GO
ALTER PROCEDURE [PDI].[usp_MJTestTop10_Select]
@StartDate DATE,
@EndDate DATE,
@Location VARCHAR
AS
DECLARE @CalendarKey TABLE (
Calendar_Key int,
Organization_Key int,
Day_Date DATETIME
BEGIN
INSERT INTO @CalendarKey
SELECT C.calendar_key,
O.Organization_Key,
C.Day_Date AS DATETIME
FROM pdi.PDI_Warehouse_952_01.dbo.calendar C,
pdi.PDI_Warehouse_952_01.dbo.Organization O
where @EndDate is not null
and C.Day_Date BETWEEN @StartDate and @EndDate
or @EndDate is null
and C.Day_Date = @StartDate
END
SELECT CAST(C.Day_Date as DATE) as [Memo Date],
--C.calendar_key,
ISNULL(CAST(MBH.Transaction_Number as VARCHAR), 'Unknown') as [Memo Number],
O.Site_id,
O.Site_desc,
--p.Product_Key,
p.UPC as [UPC],
(CAST(P.Department_ID as VARCHAR) + ' ' + CAST(P.Category_ID as VARCHAR) + ' ' + CAST(P.Sub_Category_Id as VARCHAR)) as [D C S],
ISNULL(CAST(IPF.Vendor_Key as VARCHAR), 'Unknown') as [Vendor Code],
--ISNULL(CAST(V.Vendor_Desc as VARCHAR), 'Unknown') as [Vendor Desc],
ISNULL(P.Item_Desc, 'Unknown') as [Description],
ISNULL(P.Size_Desc, 'Unknown') as [Size],
ISNULL(RTrim(Cash.Cashier_Name), 'Unknown') as [Associate],
ISNULL(CONVERT(INT, IIF.Beg_Inv_Qty, 0), '0') as [Old Qty],
ISNULL(CONVERT(INT, IIF.End_Inv_Qty,0), '0') as [Adj Qty],
ISNULL(CONVERT(INT, IIF.End_Inv_Qty - IIF.Beg_Inv_Qty, 0), '0') as [Dif Qty]
FROM pdi.PDI_Warehouse_952_01.dbo.Item_Sales_Fact ISF
INNER JOIN pdi.PDI_Warehouse_952_01.dbo.Product P ON ISF.Product_Key = P.Product_Key
LEFT JOIN pdi.PDI_Warehouse_952_01.dbo.Organization O ON ISF.Organization_key = O.organization_key
LEFT JOIN pdi.PDI_Warehouse_952_01.dbo.Item_Purchases_Fact IPF ON ISF.Product_key = IPF.Product_Key
AND ISF.Organization_key = IPF.Organization_key
AND ISF.Calendar_key = IPF.Calendar_key
LEFT JOIN pdi.PDI_Warehouse_952_01.dbo.Item_Inventory_Fact IIF ON ISF.Product_Key = IIF.Product_Key
AND IIF.Product_Key = P.Product_Key
AND ISF.Organization_key = IIF.Organization_Key
AND ISF.Calendar_key = IIF.Calendar_Key
LEFT JOIN pdi.PDI_Warehouse_952_01.dbo.Calendar C ON ISF.calendar_key = C.calendar_key
LEFT JOIN pdi.PDI_Warehouse_952_01.dbo.Cashier Cash ON ISF.Organization_Key = Cash.Organization_Key
LEFT JOIN pdi.PDI_Warehouse_952_01.dbo.Cashier_Metric_Hourly_Dept_Snapshot CMH on Cash.Organization_Key = CMH.Organization_Key
AND Cash.Cashier_Key = CMH.Cashier_Key
AND ISF.Calendar_Key = CMH.Calendar_Key
LEFT JOIN pdi.PDI_Warehouse_952_01.dbo.MarketBasket_Header MBH ON ISF.Calendar_Key = MBH.Calendar_Key
AND ISF.Organization_Key = MBH.Organization_Key
AND Cash.Cashier_Key = MBH.Cashier_Key
LEFT JOIN pdi.PDI_Warehouse_952_01.dbo.Vendor V ON IPF.Vendor_Key = V.Vendor_key
AND IPF.Calendar_Key = C.Calendar_Key
LEFT JOIN @CalendarKey CK ON ISF.Calendar_Key = ck.Calendar_Key
AND ISF.Organization_Key = CK.Organization_Key
WHERE C.calendar_key = CK.Calendar_Key
ORDER BY
O.Location_ID,
C.Day_Date,
IPF.Vendor_Key,
P.UPC,
P.Size_Desc

Some additional comments.
@Location VARCHAR
Look closely at this. How many characters can @Location contain? You did not specify, so perhaps you think some appropriately large default value is used. Guess again. You did a similar thing with cast (multiple times) - which is handled
differently. Don't be lazy.
WHERE C.calendar_key = CK.Calendar_Key
Go review the join to the CK table. It is an outer join. Yet you have included criteria in the where clause that requires a match in the unpreserved (@CalendarKey aka CK) table. This effectively transforms that join from outer to inner.
Was that intentional? Probably, but then you don't need to use an outer join
FROM pdi.PDI_Warehouse_952_01.dbo.calendar C,
pdi.PDI_Warehouse_952_01.dbo.Organization O
Evolve. We do not join in the where clause any longer. You should be joining using join operators. And perhaps more importantly, why do you need to dump a resultset into a table variable at all? Note that your join is a cross join
since there is no relationship between calendar and Organization - intentional? Given the rest of the logic, it seems that you don't really need to do this.
ISNULL(CONVERT(INT, IIF.End_Inv_Qty,0), '0') as [Adj Qty],
Go review the documentation for convert. You supply a style, but does it do anything? We don't know what datatype End_Inv_Qty is, but I assume it is numeric (and not float). So what do you intend? And you convert it to integer but
use a character '0' in the isnull function. Your lack of consistency can lead to issues that are difficult to find and resolve.
CAST(C.Day_Date as DATE)
Why are you doing this? You defined the column in your table variable as datetime. You cast the value you use to populate this column to datetime. I'm guessing that you only really care about the date portion. The name you used for the
column implies this. So why bother with datetime in the first place?
And one last suggestion. If you disallow the use of NULL for the @EndDate argument (simply supply the same value for both date arguments) you can simplify the logic that populates your table variable (or its replacement) and greatly eliminate the confusion
and chance for errors that nullability requires.

Timeout expired. the timeout period elasped prior to completion of the operation or the server is not responding

HI All --- i am facing " Timeout expired. the timeout period elapsed prior to completion of the operation or the server is not responding " facing this issue every second day in our database.. for the rectification we just restart
the DB instance and its start working fine..... although database is in working condition and other databases in same instances are working fine, please suggest me any remedy to get rid from this issue.

Imran,
Check this:
http://sqlserverplanet.com/troubleshooting/fix-timeout-expired-the-timeout-period-elapsed-prior-to-completion-of-the-operation-or-the-server-is-not-responding
(similar thread)
http://social.msdn.microsoft.com/Forums/silverlight/en-US/685816f3-8d06-4411-8d00-d34c48c2938d/timeout-expired-the-timeout-period-elapsed-prior-to-completion-of-the-operation-or-the-server-is?forum=silverlightgamedev
http://blogs.msdn.com/b/spike/archive/2008/07/31/timeout-expired-the-timeout-period-elapsed-prior-to-completion-of-the-operation-or-the-server-is-not-responding.aspx
Thanks,
Jay
<If the post was helpful mark as 'Helpful' and if the post answered your query, mark as 'Answered'>

Can't print- 27" 2013 iMac-my epson stylus 3800 pro will not print-i updated driver n added printer in syst prefs-When i print the printer queue opens and shows the job as "stopped"-Supply level "information is not available"-maybe part of problem...thx

I can't print from my 27" late 2013 iMac. I am using an epson stylus 3800 pro. I updated driver and added printer in system preferences. When i print the printer queue opens and shows the job as "stopped". Supply level shows "information is not available which maybe part of problem...thank you

The first thing you could try is a reset of the printing system. Please note that this action will remove all printers and scanners from the Printers & Scanners preference pane.
With the reset complete, unplug the Epson USB cable from the Mac for a minute and then reconnect it. This action should result in the printer being added again to the Mac automatically. If this does happen, then see if you can print again.
If the printer is not added again automatically, open Printers & Scanners and click the plus button to add the Epson. Once this is done, then see if you can print again.

An unexpected error occurred while the job was running. (ID 104 Details: The parameter is incorrect (0x80070057))

We are using DPM Version: 4.1.3465.0 with System Center 2012 Service Pack 1 to back up VMs in our Hyper V Cluster. We have a total of 37 VMs with a combination of 2008r2 servers and 2012 servers. One of our 2012 servers will not backup, and we consistently
get the message "An unexpected error occurred while the job was running. (ID 104 Details: The parameter is incorrect (0x80070057))". I have seen this error message when I Googled it, but cannot get past it. I have deleted the Protection Group and
data and tried to re-create, but get the same errors. I also thought the the server might be mis-reporting the data size, but I expanded that to cover the replication data. I have also tried to perform consistancy checks multiple times with no luck. I have
not seen a difinitive answer from my Google searches, so was hopeful someone has seen this also, and have had success in resolving. Currently this server has no backup recovery points, so I am worried if it does crash. I think I have the rollups installed
as well.

Hi Kelly,
does the issue still persists?

The timeout period elapsed prior to completion of the operation or the server is not responding

the timeout period elapsed prior to completion of the operation or the server is not responding.
The error shows while executing a (select query) telerik report in MVC.

Hello,
Did you set the CommandTimeOut property of the SQL Command when you call the connection string to SQL Server?
If your select query is complex or the data is larger, please try to specify connectiontimeout property to maximum integer value.
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

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.

An unexpected error occurred while the job was running. (ID 104 Details: The parameter is incorrect (0x80070057)) After DPM 2012 SP1 to R2 Upgrade

Hi,
We have upgraded DPM 2012 SP1 to DPM 2012 R2 and OS is Windows 2012 standard.
Now in File Protection Group, we receive error
"An unexpected error occurred while the job was running. (ID 104 Details: The parameter is incorrect (0x80070057))".
This happens to only one Drive(X: Drive) of the PG server, other drive(Z: Drive) backup is working fine.
We tried,
Deleted entire protection group and recreated ,
Ran consistency job 2 to 3 times.
Ran Synchronize with consistency check.
But every time It failed. Before upgrade it was working fine.
Thanks

Hi
I would suggest opening a new case with MS to allow the DPM team to further look into the issue. Also the DPM 2012 R2 RollUp which addresses the (0x80070057)
issue is Rollup 1 and the private will not be needed after applying Rollup 1. The Roll up is found here
http://support.microsoft.com/kb/2904687/en-us
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your
question. This can be beneficial to other community members reading the thread. Regards, Dwayne Jackson II. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights."

The import was stopped - return code 0013

Dea all,
I have a problem. I'm updating SPAM from level 7.00/0029 to level 7.00/0037.
The following details help you to analyze the problem:
The import was stopped, since an error occurred during the phase
IMPORT_PROPER, which the Support Package Manager is unable to resolve
without your input.
After you have corrected the cause of the error, continue with the
import by choosing Support Package -> Import queue from the initial
screen of the Support Package Manager.
The following details help you to analyze the problem:
    -   Error in phase: IMPORT_PROPER
    -   Reason for error: TP_STEP_FAILURE
    -   Return code: 0013
    -   Error message: OCS Package SAPKD70037, tp step "I", return code
        0013
Please help me.
thanks a lot.

Yes I tried but it does not work.
Main import
Transport request   : SAPKD70037
System              : GT6
tp path             : tp
Version and release: 372.04.78 700
R3trans version 6.14 (release 700 - 10.02.10 - 13:32:00).
unicode enabled version
===============================================
date&time   : 26.02.2010 - 17:42:19
control file: /usr/sap/trans/tmp/SAPKKD70037.GT6
> #pid 7512 on ensv15wz (gt6adm)
> import
> buffersync=yes
> file='/usr/sap/trans/data/RD70037.SAP'
> continuation='/usr/sap/trans/data/RD70037_#.SAP'
> client cascade yes
> watchparallelprocesses yes
>
> excluding 'R3TRDDDD','R3TRDOMA','R3TRDTEL','R3TRENQU','R3TRMACO','R3TRMCID','R3TRMCOB','R3TRSHLP','R3TRSQLT','R3TRTABL','R3TRTTYP
R3trans was called as follows: R3trans -w /usr/sap/trans/tmp/SAPID70037.GT6 /usr/sap/trans/tmp/SAPKKD70037.GT6
Connected to DBMS = ORACLE     dbs_ora_tnsname = 'GT6'     SYSTEM = 'GT6'.
0 0
trace at level 1 opened for a given file pointer
================== STEP 1 =====================
date&time        : 26.02.2010 - 17:42:19
function         : IMPORT
data file        : /usr/sap/trans/data/RD70037.SAP
Continuation     : /usr/sap/trans/data/RD70037_#.SAP
buffersync       : YES
clients          : cascade
repeatimport     : NO
repeatclimport   : NO
c.s.i.           : NO
watchparallelprocesses: YES
autorepeat       : -1 (automatic)
l.s.m.           : VECTOR
charsetadapt     : YES
def. charset     : WEUROPEAN
commit           : 100000
table cache      : dynamic
EXCLUDING        : 'R3TRVIEW','R3TRUENO','R3TRTTYP','R3TRTABL','R3TRSQLT','R3TRSHLP','R3TRMCOB','R3TRMCID','R3TRMACO','R3TRENQU','R
clients which are protected against client cascade: 066
client cascade to: 000, 001, 010, 065, 100, 200, 300, 900, 910
Character set on this machine : 2 byte unicode little endian.
Character set on the data file: 2 byte unicode big endian.
Data file is compressed with algorithm 'L'.
Export was executed on 17.11.2009 at 16:48:17 by k7badm
700
with R3trans version: 20.04.09 - 13:27:00
Source System = Solaris on SPARCV9 CPU on DBMS = DB6     DB2DBDFT = 'K7B'     SYSTEM = 'K7B'.
language vector during export: DE
language vector during export: DE (ISO-DEEN)
lsm during export: VECTOR
trfunction = D (patch transport)
switching to selective language import
language 'F' is installed, but no entries for this language were exported ('DE')
language 'I' is installed, but no entries for this language were exported ('DE')
language 'S' is installed, but no entries for this language were exported ('DE')
the following languages will be imported: DEFIS
Used Commandfile SAPKD70037           (SAPUSER/623)
Target client in E070C updated (   )
0 entries for E070 imported (SAPKD70037).
0 entries for E071 imported (SAPKD70037          *).
Start import R3TRCLASCL_OCS_ENVIRONMENT ...
1 entry for TADIR updated (R3TRCLASCL_OCS_ENVIRONMENT                      ).
STOP R3trans received signal 11 from operating system.
Main import
End date and time : 20100226174219
Ended with return code: ===> 13 <===

Selective Deletion - can the job be stopped?

Hello experts,
we are facing this issue: a selective deletion of approx. 5000 records out of 15 million records was carried out in a cube last friday.
We can see the background job is still running. This is the first time we are doing a selective deletion so we don't know if this is normal that the job is running for so long. If it's not normal, is it safe to stop the job?
Many thanks in advance.
Regards,
Inma

Thank you for your answer. But is it safe to stop the job? why is it taking so long?
Thanks
Inma

SQL Server job failed. The Job was invoked by Schedule 11 (NAV Backup 1). The last step to run was step 1 (Subplan_1)

Date 07-01-2014 10:00:00 PM
Log Job History (NAV Backup 1.Subplan_1)
Step ID 1
Server NAVSRV
Job Name NAV Backup 1.Subplan_1
Step Name Subplan_1
Duration 00:02:26
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0
1122

About your question on How and Who changed it, i told that nobody changed it. I found in this way.
1122
I also Saw the plan and the path of Database and database log was ok , i mean PHARMANEXT_LOG_95ABA2F6-DC67-4CFC etc...
was exactly like in the C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA
Maybe is something wrong with my backup script, but i dont think so because before 23 of december
everithing was ok. After this date it failed.
Anyway check this script of "Remove SQL log" , the one that you think is a culprit:
DECLARE @name VARCHAR(50)
DECLARE @fileName VARCHAR(256)
DECLARE db_cursor CURSOR FOR
SELECT name
FROM master.dbo.sysdatabases
WHERE name NOT IN ('master','model','msdb','tempdb')
OPEN db_cursor
FETCH NEXT FROM db_cursor INTO @name
WHILE @@FETCH_STATUS = 0
BEGIN
SET @filename = @name + '_log'
Exec ('Use [master] alter database [' + @name + '] set recovery simple')
Exec ('Use [master] alter database [' + @name + '] set recovery FULL')
Exec ('Use [' + @name + '] DBCC SHRINKFILE ("' + @filename + '",1)')
FETCH NEXT FROM db_cursor INTO @name
END
CLOSE db_cursor
DEALLOCATE db_cursor
go
Hello,
You have created a cursor which will take all user databases and change recovery model to Simple and then to full what this will cause it will break the log chain and you might loose your RPO and RTO.This operation truncates the log .Please stop this job
immediately.It is worst you can do to your Database recovery and availability.After this you are trying to shrink .
As pointed out it is seriously not advised to shrink data file.And if you have proper trn log backup it manages the growth of log file
Hope this helps
Keep looking for any such activity which might change anything in your database
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

The job was stopped prior to completion by (Unknown)

Similar Messages

Maybe you are looking for