Increasing the timeout period for a custom report

Dear Friends
I have written a Program (SE38) which uses multiple select commands to search data from different tables and then generate a report. When I had less data, it was working properly. HOwever, with more data it times out.
Is there a way to manually change the timeout settings for this program only.
ANy feedback will be highly appreciated.
Thanks
Ram

>
Prasad Ram wrote:
> Is there a way to manually change the timeout settings for this program only.
Think about it, if this would have been the case every developer would then have changed the timeout settings for the program which was not performance efficient
Instead of concentrating on the solution for evading the timeout you should rather focus why it is occurring at first place.
BR,
Suhas

Similar Messages

  • How to find optimal timeout period for trans-timeout-seconds element.

    we are using Weblogic 7.0 Integration Studio,in one workflow we got "weblogic.transaction.internal.TimedOutException" and the exception text is "Transaction timed out after 1089 seconds".
    Presently we are using timeout period as 1089 seconds.
    On what basis the timeout period for transactions is specified, i.e. how the value of the <trans-timeout-seconds> is set in weblogic-ejb-jar.xml file?
    Is there any method to find the optimal value?

    You should base this on the average time your transaction typically takes. It would have to factor in the type of backend systems that you are connecting too, the type of work you are doing and any network etc issues.
    Typically 1089 seconds seems like it should be more then ENOUGH.
    Kunal Mittal

  • Unhandled Exception: System.TimeoutException: The request channel timed out while waiting for a reply after 00:01:59.9139778.Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding.

    Hi, 
    I created a simple plugin and since i wanted to use Early Binding i added Xrm.cs file to my solution.After i tried registering the plugin (using the Plugin Registration Tool) the plugin does not gets registered and i get the below mentioned Exception.
    Unhandled Exception: System.TimeoutException: The request channel timed out while waiting for a reply after 00:01:59.9139778. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this
    operation may have been a portion of a longer timeout.
    Server stack trace: 
       at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
       at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.Request(Message message, TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
       at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
    Exception rethrown at [0]: 
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       at Microsoft.Xrm.Sdk.IOrganizationService.Update(Entity entity)
       at Microsoft.Xrm.Sdk.Client.OrganizationServiceProxy.UpdateCore(Entity entity)
       at Microsoft.Crm.Tools.PluginRegistration.RegistrationHelper.UpdateAssembly(CrmOrganization org, String pathToAssembly, CrmPluginAssembly assembly, PluginType[] type)
       at Microsoft.Crm.Tools.PluginRegistration.PluginRegistrationForm.btnRegister_Click(Object sender, EventArgs e)
    Inner Exception: System.TimeoutException: The HTTP request to 'https://demoorg172.api.crm.dynamics.com/XRMServices/2011/Organization.svc' has exceeded the allotted timeout of 00:01:59.9430000. The time allotted to this operation may have been a portion of a
    longer timeout.
       at System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason)
       at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
       at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
    Inner Exception: System.Net.WebException: The operation has timed out
       at System.Net.HttpWebRequest.GetResponse()
       at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
    And to my Surprise after i remove the Xrm.cs file from my solution the Plugin got registered!
    Not understanding what exactly is the issue.
    Any Suggestions are highly appreciated.
    Thanks,
    Shradha
      

    Hello Shardha,
                            I really appreciate that you have faced this issue.This is really very strange issue and basically it occurs because of big size of your early bound class and slow internet
    connection.
                            I would strictly recommend you to reduce the file size of your early bound class and then register.By default early bound class is created for all the entities which are
    present in CRM(System entities as well custom entities).Such kind of early bound classes takes lots of time to register on server and hence timeout exception comes.
                            There is some standard define to reduce the size of early bound class.Please follow the link to get rid from big size of early bound class.
    Create a new C# class library project in Visual Studio called SvcUtilFilter.
    In the project, add references to the following:
    CrmSvcUtil.exe(from sdk)   This exe has the interface we will implement.
    Microsoft.Xrm.Sdk.dll  (found in the CRM SDK).
    System.Runtime.Serialization.
      Add the following class to the project:
    using System;
    using System.Collections.Generic;
    using System.Xml.Linq;
    using Microsoft.Crm.Services.Utility;
    using Microsoft.Xrm.Sdk.Metadata;
    namespace SvcUtilFilter
        /// <summary>
        /// CodeWriterFilter for CrmSvcUtil that reads list of entities from an xml file to
        /// determine whether or not the entity class should be generated.
        /// </summary>
        public class CodeWriterFilter : ICodeWriterFilterService
            //list of entity names to generate classes for.
            private HashSet<string> _validEntities = new HashSet<string>();
            //reference to the default service.
            private ICodeWriterFilterService _defaultService = null;
            /// <summary>
            /// constructor
            /// </summary>
            /// <param name="defaultService">default
    implementation</param>
            public CodeWriterFilter( ICodeWriterFilterService defaultService )
                this._defaultService = defaultService;
                LoadFilterData();
            /// <summary>
            /// loads the entity filter data from the filter.xml file
            /// </summary>
            private void LoadFilterData()
                XElement xml = XElement.Load("filter.xml");
                XElement entitiesElement = xml.Element("entities");
                foreach (XElement entityElement in entitiesElement.Elements("entity"))
                    _validEntities.Add(entityElement.Value.ToLowerInvariant());
            /// <summary>
            /// /Use filter entity list to determine if the entity class should be generated.
            /// </summary>
            public bool GenerateEntity(EntityMetadata entityMetadata, IServiceProvider services)
                return (_validEntities.Contains(entityMetadata.LogicalName.ToLowerInvariant()));
            //All other methods just use default implementation:
            public bool GenerateAttribute(AttributeMetadata attributeMetadata, IServiceProvider services)
                return _defaultService.GenerateAttribute(attributeMetadata, services);
            public bool GenerateOption(OptionMetadata optionMetadata, IServiceProvider services)
                return _defaultService.GenerateOption(optionMetadata, services);
            public bool GenerateOptionSet(OptionSetMetadataBase optionSetMetadata, IServiceProvider services)
                return _defaultService.GenerateOptionSet(optionSetMetadata, services);
            public bool GenerateRelationship(RelationshipMetadataBase relationshipMetadata, EntityMetadata otherEntityMetadata, IServiceProviderservices)
                return _defaultService.GenerateRelationship(relationshipMetadata, otherEntityMetadata, services);
            public bool GenerateServiceContext(IServiceProvider services)
                return _defaultService.GenerateServiceContext(services);
    This class implements the ICodeWriterFilterService interface.  This interface is used by the class generation
    utility to determine which entities, attrributes, etc. should actually be generated.  The interface is very simple and just has seven methods that are passed metadata info and return a boolean indicating whether or not the metadata should be included
    in the generated code file.   
    For now I just want to be able to determine which entities are generated, so in the constructor I read from an XML
    file (filter.xml) that holds the list of entities to generate and put the list in a Hashset.  The format of the xml is this:
    <filter>
      <entities>
        <entity>systemuser</entity>
        <entity>team</entity>
        <entity>role</entity>
        <entity>businessunit</entity>
      </entities>
    </filter>
    Take a look at the methods in the class. In the GenerateEntity method, we can simply check the EntityMetadata parameter
    against our list of valid entities and return true if it's an entity that we want to generate.
    For all of the other methods we want to just do whatever the default implementation of the utility is.  Notice
    how the constructor of the class accepts a defaultService parameter.  We can just save a reference to this default service and use it whenever we want to stick with the default behavior.  All of the other methods in the class just call the default
    service.
    To use our extension when running the utility, we just have to make sure the compiled DLL and the filter.xml file
    are in the same folder as CrmSvcUtil.exe, and set the /codewriterfilter command-line argument when running the utility (as described in the SDK):
    crmsvcutil.exe /url:http://<server>/<org>/XrmServices/2011/Organization.svc /out:sdk.cs  /namespace:<namespace> /codewriterfilter:SvcUtilFilter.CodeWriterFilter,SvcUtilFilter
    /username:[email protected] /password:xxxx
    That's it! You now have a generated sdk.cs file that is only a few hundred kilobytes instead of 5MB. 
    One final note:  There is actually a lot more you can do with extensions to the code generation utility. 
    For example: if you return true in the GenerateOptionSet method, it will actually generated Enums for each CRM picklist (which it doesn't normally do by default).
    Also, the source code for this SvcUtilFilter example can be found here. 
    Use at your own risk, no warranties, etc. etc. 
    Please mark as a answer if this post is useful to you.

  • This item could not be crawled because the repository did not respond within the specified timeout period. Try to crawl the repository at a later time, or increase the timeout value on the Proxy and Timeout page in search administration. You might also wa

    HI,
    I got the error message in the crawl log as below after performing the Full Crawl
    This item could not be crawled because the repository did not respond within the specified timeout period. Try to crawl the repository at a later time, or increase
    the timeout value on the Proxy and Timeout page in search administration. You might also want to crawl this repository during off-peak usage times.
    To overcome the above error,many forums have suggested me to increase the time out which is under Farm level settings.But if time out gets increased,performance impacts as well.
    So please suggest me to overcome this error without increasing the timeout.Thanks in advance
    Regards,
    Sudheer
    Thanks & Regards, Sudheer

    Hi,
    I understand that you get the error message when performing a full crawl. I have seen similar cases caused by IE proxy settings. You can try to edit the Internet Options>Connections>LAN settings. Uncheck ‘Automatically detect settings’.
    For more information, please refer to this site:
    Search error: crawler could not connect to the repository:
    http://social.technet.microsoft.com/forums/en-US/sharepointadminprevious/thread/c230ab36-8d0b-4c25-bf86-33136d17642b/
    Thanks,
    Entan Ming
    Entan Ming
    TechNet Community Support

  • Failover Cluster Manager : Add node wizard Error " This operation returned because the timeout period expired" Windows Server 2012

    Hi Everybody,
    I have two node cluster and trying to add the third node (which is a Virtual Machine), all nodes are in different subnet and can communication with each other. While adding the third node it gives the error at the end of wizard "  This operation
    returned because the timeout period expired ". My domain controller is 2008 Enterprise Server and nodes are all running Windows Server 2012 Standard Edition. Any idea what is causing the issue.
    thanks 

    Hi,
    Before you add a server (node) to a failover cluster, we strongly recommend that you run the Validate a Configuration Wizard for the existing cluster nodes and the new node
    or nodes. The Validate a Configuration Wizard helps you confirm the configuration in a variety of important ways. For example, it validates that the server to be added is connected correctly to the networks and storage and that it contains the same software
    updates. Please post the error or warning report.
    Please try to install the Recommended hotfixes and updates for Windows Server 2012-based failover clusters:
    Recommended hotfixes and updates for Windows Server 2012-based failover clusters
    http://support.microsoft.com/kb/2784261
    Hope this helps.
    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.

  • SharePoint - Error_1_Error occurred in deployment step 'Add Solution': Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was rea

    Hi,
    I am Shanmugavel, SharePoint developer, 
    I am facing the below SharePoint 2013 deployment issue while deploying using VS2012.
    If i will deploy the same wsp or existing wsp
    (last build) using direct powershell deployment, the solution adding properly, but the same timeout exception coming while activation the features.  Please find the below error.
    I tried the below activists:
    1. Restarted my dev server, DB server. 
    2. tried the same solution id different server
    3. tried existing wsp file (last build version)
    4. Deactivated all the features, including project Active deployment configuration.... but still i am facing the same issue.
    I hope this is not coding level issue, because still my code is not start running, before that some problem coming.
    Please help me any one.....  Last two days i am struck because of this...

    What you need to understand is the installation of a WSP does not do much. It just makes sure that you relevant solution files are deployed to the SharePoint farm.
    Next comes the point when you activate the features. It is when the code which you have written to "Activate" certain features for your custom solution.
    Regarding the error you are getting, it typically means that you have more connections (default is I guess 100) open for a SQL database then you are allowed to.
    If you have a custom database and you are opening a connection, make sure you close it as well.
    Look at the similar discussion here:
    The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool
    size was reached[^]
    I would suggest further to look at the
    ULS logs[^] to get better insight.
    Manas Bhardwaj's Stream : www.manasbhardwaj.net

  • 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.

  • 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

  • "Error: 0x800705B4. This operation returned because the timeout period expired"

    Hello,
    I deployed security updates Mid October 201, however some clients failed to install with the error "0x800705B4 this operation returned because the timeout period expired when installing updates".
    Although, i saw an article but this did not address the issue. It was advised  i temporarily disable any third party antivirus software and firewall.
    Unfortunately, we use SEP antivirus and any attempt to disable it would yanck the clients off the network. Windows Firewall is also disabled on these clients. 
    Can anyone help urgently?

    Hi,
    What's the status in Software Center about the updates?
    Have you checked SCCM updates logs on the clients?
    http://technet.microsoft.com/en-us/library/hh427342.aspx#BKMK_SU_NAPLog
    Please also check the boundary groups associated with DPs have been configured correctly.
    Best Regards,
    Joyce
    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.

  • 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

  • How to increase the waiting time for response in Adapter Engine not in IE

    Hi Experts,
                It is a SOAP to Proxy Synchronous interface. SOAP system is sending the request to PI, PI sending the same request to ECC system, After execution of some logic response back to PI in 7 minutes. In ABAP Stack(sxmb_moni) processing the response message also successfully with success flag after completion of these 7 minutes. But exactly 5 minutes later getting the error at Java Stack RWB- in communication channel monitoring i.e
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message bd2bf8d0-b2c2-11e0-c383-001cc4fb5cb7(OUTBOUND) expired.  We have set the "runtime-HTTP_TIMEOUT" parameter as 3600. thats why in Integration engine it is processing successfully.
    kindly suggest me how to increase the waiting time for response in Adapter Engine. Exactly after 5 mins getting the above error in rwb, but in Integration Engine getting successful flag after 7 mins until then it is waiting for response with  status flag Log version.
    Thanks & Regards,
    Srihari.

    Hi,
    Please see
    How To... Investigate Timeouts In Synchronous XI/PI Scenarios
    It will answer all your queries
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c059d583-a551-2c10-e095-eb5d95e03747?QuickLink=index&overridelayout=true

  • 11.1.1.5 - How can we increase the timeout of BPM Workspace ?

    Hi ,
    I am facing an issue where the BPM Workspace times out after every 5 mins or so.
    I read in another post that we need to edit some workspace.properties file - where can I find it.
    I tried using http://technology.amis.nl/blog/13768/increase-the-timeout-of-oracle-bpm-worklist-app/comment-page-1#comment-481839 but ran into some issues (should be there as my comment) where the timeout became too high.
    Appreciate your help.
    Thanks

    I got this resolved. Added a different variable for the weblogic.xml timeout and teh web.xml timeout (Btw the digits after the timeout props are not needed if you donot need too many variables).
    Also My config root was pointing to the wrong war. I changed it to point to a correct .war (relative location can be used too) & it worked just fine after that !
    Thanks

  • Error: Device\Ide\iaStor0, did not respond within the timeout period.

    Hello,
    In last few months, I began getting the error:
    The device, \Device\Ide\iaStor0, did not respond within the timeout period.
    My system hangs and slows to a crawl.  Error seems to be well-known, and solution is to install the latest version of Intel Matrix Manager, which is 8.6.   I've done this, I reinstalled my OS, and I've reinitialized my hard Raid1 array.  None of this has helped.
    http://www.intel.com/support/chipsets/imsm/sb/cs-025783.htm
    Any suggestions?
    Thx.
    Scott

    Quote
    Have you tested HDD's with Seagate diagnostic utility?
    Going by the link you have provided I assume you are using Vista?
    Yes, I am using Vista and I did also use Sea Tools; no issue identified.  I'd love to hear more suggestions.  Things I've done:
    1.  Reformat / reinstall.  Helped, but problem not eliminated.
    2.  Ran SeaTools Disk Diagnostic.  No issue.
    3.  Installed Intel Matrix STorage, most recent version 8.6.  Should've fix prob, but didn't. 
    4.  Upgraded Bios from 7.5 to 7.9.
    Seems like the upgrade to Intel Matrix Storage Manager should've fixed this issue, but it didn't.   Any particular drive identified in the error message in the original post? 
    It is also not clear what changed to have introduced this error.  My system has been stable for 2 years and from the errors looks like I've had problems for the last 3 months, but they got notably worse in the last 2 weeks.  Reformatting / reinstall helped, but didn't eliminate these issues.  Any insight would be appreciated.

  • Transaction Variant for a Custom Report

    Hi Folks...
    I am trying to create a transaction variant for a custom report...and i am unable to do it. Have any one tried that before and got it worked..please let me know.
    Thanks in advance.
    Rajeev

    hi,
    i also used a different approach based on the requirement.  this might be helpful to someone:
    requirement: to make one of the parameter fields as display only.  other users should not be allowed to edit this field & make it modifiable again.
    _solution1:_ in the program, assign the parameter field to a modification id and make it protected (screen-input=0). 
    limitation: needs program modification incase there is a future requirement to change the parameter field value.
    solution2: [1]create & save a variant and protect that parameter field. [2] go to SE93 & create a report transaction, put your saved variant in the 'start with variant'. [3] go to SU21 & create an authorization object for controlling the access to the variant. [4] ask your basis to attach this authorization object to the user id responsible for maintaining the variants for that program. [5] add a logic to check the authorization object in your program whenever the user tries to save or delete variants.
    remarks: in production, make sure the authorization object & the update profile are transported.  create also the same variant name as what you have defined in your report transaction code.

  • 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.

Maybe you are looking for