Store Operations Business Rules

[shah68]

While doing year end inventory we have come across the following errors and the software closes.
----------------
Store Operations Business Rules
Database connection lost, application will be closed
Error #-214746759
Connection Failure
(Source:Microsoft OLE DB Provider for SQL Server)
(Sql State: 08501)
(NativeError:0)
No Help file available
SELECT GETDATE() AS CurrentDateTime.

please help me out from this issue.

 

[fredericofonseca]

you probably have other errors following that one.

my initial advise is increase the connection and command timeouts and re-index your database before attempting the process again.

And there are lots of reported errors exactly like this on the net - searching for

https://www.google.com/search?q=Sto...q=t#q=Store+Operations+Business+Rules+timeout

may also point you out to some other possibilities.

Regards

Frederico Fonseca
SysSoft Integrated Ltd

http://www.syssoft-int.com

FAQ219-2884
FAQ181-2886

 

[SQLBill]

As Frederico said...there should be other messages that will help track down the issue...but also look at when the issues are happening and see if there is anything else happening at those times. For example, if it happens at the top of each hour...what is happening at that time? Could there be a command on the database that is killing connections? If it is happening once a day...is the database server being rebooted? Connection issues like that are difficult for anyone not at the location to troubleshoot....

Good luck tracking it down.

-SQLBill

The following is part of my signature block and is only intended to be informational.
Posting advice: FAQ481-4875

 

[shah68]

the problem is breaking my head. I have already change the lan put new lan card in server even and POS PC. And for your kind information I have another database on the sql which is working good. Even we have 15 branches and all are working well.
as per Fredorice said,,,,, I have already re index it but, no profit.
Please help me to get out from this issue.

 

[fredericofonseca]

as I and Bill said you will need to look at all the other messages that happened before and after the error you gave.

You should also go through the SQL Server logs and see what messages you got around the time you received this error.
and if this is happening all the time make sure you are watching the server activity at that point in time to see if you can identify possible causes for the problem.
e.g. check cpu usage on server, tempdb usage while the process is being executed.
Check other queries being executed at the same time and if possible prevent them.
Check index usage and sql usage of the process you are executing - and if any of the sqls can be improved by
you adding a new indexes do so.

And again raise the connection and command timeouts on your application.
And unfortunately without being onsite its very difficult to give any further advise unless we have further errors/warnings.

Regards

Frederico Fonseca
SysSoft Integrated Ltd

http://www.syssoft-int.com

FAQ219-2884
FAQ181-2886

 

[gk53]

Run one query at a time and insulate a problem