emijohns
asked on
corrupt .mdb BE when using Citrix
I have a database with an XP FE and a 97 BE. The backend is on a shared server and the front end is either installed on the user's C:\... folder (typically Windows XP computer) or if they are off-campus and need to improve the response time, they use a Citrix server (Windows 2000 computer) and download a copy of the FE to their personal U:\ drive they can access when in Citrix.
Once we began using the Citrix terminal server with this database, we noticed the back end was corrupting every couple weeks which then turned into every couple of days. We took the away the access to use the Citrix server and it hasn't corrupted since.
Has anyone seen and resolved this type of issue? Let me know if there are any questions I can answer.
Thanks in advance for your help!
emijohns
Once we began using the Citrix terminal server with this database, we noticed the back end was corrupting every couple weeks which then turned into every couple of days. We took the away the access to use the Citrix server and it hasn't corrupted since.
Has anyone seen and resolved this type of issue? Let me know if there are any questions I can answer.
Thanks in advance for your help!
emijohns
ASKER
Thank you for the response nico. I am looking into that solution.
To my knowledge, no one has ever mentioned that they were kicked out of the database or Citrix while using the database. Although that doesn't mean it didn't happen. ;) The only calls I've received were from user's not able to open the database because the back end was corrupt.
I should also mention that the database is opened using Access XP runtime.
Thanks!
To my knowledge, no one has ever mentioned that they were kicked out of the database or Citrix while using the database. Although that doesn't mean it didn't happen. ;) The only calls I've received were from user's not able to open the database because the back end was corrupt.
I should also mention that the database is opened using Access XP runtime.
Thanks!
I guess you've activated a regular compact on the back end, or doesn't the size approach the max 2Gb?
Nic;o)
Nic;o)
ASKER
Yes, we compact every night. The size of the BE is about 14 MB. Not too big.
Hmm, hard to detect when you can't trace the actual session that's corrupting the .mdb.
Perhaps worthwhile to add a database decompile after the compact to make sure it's in "fresh" condition.
Nic;o)
Perhaps worthwhile to add a database decompile after the compact to make sure it's in "fresh" condition.
Nic;o)
ASKER
The solution we took was to move the db to another Citrix server running Windows 2003. We think the problem may have had something to do with OpsLock problems which would take some patches and other investigation. Since 2003 doesn't have the OpsLock problems (to our knowledge) the move was the easier/faster solution.
How do I handle points in this situation?
Thanks!
emijohns
How do I handle points in this situation?
Thanks!
emijohns
Just post a request for a PAQ/refund at CS: https://www.experts-exchange.com/Community_Support/
It's worth to save the info for future reference by other Citrix users !
Nic;o)
It's worth to save the info for future reference by other Citrix users !
Nic;o)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you nico! I really appreciate your help and discussion!
emijohns
emijohns
Discussions are my favorite "topic" :-)
Success with the application !
Nic;o)
Success with the application !
Nic;o)
https://www.experts-exchange.com/questions/20427450/Citrix-Access-Problems.html
Nic;o)