Applies to VISTA.

This should be fixed in office 2007 sp2 but if for some reason it is not fixed after the servicepack installation then you can do the following:

Now, MS puts that file there in the outlook.exe folder and if it’s not their
file but some other one things get broken and Outlook can’t start.

If you have that file in your outlook.exe folder open it in Notepad and make
sure it has an entry in there with this text “Microsoft.VC80.CRT”. If that’s
in there it’s the MS file and should be OK. If something else is there you
need to remove it and replace it with the original MS file.

The error message:

2705,”42S21″,[Microsoft][ODBC SQL Server Driever][SQL Server]Column names in each table must be unig. Column name ’securityoption’ in table ‘dbo.$ndo$dbproperty’ is specified more than once.

SQL:

ALTER TABLE [dbo].[$ndo$dbproperty] ADD securityoption INTEGER NOT NULL DEFAULT 0

Unfortunately, this error occurs quite often when “converting” a database. The problem is, that the field “securityoption” is added to the table “$ndo$dbproperty” in the beginning of a conversion. Once the upgrade fails, the transactions are not completely rolled back, the field “securityoption” still remains. Now if you try to convert again, this error is raised, because C/SIDE tries to add this column again.

To solve this, you have to delete the field “securityoption” manually from the table “$ndo$dbproperty” via Management Studio and run the conversion again.