All of a sudden, we're getting "disk or network error" when we run an integration. This just started happening last week on multiple workstations. I applied the latest patches and it solved it for a day, but then it came back. The integration appears to work, even though we have to forcefully kill the integration.
Has anyone experienced this before?
*This post is locked for comments
does she have access to that file? Can you browse to that file from her workstation and open the mdb?
That didn't help...her path was set to the MDB file.
She did tell me that other stations work just fine (her's seems to be the only one with issues)
I was going to say, LDB is the locking file that Access uses. so either you're pointing at the wrong file or the access mdb was corrupted and maybe just needs to be opened and then a compact and repair might clear it up.
You know what, that's the wrong extension..it's supposed to be an MDB
is that .LDB? Are you writing to an Access database?
There were no errors on the server and no errors in SQL. When I looked at the error logs on the workstation, i did find errors:
Delayed Write Failed} Windows was unable to save all the data for the file \\gp\intyshare\IM\Converted_Converted_Billing.ldb; the data has been lost. This error may be caused by network connectivity issues. Please try to save this file elsewhere.
We are ditching IM for SmartConnect this week, so we'll just deal with this for now. Interesting that it started last monday though.
Is the disk space where your log and data files in good shape? What is the integration doing? Is it moving a ton of data by chance?
If you run into that issue again, I would check the event viewer on the machine where the integration was being executed from (or the client if it's citrix or something like that). I would then check the server event viewer and note the time of the error and check the sql logs.
If you ping the server it is trying to connect to, does the ping ever fail? Any chance they are losing connectivity by chance? One other thing to check, if this is doing any kind of web based work (through web services or something else), make sure there isn't a new proxy tool installed that might think this work is some kind of DoS attack or something. I've had that happen before with a CRM implementation.
SQL server appears to be fine, no other issues have been reported. I did reboot it this past weekend, but that didn't help. The integration itself is not logging any errors, but I have not check the other locations you mention.
How is your SQL server? You may find some information either in the server event viewer, local desktop event viewer or in the SQL server log file that will help.
#1
André Arnaud de Cal...
291,391
Super User 2024 Season 2
#2
Martin Dráb
230,445
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
