Error Description differs when logged with Redirect Rows compared with Debug mode

Hi,

Can any one please tell me how to get the complete error description for example when i dont Redirect Row for Error in OLEDB Source i get a detailed error message with column name as

[RCheck [385]] Error: There was an error with input column "CHECK_STATUS" (456) on input "OLE DB Destination Input" (398). The column status returned was: "The value could not be converted because of a potential loss of data.".

But when I set Redirect Row for error and use the Script component to log them into a Table with ErrorDescription based on ErrorColumnID it only gives me this.

The data value cannot be converted for reasons other than sign mismatch or data overflow.

Thanks

Sat

Can't make the FailComponent and RedirectRow error messages the same with stock OLEDB source component.

If you want to actually redirect AND get the original provider error message that you would get in Fail Component mode, well, that component has yet to be written by Microsoft.

Instead, as you're seeing, when performing redirection using the OLEDB source; only the generic ErrorCode => generic textual description is exposed via ComponentMetaData.GetErrorDescription().

With a custom component of course, you can amend error outputs with additional columns, which is exactly what I have had to do to circumvent this problem.

Error copying data to a remote sql server 2005 database.

When copying data to a remote SQL2K5 destination from a SQL2K5 source database, both using mixed sql server security mode, my job generates the following error:

[Transfer SQL Server Objects Task] Error: Execution failed with the following error: "Cannot apply value null to property Login: Value cannot be null..".

This occurs after the destination database tables have been truncated and replacement data from the source would begin to copy.

The same process can be successfully completed from the Management studio with a simple data export process. However, when I run the saved package again from the BI interface, I get this error.

My search engine searches have yielded numerous hits of others having the same problem with one microsoft rep indicating it was a bug and would be resolved in sp1. I am working with sp1. Oddly, there is only mention of this in the forums. No KB article from MS addresses the problem and I do not see it addressed elsewhere at sqlservercentral.

It appears that others have switched to Integrated Security and resolved the problem. However, I do not have that option with a remotely hosted database.

Does anyone have any information concerning this problem?

bug reports may be submitted here: SQL Server Feedback.

i suggest that you first check for the status of any existing bug report to avoid duplication.

Error Connecting SQL Server 2005

Hi There,
Any one can help me suggest what to do with below problem?
while install SQL Server 2005, there is no Authentication Mode Option
prompted out for users to select The Mixed Mode. This is installed using the
correct Copyright from Ms SQL Server 2005 CD with Standard Version, where it
having CD1 and CD2. After complete setup without any error message, when
trying to open the Ms SQL Server Management Studio and connect to the server,
there are error prompted out can not be connected. error message like below:
"an error has occurred while establishing a connection to the server. when
connecting to sql server 2005, this failure may be caused by the fact that
under the default settings sql server does not allow remote connections.
(provider: named pipes provider, error: 40 - could not open a connection to
sql server) (microsoft sql server, error: 2) "
Kindly advice
Thank you
Regards,
Carmen
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server/200711/1
As the error says, the default installation of SQL 2005 does not
allow remote connections.
You will have to enable remote connections and [optionally] start
the SQL Server Browser service.
Detailed information:
914277 - How to configure SQL Server 2005 to allow remote
connections
http://support.microsoft.com/?kbid=914277
__________________________________________________ _______
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
SQL troubleshooting: http://sql.veranoest.net
___ please respond in newsgroup, NOT by private email ___
"carmen413 via droptable.com" <u21749@.uwe> wrote on 23 nov 2007
in microsoft.public.sqlserver.server:

