bfuchs
asked on
Some sers suddenly getting error popup msg
Hi Experts,
We have an ADP project connected to SQL Server 2005 BE.
For some reason few users are suddenly getting the attached error after leaving the application unattended for a short time.
Any idea where to start looking into?
Thanks in advance.
Capture.PNG
We have an ADP project connected to SQL Server 2005 BE.
For some reason few users are suddenly getting the attached error after leaving the application unattended for a short time.
Any idea where to start looking into?
Thanks in advance.
Capture.PNG
Sounds like the connection is timing out. I don't use ADP's so I can't tell you where to look but check the form or the query to see what the timeout property is set to. It could also be a default at the server that was changed.
ASKER
Hi,
The OLE DDE timeout property is set to 30, but that was always the case and didnt change now.
In addition if this is a server issue then I guess would happen to everyone, not only to few users.
Thanks,
Ben
untitled.png
The OLE DDE timeout property is set to 30, but that was always the case and didnt change now.
It could also be a default at the server that was changed.Attached the server settings, however cant beleive this got changed as I'm the one responsible for it..
In addition if this is a server issue then I guess would happen to everyone, not only to few users.
Thanks,
Ben
untitled.png
set remote query timeout to 0 (or >600 based on your business logic)
it can help
it can help
ASKER
@EugeneZ,
As stated above, this problem just started occuring and only to few users, therefore I would rather look at something that may have happen to their pc.
In general, if I should start modify server settings for every issue particular users are facing, It will definitely lead to more trouble in the long run..
Thanks,
Ben
As stated above, this problem just started occuring and only to few users, therefore I would rather look at something that may have happen to their pc.
In general, if I should start modify server settings for every issue particular users are facing, It will definitely lead to more trouble in the long run..
Thanks,
Ben
This is just a stab in the dark but I had trouble with SQL Server linked to Access last year. The support folks installed a new version of the firewall firmware on the server and it turned out to be the wrong version so any recordset I retrieved that was more than ~ 4,000 rows was displayed as #deleted# in every field and every row. This affected everyone because the problem was related to the server box. But in your case, check updates on the computer in question to see if a firewall or other security product was recently updated.
ASKER
@Pat,
Thanks,
Ben
This affected everyone because the problem was related to the server box.This is exactly my point here..
But in your case, check updates on the computer in question to see..How about if I do a system restore on their pc, will that help?
Thanks,
Ben
If you have a valid restore point prior to when the error occurred, try it. But at some point, you will need to determine which update caused the problem to prevent it from recurring.
ASKER
@Pat,
As of now we will be doing the system restore and give it a couple of days to see if this helped, now in case it did help then we have time to speculate which update/s were the cause, however if it doesn't then we'll need to look in different direction..
Thanks,
Ben
As of now we will be doing the system restore and give it a couple of days to see if this helped, now in case it did help then we have time to speculate which update/s were the cause, however if it doesn't then we'll need to look in different direction..
Thanks,
Ben
ASKER
Hi Pat,
We did the system restore as mentioned and nothing changed, meaning user still got the error message, what else would you recommend to do?
Thanks,
Ben
We did the system restore as mentioned and nothing changed, meaning user still got the error message, what else would you recommend to do?
Thanks,
Ben
When some people have a problem and others don't, there is something different between the environments. Try reinstalling Office. Make sure everyone is using the same ODBC driver. Virus programs are frequent culprets.
ASKER
Hi,
Reinstalling office we did that already.
Virus program we all have AVG in place.
Re ODBC driver, not sure where to look for that as I never install it, tough this is part of windows..
Besides we need to focus on something that suddenly happen while this is something that if wrong was always like that..
Thanks,
Ben
Reinstalling office we did that already.
Virus program we all have AVG in place.
Re ODBC driver, not sure where to look for that as I never install it, tough this is part of windows..
Besides we need to focus on something that suddenly happen while this is something that if wrong was always like that..
Thanks,
Ben
<In general, if I should start modify server settings for every issue particular users are facing, It will definitely lead to more trouble in the long run..
>
<set remote query timeout to 0 (or >600 based on your business logic)
it can help>
the recommended setting "0" can help your business to keep working while you try tpo find why these "few users " have the issue.
you should test it on some non prod sql server...
Also contact vendors to see if this is a "normal" error.
>
<set remote query timeout to 0 (or >600 based on your business logic)
it can help>
the recommended setting "0" can help your business to keep working while you try tpo find why these "few users " have the issue.
you should test it on some non prod sql server...
Also contact vendors to see if this is a "normal" error.
ASKER
@EugeneZ,
Ok will try modify that & let you know.
Thanks,
Ben
Ok will try modify that & let you know.
you should test it on some non prod sql server...What should I test in non prod server?
Also contact vendors to see if this is a "normal" error.You mean contact msft?
Thanks,
Ben
ASKER
@EugeneZ,
Thanks,
Ben
<set remote query timeout to 0 (or >600 based on your business logic)I did that and didn't help, any other suggestions?
it can help>
Thanks,
Ben
adjust ADP application connections string
and open case with them to see if on apps level they can set the front-end expiration setting adjustments for such users activities
it looks like front-end issues for these users
do you know how short is the short time? "the application unattended for a short time."
for some users several hours is "short" :)
thus - it can be a normal Apps functionality and users just need or close or re-login
and open case with them to see if on apps level they can set the front-end expiration setting adjustments for such users activities
it looks like front-end issues for these users
do you know how short is the short time? "the application unattended for a short time."
for some users several hours is "short" :)
thus - it can be a normal Apps functionality and users just need or close or re-login
ASKER
Hi EugeneZ,
Thanks,
Ben
untitled.png
adjust ADP application connections stringActually there is nothing I have been setting up for this except for providing user name and password as seen attached.
and open case with them to see..
it looks like front-end issues for these usersThey all share same app, therefore I dont think something with the FE is causing it.
do you know how short is the short time?This is something I will double check..
Thanks,
Ben
untitled.png
ASKER
do you know how short is the short time?According to users, just by leaving it unattended for about 10-15 Min the problem occurs.
They all share same app, therefore I dont think something with the FE is causing it.Very BAD practice. Every user should have his own copy of the FE. This avoids issues caused when one person who has the file open has a problem. Sharing the same physical copy of the file causes everyone to have a problem.
Sounds like your connection is dropping. See if you can get the tech folks to confirm this
ASKER
@Pat,
Thanks,
Ben
Every user should have his own copy of the FE.Sorry for having it wrong expressed..we do have a batch that creates for each user a private copy of the FE, I basically meant to say that we should not try to focus on the FE as we all use the same app logic.. and therefore if its only happening to one user, obviously its not the app at fault.
Sounds like your connection is dropping.I will do a ping test (ping myserverip -t >myfile) for a while there and see if something like that gets recorded.
Thanks,
Ben
ASKER
Just updating..
Thanks,
Ben
Sounds like your connection is dropping. See if you can get the tech folks to confirm thisThey are looking into this, hope to get results next week.
Thanks,
Ben
ASKER
Hi,
Believe it or not, I'm still waiting for users to confirm if replacing the network card solved the issue..
Hope to get that this week.
Thanks,
Ben
Believe it or not, I'm still waiting for users to confirm if replacing the network card solved the issue..
Hope to get that this week.
Thanks,
Ben
ASKER
Hi Experts,
Sorry for the delay, as I got shifted to different tasks..
Re this issue, we replaced the network card and problem is still happening (quite often), therefore whoever has a working solution is very welcome!
Thanks,
Ben
Sorry for the delay, as I got shifted to different tasks..
Re this issue, we replaced the network card and problem is still happening (quite often), therefore whoever has a working solution is very welcome!
Thanks,
Ben
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi,
The attached is what I saw in windows log, guess its kind of a network issue, however with our IT guy the story is as follows, the programmer/software is always the one to be blamed, as long I dont prove different..
Thanks,
Ben
Untitled.png
The attached is what I saw in windows log, guess its kind of a network issue, however with our IT guy the story is as follows, the programmer/software is always the one to be blamed, as long I dont prove different..
Thanks,
Ben
Untitled.png
For around $500, you can open a problem ticket with Microsoft and they will help you to debug the problem.
ASKER
Updated our IT guy, will wait few days for his solution in order to finalize.
Thanks,
Ben
Thanks,
Ben
ASKER
By looking into the logs we saw the problem, by switching the jack we fixed it.
Thank you!
Thank you!
You're welcome. It is always difficult debugging this type of problem since it requires involving other people who are more inclined to blame Access than look deeper.