Showing posts with label nor. Show all posts
Showing posts with label nor. Show all posts

Monday, March 26, 2012

Error during set partner statement (SP1)

Hi!

I have the following error during setting partner on mirror server
Msg 1431, Level 16, State 4, Line 1
Neither the partner nor the witness server instance for database "masterserver" is available. Reissue the command when at least one of the instances becomes available.

The partner is available through telnet. I've also checked ports vai netstat and have no found errors.

There are two noteworthy erros in the error log at mirror server
Error: 9642, Severity: 16, State: 3.
and
An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '')

Security settings it seems are set accurately.

Ok, find out the problem.
I leave database yesterday in restoring state and today morning it has recovering state.

When I synchronize logs again mirroring has worked fine. I think during server startup (I restarted server today morning) it tries to recover mirror database. It leads database status changing and impossibility to set up partner.

Sunday, February 26, 2012

error code from DTEXEC not 0 nor 1

I would like to send back to MS-DOS (ERRORLEVEL) an error code 2 ( different from 0 and 1) via a scripting Task.

Our package are started with the DTEXEC Utility.

In general, how can i send back a flag saying "There were warnings" during the execution of a Package

Warnings can happen with successful package executions, and for that matter, so can errors.

There are a numerous ways to figure out there were warnings though, such that a shell caller is aware of that fact.

One, capture the console output from dtexec and look through the captured text for the warning event.

Two, create a console utility which calls Package.Execute() and iterates through the .Warnings collection. If the count > 0, return what you want as the process exit code.

Three, use logging. Configure the package to use the native SSIS logging facilities to write log entires. Read the produced log provider for warning events.

Four, use a package level OnWarning event handler. Inside the event handler, set something external to the package (file, db, message queue, doesn't matter) which is readable post-execution.