Hello all -
The past few weeks we have been seeing a couple error messages on three databases that are linked together. The message is either "Unrecognizable Database Format" or that the database is in an "inconsistent state". It happens on all three databases but not all at the same time.
I am able to fix the problem by having everyone log out of the databases/shut down their PCs and then doing a compact and repair on the database that is producing the error. The problem with that is that it stops the users from doing their work for 15-20 minutes while I get everyone out and do the repair. It may not seem like a lot of time but I work in a warehouse that has to get trucks out at specific times throughout the day and I try to disrupt their work day as little as possible so that everything runs on time.
Is there a specific reason that this is happening?
A little more background info... This mainly started happening more often (it is now basically a daily occurrence) when our company started migrating PCs from Windows 7 to Windows 10. All PCs should have Office 2013 on them now but there is a mix of Windows 7 and Windows 10 throughout the building.
I wondered if this was part of the problem. The good news is they are in the process of moving everyone over to Windows 10 and the conversion should be completed in the next couple weeks. If it is a result of multiple Windows versions we may be able to muddle through it until they are all complete but I'm not 100% sure that is the issue. We use other databases as well and they don't seem to have this issue. It's only the three that are linked and used by the most people.
Any light you could shine on this would be much appreciated.
Thank you in advance!
The past few weeks we have been seeing a couple error messages on three databases that are linked together. The message is either "Unrecognizable Database Format" or that the database is in an "inconsistent state". It happens on all three databases but not all at the same time.
I am able to fix the problem by having everyone log out of the databases/shut down their PCs and then doing a compact and repair on the database that is producing the error. The problem with that is that it stops the users from doing their work for 15-20 minutes while I get everyone out and do the repair. It may not seem like a lot of time but I work in a warehouse that has to get trucks out at specific times throughout the day and I try to disrupt their work day as little as possible so that everything runs on time.
Is there a specific reason that this is happening?
A little more background info... This mainly started happening more often (it is now basically a daily occurrence) when our company started migrating PCs from Windows 7 to Windows 10. All PCs should have Office 2013 on them now but there is a mix of Windows 7 and Windows 10 throughout the building.
I wondered if this was part of the problem. The good news is they are in the process of moving everyone over to Windows 10 and the conversion should be completed in the next couple weeks. If it is a result of multiple Windows versions we may be able to muddle through it until they are all complete but I'm not 100% sure that is the issue. We use other databases as well and they don't seem to have this issue. It's only the three that are linked and used by the most people.
Any light you could shine on this would be much appreciated.
Thank you in advance!