RIP Dwain

did you reboot the server after installing the drivers?

Have you tried the odbc driver?[/url]

When there was sql server 2005

I meant, perhaps the windows logs (eventvwr) mentions why it couldn't write to the error logs.

SQL_Latin1_General_CP1_CI_AS isn't really an unicode character set. So it is possible that it displays Korean differently when connecting with another client.

Perhaps a difference on the client side

Unicode compatiblity

A note on...

Windows logs?

Statistics out of date?

Exception handling with a dialog box causing it to wait on user input?

From management studio

Navigate to Integration Services Catalog

Right-click SSISDB

Properties

In the section of Operations Log: Retention Period

In the section of Project Versions: Maximum number of versions per Project

Thanks for posting your solution

Can you query ACC from PRD through linked server?

Perhaps a firewall issue

I guess its Azure now.

Thanks for your input Brandie, got a possible workaround.

To the experts of DBCC TIMEWARP

Why can't system databases be restored "with move" like the others?

Example: RESTORE database model with move -> The system database cannot be moved by RESTORE

I would start them in this order

1.SSRS Server

2.SharePoint SQL (no connection errors to reports)

3.SharePoint Web (no connection errors to SharePoint sql)

Great story