> Hi There,
> Any one can help me suggest what to do with below problem?
> while install SQL Server 2005, there is no Authentication Mode
> Option prompted out for users to select The Mixed Mode. This is
> installed using the correct Copyright from Ms SQL Server 2005 CD
> with Standard Version, where it having CD1 and CD2. After
> complete setup without any error message, when trying to open
> the Ms SQL Server Management Studio and connect to the server,
> there are error prompted out can not be connected. error message
> like below: "an error has occurred while establishing a
> connection to the server. when connecting to sql server 2005,
> this failure may be caused by the fact that under the default
> settings sql server does not allow remote connections.
> (provider: named pipes provider, error: 40 - could not open a
> connection to sql server) (microsoft sql server, error: 2) "
> Kindly advice
> Thank you
> Regards,
> Carmen
|||Hello Carmen,
SQL Server 2005' s authentication mode is Windows Authentication by default
and the "sa" account will be disabled by default.
So, you can change your authentication mode by connecting your SQL Server
instance using SSMS after the setup. Go to Server Properties and Security.
You'll see the authentication modes there. I want to stress that "sa"
account is disabled by default. You can enable it (if you really need that)
from the Security\Logins nodes.
To be able to connect to your SQL Server instance, you must ensure that your
SQL Server service is running. You can check it using SQL Server
Configuration Manager or Services MMC.
This is not about remote connections at all because Remote Connections is
enabled by default for Standard and Enterprise Editions of SQL Server 2005.
It's disabled for Express and Developer Editions of SQL Server 2005 by
default.
Ekrem ?nsoy
"carmen413 via droptable.com" <u21749@.uwe> wrote in message
news:7ba5d81d07de2@.uwe...
> Hi There,
> Any one can help me suggest what to do with below problem?
> while install SQL Server 2005, there is no Authentication Mode Option
> prompted out for users to select The Mixed Mode. This is installed using
> the
> correct Copyright from Ms SQL Server 2005 CD with Standard Version, where
> it
> having CD1 and CD2. After complete setup without any error message, when
> trying to open the Ms SQL Server Management Studio and connect to the
> server,
> there are error prompted out can not be connected. error message like
> below:
> "an error has occurred while establishing a connection to the server. when
> connecting to sql server 2005, this failure may be caused by the fact that
> under the default settings sql server does not allow remote connections.
> (provider: named pipes provider, error: 40 - could not open a connection
> to
> sql server) (microsoft sql server, error: 2) "
> Kindly advice
> Thank you
> Regards,
> Carmen
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums.aspx/sql-server/200711/1
>

Error Connecting SQL Server 2005

Hi There,
Any one can help me suggest what to do with below problem?
while install SQL Server 2005, there is no Authentication Mode Option
prompted out for users to select The Mixed Mode. This is installed using the
correct Copyright from Ms SQL Server 2005 CD with Standard Version, where it
having CD1 and CD2. After complete setup without any error message, when
trying to open the Ms SQL Server Management Studio and connect to the server,
there are error prompted out can not be connected. error message like below:
"an error has occurred while establishing a connection to the server. when
connecting to sql server 2005, this failure may be caused by the fact that
under the default settings sql server does not allow remote connections.
(provider: named pipes provider, error: 40 - could not open a connection to
sql server) (microsoft sql server, error: 2) "
Kindly advice
Thank you
Regards,
Carmen
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200711/1As the error says, the default installation of SQL 2005 does not
allow remote connections.
You will have to enable remote connections and [optionally] start
the SQL Server Browser service.
Detailed information:
914277 - How to configure SQL Server 2005 to allow remote
connections
http://support.microsoft.com/?kbid=914277
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
SQL troubleshooting: http://sql.veranoest.net
___ please respond in newsgroup, NOT by private email ___
"carmen413 via SQLMonster.com" <u21749@.uwe> wrote on 23 nov 2007
in microsoft.public.sqlserver.server:
> Hi There,
> Any one can help me suggest what to do with below problem?
> while install SQL Server 2005, there is no Authentication Mode
> Option prompted out for users to select The Mixed Mode. This is
> installed using the correct Copyright from Ms SQL Server 2005 CD
> with Standard Version, where it having CD1 and CD2. After
> complete setup without any error message, when trying to open
> the Ms SQL Server Management Studio and connect to the server,
> there are error prompted out can not be connected. error message
> like below: "an error has occurred while establishing a
> connection to the server. when connecting to sql server 2005,
> this failure may be caused by the fact that under the default
> settings sql server does not allow remote connections.
> (provider: named pipes provider, error: 40 - could not open a
> connection to sql server) (microsoft sql server, error: 2) "
> Kindly advice
> Thank you
> Regards,
> Carmen|||Hello Carmen,
SQL Server 2005' s authentication mode is Windows Authentication by default
and the "sa" account will be disabled by default.
So, you can change your authentication mode by connecting your SQL Server
instance using SSMS after the setup. Go to Server Properties and Security.
You'll see the authentication modes there. I want to stress that "sa"
account is disabled by default. You can enable it (if you really need that)
from the Security\Logins nodes.
To be able to connect to your SQL Server instance, you must ensure that your
SQL Server service is running. You can check it using SQL Server
Configuration Manager or Services MMC.
This is not about remote connections at all because Remote Connections is
enabled by default for Standard and Enterprise Editions of SQL Server 2005.
It's disabled for Express and Developer Editions of SQL Server 2005 by
default.
--
Ekrem Ã?nsoy
"carmen413 via SQLMonster.com" <u21749@.uwe> wrote in message
news:7ba5d81d07de2@.uwe...
> Hi There,
> Any one can help me suggest what to do with below problem?
> while install SQL Server 2005, there is no Authentication Mode Option
> prompted out for users to select The Mixed Mode. This is installed using
> the
> correct Copyright from Ms SQL Server 2005 CD with Standard Version, where
> it
> having CD1 and CD2. After complete setup without any error message, when
> trying to open the Ms SQL Server Management Studio and connect to the
> server,
> there are error prompted out can not be connected. error message like
> below:
> "an error has occurred while establishing a connection to the server. when
> connecting to sql server 2005, this failure may be caused by the fact that
> under the default settings sql server does not allow remote connections.
> (provider: named pipes provider, error: 40 - could not open a connection
> to
> sql server) (microsoft sql server, error: 2) "
> Kindly advice
> Thank you
> Regards,
> Carmen
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200711/1
>

