SQL Server 2005 Conflict With Outlook BCM

Apr 1, 2006

Hi,

I just installed the SQL Server 2005 eval version on my laptop to try it out and now Outlook crashes. There appears to be a conflict with Outlook Business Contact Manager, which might be running its own database under the covers.

When I try to start Outlook I get the error message "Business Contact Manager has encountered a problem and needs to close. We are sorry for the inconvenience". The button choices are Debug, Send Report Later and Don't Send. Clicking Don't Send closes Outlook.

I found some info on modifying the registry to disable BCM, which I did, but I still get the same error and Outlook won't start. I also tried removing all of the SQL Server 2005 stuff from my path environment variable but it didn't work either.

Any suggestions would be appreciated because I depend on Outlook for my email and contacts.

Thanks,

Mike

View 4 Replies

Email Report In Outlook 2007 Not The Same As Outlook 2003

Feb 7, 2007

I have a Reporting Services 2005 report that is emailed to users. I created/formatted the report based on how it looked in Outlook 2003 which all of our users had at that time. The report is wide, but just fit in the email window when it was full size. Now I have a user who has been converted to Outlook 2007 and he emailed me a copy of the report he received in Outlook 2007 and it looks like it reduced the column sizes; it does not fill the entire email window and wraps the wording on most lines because the column sizes have been reduced.

The report is:

Delivered by: Report Server E-mail

Include Report is checked

Render Format is Web archive

Any ideas on how I can fix this?

Thanks in advance.

View 23 Replies View Related

SQL Server 2005 X64 SP2 Conflict With Teradata Oledb? (class Not Registered)

Jul 23, 2007

SP2 for SQL Server 2005 x64 has been less than happy for me.

The initial problem, mentioned in another thread, concerned SSIS client which stopped liking Data Flow components. It was solved by a removal and reinstallation of the client tools.

However, there now seems to be a problem with making use of the Teradata oledb provider within SSIS. Prior to the installation of SP2 there was no problem.

I create a new SSIS package
Add a Data Flow component
Within the data flow add an oledb source
Create a new connection - using the Teradata oledb provider
Test the connection (it works!)
Use SQL something like "select * from some_teradata_table_on_the_TD_server"
Click on columns, wait a second, a list of columns is returned
Add a SQL Server destination (with a new SQL Server connection)
Connect the two components
Save the package

Click go
The TD oledb source component turns bright red and the error is "class not registered"

I have uninstalled the TD oledb provider (and underlying TD components) and re-installed (32-bit and 64-bit) - no change

Any ideas?

- KjM

View 7 Replies View Related

SQL Server 2005: Collation Conflict Error When Selecting Database Properties

Mar 27, 2006

I have just upgraded to SQL Server 2005 from SQL Server 2000.In Microsoft SQL Server Management Studio, when I click on databaseproperties, I receive the following error:-Cannot resolve the collation conflict between"Latin1_General_CI_AS"and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.(Microsoft SQL Server, Error: 468)Some reference suggest that I can change the database collation byclicking database properties!What can I do?

View 21 Replies View Related

Outlook And SQL Server

Dec 8, 1999

Can anyone recommend a source of info on connecting Outlook to a SQL database of contacts? Also interested in third party tools/solutions that I could just buy and customize.

I need to be able to get at data from my own VB apps, but it would be nice to dump contacts into Outlook for people taking laptops and CE machines on the road. Even nicer if they could use Outlook to update addresses and upload to SQL Server.

Or am I just dreaming?