login failed db-library network

I am getting this error when loggin in to our application connecting only to
a specific server.
We were experiencing some "db connection or not enabled errors" previously
and to solve the problem I installed the SQL Client Network Ulitities and
setup the TCP/IP protocol with the remote SQL server alias. Now the
application won't connec at all and get's "login failed db-library network".
I've uninstalled the Clinet Network Utilities, but it still won't connect.
Any ideas?
Thanks.
Jim in Alabama
Without the exact error message, it's hard to say. You will
need to provide more specifics - version of SQL Server,
exact error messages, how the application connects (DSN,
connection string, etc).
-Sue
On Mon, 9 Jan 2006 09:42:06 -0800, "KAI Network Admin"
<KAINetworkAdmin@.discussions.microsoft.com> wrote:

>I am getting this error when loggin in to our application connecting only to
>a specific server.
>We were experiencing some "db connection or not enabled errors" previously
>and to solve the problem I installed the SQL Client Network Ulitities and
>setup the TCP/IP protocol with the remote SQL server alias. Now the
>application won't connec at all and get's "login failed db-library network".
>I've uninstalled the Clinet Network Utilities, but it still won't connect.
>Any ideas?
>Thanks.
>Jim in Alabama

Logging: Can't disable Informational Events

I enabled Windows Events for OnError, OnTaskFailed, OnWarning for my package and subelements. However, even if no errors occur, I still get Informational Events generated even though those are disabled for all modules and packages.

Any way to disable Information Events? Is this an SSIS defect, or just an oddity of how it implements Windows Events?

Windows Event:
Source: SQLISPackage
Type: Information
Event ID: 12288
Description: Package "XXXXXX" started.

Event ID: 122289
Description: Package "XXXXXX" finished successfully.

faype02 wrote:

I enabled Windows Events for OnError, OnTaskFailed, OnWarning for my package and subelements. However, even if no errors occur, I still get Informational Events generated even though those are disabled for all modules and packages.

Any way to disable Information Events? Is this an SSIS defect, or just an oddity of how it implements Windows Events?

Windows Event:
Source: SQLISPackage
Type: Information
Event ID: 12288
Description: Package "XXXXXX" started.

Event ID: 122289
Description: Package "XXXXXX" finished successfully.

Oh yeah, I can reproduce that. Weird - I don't think those should be there.

[Microsoft follow-up] Is this a bug or by design?

-Jamie

|||

It appears that this is by design see:

http://www.microsoft.com/technet/prodtechnol/sql/2005/mgngssis.mspx

In section on "Custom Log Provider" it says:

"To facilitate operations management, SSIS packages always write some basic logging information to the Windows event log, even for packages that do not incorporate logging. SSIS packages write events for package initiation and package completion and they can be identified using either the SQLISPackage or SQLISService event sources."

It would be a lovely option to be able to disable this.

Regards

|||So if I have a package that executes every 30 seconds, I have no control over thousands of "package start" and "package finished" log events per day?

There must be a way to intercept these with an event handler in the package - how would this be done?