Error Connecting SQL Server 2005

Hi There,
Any one can help me suggest what to do with below problem?
while install SQL Server 2005, there is no Authentication Mode Option
prompted out for users to select The Mixed Mode. This is installed using the
correct Copyright from Ms SQL Server 2005 CD with Standard Version, where it
having CD1 and CD2. After complete setup without any error message, when
trying to open the Ms SQL Server Management Studio and connect to the server
,
there are error prompted out can not be connected. error message like below:
"an error has occurred while establishing a connection to the server. when
connecting to sql server 2005, this failure may be caused by the fact that
under the default settings sql server does not allow remote connections.
(provider: named pipes provider, error: 40 - could not open a connection to
sql server) (microsoft sql server, error: 2) "
Kindly advice
Thank you
Regards,
Carmen
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200711/1As the error says, the default installation of SQL 2005 does not
allow remote connections.
You will have to enable remote connections and [optionally] start
the SQL Server Browser service.
Detailed information:
914277 - How to configure SQL Server 2005 to allow remote
connections
http://support.microsoft.com/?kbid=914277
________________________________________
_________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
SQL troubleshooting: http://sql.veranoest.net
___ please respond in newsgroup, NOT by private email ___
"carmen413 via droptable.com" <u21749@.uwe> wrote on 23 nov 2007
in microsoft.public.sqlserver.server:

> Hi There,
> Any one can help me suggest what to do with below problem?
> while install SQL Server 2005, there is no Authentication Mode
> Option prompted out for users to select The Mixed Mode. This is
> installed using the correct Copyright from Ms SQL Server 2005 CD
> with Standard Version, where it having CD1 and CD2. After
> complete setup without any error message, when trying to open
> the Ms SQL Server Management Studio and connect to the server,
> there are error prompted out can not be connected. error message
> like below: "an error has occurred while establishing a
> connection to the server. when connecting to sql server 2005,
> this failure may be caused by the fact that under the default
> settings sql server does not allow remote connections.
> (provider: named pipes provider, error: 40 - could not open a
> connection to sql server) (microsoft sql server, error: 2) "
> Kindly advice
> Thank you
> Regards,
> Carmen|||Hello Carmen,
SQL Server 2005' s authentication mode is Windows Authentication by default
and the "sa" account will be disabled by default.
So, you can change your authentication mode by connecting your SQL Server
instance using SSMS after the setup. Go to Server Properties and Security.
You'll see the authentication modes there. I want to stress that "sa"
account is disabled by default. You can enable it (if you really need that)
from the Security\Logins nodes.
To be able to connect to your SQL Server instance, you must ensure that your
SQL Server service is running. You can check it using SQL Server
Configuration Manager or Services MMC.
This is not about remote connections at all because Remote Connections is
enabled by default for Standard and Enterprise Editions of SQL Server 2005.
It's disabled for Express and Developer Editions of SQL Server 2005 by
default.
Ekrem ?nsoy
"carmen413 via droptable.com" <u21749@.uwe> wrote in message
news:7ba5d81d07de2@.uwe...
> Hi There,
> Any one can help me suggest what to do with below problem?
> while install SQL Server 2005, there is no Authentication Mode Option
> prompted out for users to select The Mixed Mode. This is installed using
> the
> correct Copyright from Ms SQL Server 2005 CD with Standard Version, where
> it
> having CD1 and CD2. After complete setup without any error message, when
> trying to open the Ms SQL Server Management Studio and connect to the
> server,
> there are error prompted out can not be connected. error message like
> below:
> "an error has occurred while establishing a connection to the server. when
> connecting to sql server 2005, this failure may be caused by the fact that
> under the default settings sql server does not allow remote connections.
> (provider: named pipes provider, error: 40 - could not open a connection
> to
> sql server) (microsoft sql server, error: 2) "
> Kindly advice
> Thank you
> Regards,
> Carmen
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200711/1
>