MSrepl_errors source_type_id?

Does anyone know what the source_type_id values relate to. I have
errors with values of 5,4 and one.
I thought that they signified agent types but agent types are
1 Snapshot Agent
2 Log Reader Agent
3 Distribution Agent
4 Merge Agent
I am not using merge and there is no agent type of 5 so this is not it
Thanks
Bert
http://msdn.microsoft.com/library/de...f_m_e_9mlg.asp
bert wrote:
> Does anyone know what the source_type_id values relate to. I have
> errors with values of 5,4 and one.
> I thought that they signified agent types but agent types are
> 1 Snapshot Agent
> 2 Log Reader Agent
> 3 Distribution Agent
> 4 Merge Agent
> I am not using merge and there is no agent type of 5 so this is not
it
> Thanks
> Bert

Msg 242 when converting date from string (date in 'YYYY-MM-DD hh:mm:ss.ms' format)

MS SQL Server 2000 SP4 Spanish

It doesn't accept such values into query, although it shows them in this format.

select * from values where Dt > '2006-06-26 00:00:00.000'

returns with Msg 242,...

What am I doing wrong?

You have me baffled, because it seems to convert fine for me; however, try this in case it is a locale issue:

Code Snippet

select convert (datetime, '2006-06-26 00:00:00.000' , 121)
as explicitConversion

/*

explicitConversion
-

2006-06-26 00:00:00.000

*/

|||Explicit conversion works, but I need to get MS SQL Server to accept dates in this format (ODBC) |||

Ok, found problem. My fault.

Actually ODBC format requires {ts 'YYYY-MM-DD hh:mms'}, not just time string.

MSDTC problem ... I think ..

I have a SSIS package in which there are lot of Sequence Containers. Each sequence container has two Execute Sql tasks which brings 2 values, and if the comparison of the value is true, it runs a data flow task. Comparison is done using Expression.

If any of the sequence container fails the comparison, I wanted whole package to rollback so I had to use Transactions. I set "Required Transaction" on the package and "Supports Transaction" on each Sequence Container and Tasks respectively.

Now that I am trying to run the package, it runs few sequence containers fine and on few it gives this error.

[Execute SQL Task] Error: Executing the query "SELECT ISNULL(MAX(ClaimBillTypeKey), -1) ClaimBillTypeKey FROM dbo.Dim_ClaimBillType" failed with the following error: "Distributed transaction completed. Either enlist this session in a new transaction or the NULL transaction.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

Also, this is not consistent, one time one Seq. Cont will fail and next time it will run fine but something else will fail. What is going on?

Hello, please anyone? Help?|||

I encountered this issue on the RTM version of SSIS. It seem to occur primarily when we were accessing a SQL Server that was behind a firewall. We never did find a solution - we ended up implementing our own transaction and recovery logic.

I haven't tried it in SP1 or SP2, so I'm not sure if might have been fixed by one of those releases.