Error updating database

Rated 4.70/5 based on 514 customer reviews

f=255&MSPPError=-2147217396 Additionally after the installing and upgrading to ACE providers, you may run into the following error message, If you are in a scenario where you have both 32-bit and 64-bit processing being performed on the same server that needs to use the ACE data provider, from the Microsoft standpoint, it is recommended to have 2 different servers (1 to process 32-bit mode and the other for 64-bit mode).

But there is an option (workaround) where you can have both the versions installed on the same machine by performing a “/quiet” install of these components from command line.

If you have already updated the package from JET to ACE, then this will not show the connection manager and is not affected by this security update.

In a command prompt: Find /I “Jet” “C:\Sample Folder\Sample Package.dtsx” Alternatively, you can search the whole folder at once: Find /C /I “Jet” “C:\Sample Folder\%.dtsx” For more information on the Find command: Find: https://technet.microsoft.com/en-us/library/bb490906.aspx?

If you run a command prompt as an administrator, you can use the find command to look through the packages for the keyword JET.

This will state all the files it looks through, but you will see a connection manager result for the files that have this in them.

error updating database-62

error updating database-80

error updating database-26

error updating database-55

NET, or a distributed component running under COM services.

To do so, download the desired Access Database or Access Databae Engine_x64to your PC, open an administrative command prompt, and provide the installation path and switch /quiet. Please note that this approach is not recommended and haven't worked in few instances, so would request you to move to 2 different server approach if possible.

This patch seems to update Excel Jet connector from V4.00.9801.0 to v4.00.9801.1.

I understand that there are many users that don’t know how many packages might be experiencing this issue.

It is possible to look through your dtsx packages using the following method.

Leave a Reply