I'd build an application in VB.net which contains some background procedures to be done every day. The exe was scheduled in SQL Server 2008 R2.
I'm getting the following error from the system. Whereas when the same scheduler is run manually it runs successfully. There are no multiple processes running during the scheduler process. Can you suggest why it happens?
Error:
Connection Timeout Expired.
The timeout period elapsed during the post-login phase.
The connection could have timed out while waiting for server to complete the login process and respond; Or it could have timed out while attempting to create multiple active connections.
The duration spent while attempting to connect to this server was -
[Pre-Login] initialization=2; handshake=5; [Login] initialization=0; authentication=0; [Post-Login] complete=14001;
Thanks in advance.
Related
i have a problem with my rundeck, in automatisation process i need to perform some long task with Rundeck such as Database Refresh from PRODUCTION to TEST Database.
This case cause problems sometimes.
I've no timeout set on rundeck job, i use script that launch action on a distant server trough SSH.
If a step took long time (Drop database, import database with datapump), Rundeck generate an error
Failed: NonZeroResultCode: Remote command failed with exit status -1
after a certain period of time.
It's look like a timeout, but i don't know where this timeout occured and i can't find it.
But the DROP or the IMPDB still continue his job and if you wait for it, the action has successfully completed but rundeck marked the step as failed, i put some workaround such as error handler to by pass but it's not very clean.
Do you have any idea were that timeout is set ?
In my opininon, after a certain period of time, if rundeck did not receive an answer from the distant server, it cut off and mark as failed with the error code Failed: NonZeroResultCode: Remote command failed with exit status -1
You can increase the ssh timeout globally at the framework.properties file.
Stop the Rundeck server, then add the following lines on the /etc/rundeck/framework.properties file:
framework.ssh-connection-timeout=0
framework.ssh-command-timeout=0
Then start the Rundeck service.
The timeout values are in milliseconds, 0 is indefinite.
More info here.
We are facing issue with windows service, its hanging just after opening the oracle connection and while creating the oracle command.
Before killing the service, when we analyzed the database logs, it showed the inactive session (not closed) and it’s matching the ‘DB last call time’ with the ‘service hung time’. That particular db session keeps waiting for application to instruct the next steps and stays idle, until we kill the service.
Most importantly this issue happens only sometimes without any pattern.
We have pool size set to 50 and connection timeout to 10min at application.
Types of oracle commands used:
using (OracleCommand cmd = oraCon.CreateCommand())
_cmd = new OracleCommand(“sqlText”, _connection)
I need some help! Some time ago we migrated an Oracle database to DB2 on Cloud.
My application use a WildFly Server and the connection to Oracle database previously only needed 5 minutes to start, that was a normal time to start.
However, when I start using DB2 on cloud, the time to start is about 14 minutes.
Using IBM Data Server Manager, I tried to monitor what is happening with the database during the application server connection and I can see a process call "Compilation Process", which is responsible for the time to complete the connection. I do not understand if that is normal, or if there exists any solution to decrease the time used for that process. Thank you very much !!
When halting service in Process Admin console - using Halt service button - I get following message after a while:
Halting of the Service timed out. Most probably, the Process Server failed to halt the Service within short time period.
From what I can see, it happens only when said service has few (say in tenths)steps, when it has more (hundreds) steps, it works well.
Can somebody see cause of this and tell me what to do? Thanks.
If we fail to halt a hung or long running (infinite loop) service within a short duration, process admin console does not allow to halt it.
This is the default behavior of how halt will work. Only way to restart the server to reinstate the BPM env.
I am working on a SQL Server 2008 R2 server.
On this server are two instances (let's call them A and B).
A replicates one of it's databases to B using a transactional replication.
This replication however became inactive and the snapshot deleted after some maintenance occurred.
I have reinitialized the subscribers and have successfully created a new snapshot but when I start synchronizing, I get the following error:
The SQL Server cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users or ask the system administrator to check the SQL Server lock and memory configuration.
(Source: MSSQLServer, Error number: 1204)
I have killed the connections to database B that aren't Administrator (login of sa) and that aren't running. This didn't work and I am still getting the error.
I'm not very knowledgeable when it comes to this stuff and I don't have a DBA to talk to so any help is greatly appreciated as I am running out of ideas fast.
Thanks in advance!
Edit: Here is some more info after talking with Razzle Dazzle.
DBCC OPENTRAN - This finds no open transactions on both the provider and the subscriber.
sp_who - This shows that very few (under 40) connections are going for both provider and subscriber. The only connection(s) that are in a status other than either 'Background' or 'Sleeping' is the connection(s) that I have to the server via SSMS.
DBCC MEMORYSTATUS -
Publisher: Publisher Memory Status
Subscriber: Subscriber Memory Status