Fatal exception while firing a rule

Hi,

I am having a problem when moving our NS application from dev environment to testing environment. What happens, is that when the rule is fired, a fatal exception is generated.

Any hints how I can start hunting down what the source of the problem is. The thing is, this works in dev environment, but not in test. Further, if I try to execute the stored proc manually which fails (NS_MyAppApplication].[NSFire3]) I get the same error: A user request from the session with SPID 63 generated a fatal exception. SQL Server is terminating this session.

Both dev and test environments use same ADF and ICF files. The ADF file is pretty much like in the InventoryTracker sample, using ConditionAction element like this:

<ConditionAction>
<SqlLogin>NSRulesEvaluator</SqlLogin>
<SqlUser>NSRulesEvaluator</SqlUser>
<InputName>InventoryTrackerEvents</InputName>
<InputSchema>NS_InventoryTrackerApplication</InputSchema>
<SqlExpression>

INSERT INTO [NS_InventoryTrackerApplication].[InventoryTrackerNotifications]
(
[SubscriberId],
[DeviceName],
[SubscriberLocale],
[ProductId],
[ProductName],
[ProductNumber],
[Quantity],
[LocationName]
)

(
SELECT
r.[Subscription.SubscriberId],
r.[Subscription.DeviceName],
r.[Subscription.SubscriberLocale],
r.[Input.ProductId],
r.[Input.ProductName],
r.[Input.ProductNumber],
r.[Input.Quantity],
r.[Input.LocationName]

FROM [NS_InventoryTrackerApplication].InventoryTrackerRule AS r
)
</SqlExpression>
</ConditionAction>

I tried changing ADF to little simple version, using action element instead of conditionaction. This time I got it working (and before that normal error messages and not just a stack dump).

Any hints how I can find out what is the problem here, or am I possibly missing something totally?

//sami

Both servers are as below:

Microsoft SQL Server Management Studio 9.00.2047.00
Microsoft Analysis Services Client Tools 2005.090.2047.00
Microsoft Data Access Components (MDAC) 2000.086.1830.00 (srv03_sp1_rtm.050324-1447)
Microsoft MSXML 2.6 3.0 6.0
Microsoft Internet Explorer 6.0.3790.1830
Microsoft .NET Framework 2.0.50727.42
Operating System 5.2.3790

These are entries from application log (in reverse order):

--

Description: The running of the rule failed. Please check the rule.
EventParameters:
Application Name: MyApp
Quantum ID: 4513
Rule Firing ID: 17
Rule Name: MyAppRule
Notification Throttle: 1000
Event Class ID: 1
Subscription Class ID: 1
Rule ID: 3
Rule Action: INSERT INTO [NS_MyAppApplication].[MyAppNotifications]
(
[SubscriberId],
[DeviceName],
[SubscriberLocale],
[SomeData]
)

(
SELECT
r.[Subscription.SubscriberId],
r.[Subscription.DeviceName],
r.[Subscription.SubscriberLocale],
r.[Input.SomeData]
FROM [NS_MyAppApplication].MyAppRule AS r

)
Stored Procedure Name: [NS_MyAppApplication].[NSFire3]

SqlServerError:
Error Number: 0
Source: .Net SqlClient Data Provider
Number: 0
State: 0
Class: 11
Message: A severe error occurred on the current command. The results, if any, should be discarded.
Procedure:
Line Number: 0

Error Number: 1
Source: .Net SqlClient Data Provider
Number: 0
State: 0
Class: 20
Message: A severe error occurred on the current command. The results, if any, should be discarded.
Procedure:
Line Number: 0

Description: A severe error occurred on the current command. The results, if any, should be discarded.
A severe error occurred on the current command. The results, if any, should be discarded.
InstanceName: MyAppInstance
ApplicationName: MyApp
Component: Generator
Thread: 4

--

Notification Services performed a quantum status update.
EventParameters:
Application Name: MyApp
Quantum ID: 4513
Status Code: 128
Quantum Status Code: 135

InstanceName: MyAppInstance
ApplicationName: MyApp
Component: Generator
Thread: 4

--

A user request from the session with SPID 57 generated a fatal exception. SQL Server is terminating this session.

--

The generator has started firing a rule.
EventParameters:
Application Name: MyApp
Quantum ID: 4513
Rule Firing ID: 17
Rule Name: MyAppRule
Notification Throttle: 1000

InstanceName: MyAppInstance
ApplicationName: MyApp
Component: Generator
Thread: 4

I have been banging my head with this one. I tried creating the NS app from scracth. I managed to get it working again with <Action> element, using STMP notifications and XsltFormatter. After that I modified to solution, taking example from Shyams books userdefinedlogic sample. Got everything up and running, but when rule starts firing same thing happens again.

After that, I disabled the generator and did the debugging procedures. All went fine up to
NPPrepareRuleFiring. When I executed NSExecuteRuleFiring, bang! Fatal exception.. no additional information, sigh.

What I was wondering was that in the preparerulefiring resultset I got EventBatchId as null. Is this correct in this scenario?|||Hi,
have the same problem you have... did you find an answer?

Thanks

Ricardo Carvalho|||Have not had any luck with this. As a workaround I am using <action> element instead of <conditionaction>. I don't like it, but at the moment I have no other solution.

Fatal exception while firing a rule

Hi,

I am having a problem when moving our NS application from dev environment to testing environment. What happens, is that when the rule is fired, a fatal exception is generated.

Any hints how I can start hunting down what the source of the problem is. The thing is, this works in dev environment, but not in test. Further, if I try to execute the stored proc manually which fails (NS_MyAppApplication].[NSFire3]) I get the same error:A user request from the session with SPID 63 generated a fatal exception. SQL Server is terminating this session.

Both dev and test environments use same ADF and ICF files. The ADF file is pretty much like in the InventoryTracker sample, using ConditionAction element like this:

<ConditionAction>
<SqlLogin>NSRulesEvaluator</SqlLogin>
<SqlUser>NSRulesEvaluator</SqlUser>
<InputName>InventoryTrackerEvents</InputName>
<InputSchema>NS_InventoryTrackerApplication</InputSchema>
<SqlExpression>

INSERT INTO [NS_InventoryTrackerApplication].[InventoryTrackerNotifications]
(
[SubscriberId],
[DeviceName],
[SubscriberLocale],
[ProductId],
[ProductName],
[ProductNumber],
[Quantity],
[LocationName]
)

(
SELECT
r.[Subscription.SubscriberId],
r.[Subscription.DeviceName],
r.[Subscription.SubscriberLocale],
r.[Input.ProductId],
r.[Input.ProductName],
r.[Input.ProductNumber],
r.[Input.Quantity],
r.[Input.LocationName]

FROM [NS_InventoryTrackerApplication].InventoryTrackerRule AS r
)
</SqlExpression>
</ConditionAction>

I tried changing ADF to little simple version, using action element instead of conditionaction. This time I got it working (and before that normal error messages and not just a stack dump).

Any hints how I can find out what is the problem here, or am I possibly missing something totally?

//sami

Both servers are as below:

Microsoft SQL Server Management Studio 9.00.2047.00
Microsoft Analysis Services Client Tools 2005.090.2047.00
Microsoft Data Access Components (MDAC) 2000.086.1830.00 (srv03_sp1_rtm.050324-1447)
Microsoft MSXML 2.6 3.0 6.0
Microsoft Internet Explorer 6.0.3790.1830
Microsoft .NET Framework 2.0.50727.42
Operating System 5.2.3790

These are entries from application log (in reverse order):

--

Description: The running of the rule failed. Please check the rule.
EventParameters:
Application Name: MyApp
Quantum ID: 4513
Rule Firing ID: 17
Rule Name: MyAppRule
Notification Throttle: 1000
Event Class ID: 1
Subscription Class ID: 1
Rule ID: 3
Rule Action: INSERT INTO [NS_MyAppApplication].[MyAppNotifications]
(
[SubscriberId],
[DeviceName],
[SubscriberLocale],
[SomeData]
)

(
SELECT
r.[Subscription.SubscriberId],
r.[Subscription.DeviceName],
r.[Subscription.SubscriberLocale],
r.[Input.SomeData]
FROM [NS_MyAppApplication].MyAppRule AS r

)
Stored Procedure Name: [NS_MyAppApplication].[NSFire3]

SqlServerError:
Error Number: 0
Source: .Net SqlClient Data Provider
Number: 0
State: 0
Class: 11
Message: A severe error occurred on the current command. The results, if any, should be discarded.
Procedure:
Line Number: 0

Error Number: 1
Source: .Net SqlClient Data Provider
Number: 0
State: 0
Class: 20
Message: A severe error occurred on the current command. The results, if any, should be discarded.
Procedure:
Line Number: 0

Description: A severe error occurred on the current command. The results, if any, should be discarded.
A severe error occurred on the current command. The results, if any, should be discarded.
InstanceName: MyAppInstance
ApplicationName: MyApp
Component: Generator
Thread: 4

--

Notification Services performed a quantum status update.
EventParameters:
Application Name: MyApp
Quantum ID: 4513
Status Code: 128
Quantum Status Code: 135

InstanceName: MyAppInstance
ApplicationName: MyApp
Component: Generator
Thread: 4

--

A user request from the session with SPID 57 generated a fatal exception. SQL Server is terminating this session.

--

The generator has started firing a rule.
EventParameters:
Application Name: MyApp
Quantum ID: 4513
Rule Firing ID: 17
Rule Name: MyAppRule
Notification Throttle: 1000

InstanceName: MyAppInstance
ApplicationName: MyApp
Component: Generator
Thread: 4

I have been banging my head with this one. I tried creating the NS app from scracth. I managed to get it working again with <Action> element, using STMP notifications and XsltFormatter. After that I modified to solution, taking example from Shyams books userdefinedlogic sample. Got everything up and running, but when rule starts firing same thing happens again.

After that, I disabled the generator and did the debugging procedures. All went fine up to
NPPrepareRuleFiring. When I executed NSExecuteRuleFiring, bang! Fatal exception.. no additional information, sigh.

What I was wondering was that in the preparerulefiring resultset I got EventBatchId as null. Is this correct in this scenario?|||Hi,
have the same problem you have... did you find an answer?

Thanks

Ricardo Carvalho
|||Have not had any luck with this. As a workaround I am using <action> element instead of <conditionaction>. I don't like it, but at the moment I have no other solution.

Fatal exception while firing a rule

Hi,

I am having a problem when moving our NS application from dev environment to testing environment. What happens, is that when the rule is fired, a fatal exception is generated.

Any hints how I can start hunting down what the source of the problem is. The thing is, this works in dev environment, but not in test. Further, if I try to execute the stored proc manually which fails (NS_MyAppApplication].[NSFire3]) I get the same error: A user request from the session with SPID 63 generated a fatal exception. SQL Server is terminating this session.

Both dev and test environments use same ADF and ICF files. The ADF file is pretty much like in the InventoryTracker sample, using ConditionAction element like this:

<ConditionAction>
<SqlLogin>NSRulesEvaluator</SqlLogin>
<SqlUser>NSRulesEvaluator</SqlUser>
<InputName>InventoryTrackerEvents</InputName>
<InputSchema>NS_InventoryTrackerApplication</InputSchema>
<SqlExpression>

INSERT INTO [NS_InventoryTrackerApplication].[InventoryTrackerNotifications]
(
[SubscriberId],
[DeviceName],
[SubscriberLocale],
[ProductId],
[ProductName],
[ProductNumber],
[Quantity],
[LocationName]
)

(
SELECT
r.[Subscription.SubscriberId],
r.[Subscription.DeviceName],
r.[Subscription.SubscriberLocale],
r.[Input.ProductId],
r.[Input.ProductName],
r.[Input.ProductNumber],
r.[Input.Quantity],
r.[Input.LocationName]

FROM [NS_InventoryTrackerApplication].InventoryTrackerRule AS r
)
</SqlExpression>
</ConditionAction>

I tried changing ADF to little simple version, using action element instead of conditionaction. This time I got it working (and before that normal error messages and not just a stack dump).

Any hints how I can find out what is the problem here, or am I possibly missing something totally?

//sami

Both servers are as below:

Microsoft SQL Server Management Studio 9.00.2047.00
Microsoft Analysis Services Client Tools 2005.090.2047.00
Microsoft Data Access Components (MDAC) 2000.086.1830.00 (srv03_sp1_rtm.050324-1447)
Microsoft MSXML 2.6 3.0 6.0
Microsoft Internet Explorer 6.0.3790.1830
Microsoft .NET Framework 2.0.50727.42
Operating System 5.2.3790

These are entries from application log (in reverse order):

--

Description: The running of the rule failed. Please check the rule.
EventParameters:
Application Name: MyApp
Quantum ID: 4513
Rule Firing ID: 17
Rule Name: MyAppRule
Notification Throttle: 1000
Event Class ID: 1
Subscription Class ID: 1
Rule ID: 3
Rule Action: INSERT INTO [NS_MyAppApplication].[MyAppNotifications]
(
[SubscriberId],
[DeviceName],
[SubscriberLocale],
[SomeData]
)

(
SELECT
r.[Subscription.SubscriberId],
r.[Subscription.DeviceName],
r.[Subscription.SubscriberLocale],
r.[Input.SomeData]
FROM [NS_MyAppApplication].MyAppRule AS r

)
Stored Procedure Name: [NS_MyAppApplication].[NSFire3]

SqlServerError:
Error Number: 0
Source: .Net SqlClient Data Provider
Number: 0
State: 0
Class: 11
Message: A severe error occurred on the current command. The results, if any, should be discarded.
Procedure:
Line Number: 0

Error Number: 1
Source: .Net SqlClient Data Provider
Number: 0
State: 0
Class: 20
Message: A severe error occurred on the current command. The results, if any, should be discarded.
Procedure:
Line Number: 0

Description: A severe error occurred on the current command. The results, if any, should be discarded.
A severe error occurred on the current command. The results, if any, should be discarded.
InstanceName: MyAppInstance
ApplicationName: MyApp
Component: Generator
Thread: 4

--

Notification Services performed a quantum status update.
EventParameters:
Application Name: MyApp
Quantum ID: 4513
Status Code: 128
Quantum Status Code: 135

InstanceName: MyAppInstance
ApplicationName: MyApp
Component: Generator
Thread: 4

--

A user request from the session with SPID 57 generated a fatal exception. SQL Server is terminating this session.

--

The generator has started firing a rule.
EventParameters:
Application Name: MyApp
Quantum ID: 4513
Rule Firing ID: 17
Rule Name: MyAppRule
Notification Throttle: 1000

InstanceName: MyAppInstance
ApplicationName: MyApp
Component: Generator
Thread: 4

I have been banging my head with this one. I tried creating the NS app from scracth. I managed to get it working again with <Action> element, using STMP notifications and XsltFormatter. After that I modified to solution, taking example from Shyams books userdefinedlogic sample. Got everything up and running, but when rule starts firing same thing happens again.

After that, I disabled the generator and did the debugging procedures. All went fine up to
NPPrepareRuleFiring. When I executed NSExecuteRuleFiring, bang! Fatal exception.. no additional information, sigh.

What I was wondering was that in the preparerulefiring resultset I got EventBatchId as null. Is this correct in this scenario?|||Hi,
have the same problem you have... did you find an answer?

Thanks

Ricardo Carvalho|||Have not had any luck with this. As a workaround I am using <action> element instead of <conditionaction>. I don't like it, but at the moment I have no other solution.

Fatal Exception error

I have an application that has to work in a merge replicated environment. To
facilitate this we use @.@.Servername to put the name of the server that the
data is changed onto the table. I have an issue now with this problem
http://support.microsoft.com/defaul...B;en-us;270061&
and am wondering when it will be resolved if there is a better workaround; o
r a solution besides dropping the server and reinstalling it ?
Thanks
ChrisHi Chris:
According the KB article you provide, there is no need for reinstall,
what we should do is follow the workaround.
Is there a misunderstanding by me?
Best Wishes
Wei Ci Zhou|||Hi Chris,
Thank you for using the newsgroup and it is my pleasure to answer you
question.
From the knowledge base article
http://support.microsoft.com/defaul...B;en-us;270061&
There is a workaround to avoid it by:
exec sp_addserver 'WindowsNT_Machine_Name', 'local'
I will notify you as soon as possible to you any information about the fix
on this problem. If you still have questions about it, please feel free to
post message here and I am glad to help you. Thanks.
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.|||Wei,
Is there a timescale on the hotfix : i have 20 servers that i have to go thr
ough change control to try the fix : i dont have the issue with my dev / tes
t servers so am finding it hard to resolve.
Also i am interested to know what might cause the issue to have occured in t
eh first place !
many thanks|||Hi Chris,
Thank you for using the newsgroup and it is my pleasure to answer you
question.
The product group is aware of this issue. I cannot guarentee it.
Thanks!
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.

Fatal Exception error

I have an application that has to work in a merge replicated environment. To facilitate this we use @.@.Servername to put the name of the server that the data is changed onto the table. I have an issue now with this problem
http://support.microsoft.com/default.aspx?scid=KB;en-us;270061&
and am wondering when it will be resolved if there is a better workaround; or a solution besides dropping the server and reinstalling it ?
Thanks
ChrisHi Chris:
According the KB article you provide, there is no need for reinstall,
what we should do is follow the workaround.
Is there a misunderstanding by me?
Best Wishes
Wei Ci Zhou|||Hi Chris,
Thank you for using the newsgroup and it is my pleasure to answer you
question.
From the knowledge base article
http://support.microsoft.com/default.aspx?scid=KB;en-us;270061&
There is a workaround to avoid it by:
exec sp_addserver 'WindowsNT_Machine_Name', 'local'
I will notify you as soon as possible to you any information about the fix
on this problem. If you still have questions about it, please feel free to
post message here and I am glad to help you. Thanks.
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.|||Wei
Is there a timescale on the hotfix : i have 20 servers that i have to go through change control to try the fix : i dont have the issue with my dev / test servers so am finding it hard to resolve
Also i am interested to know what might cause the issue to have occured in teh first place
many thanks|||Hi Chris,
Thank you for using the newsgroup and it is my pleasure to answer you
question.
The product group is aware of this issue. I cannot guarentee it.
Thanks!
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.

Failure saving package

Hello All,

I have a package in the SQL 2000 environment that works fine. I have migrated this DTS Package to a SSIS Package using the Visual Studio 2005.

After that, i made some changes in this package and now I'm trying to save it but I am facing with this error message below:

TITLE: Microsoft Visual Studio

Failure saving package.

ADDITIONAL INFORMATION:

Invalid at the top level of the document.
(Microsoft OLEDB Persistence Provider)

Invalid at the top level of the document.
(Microsoft OLEDB Persistence Provider)

BUTTONS:

OK

Could someone please help me with this ?

Thanks in advance.

Thiago

Has anybody seen this issue resolved? I am experiencing the exact same issue.|||

hi guys,

Probably not very helpful for you but a few months ago I suffered the same and my solution was make a DTSX from the beginning...

|||

That's what I am doing at present but there are a couple of hundred of these that I need to change. If I have to build them all from scratch the project time is going to blow out considerably. The migration is not perfect (as I expected) but it does considerably speed up the conversion process.

The funny thing is that a couple seem to have converted cleanly but the majority haven't.

I will be putting in a support issue with Microsoft and I will report back with any findings.

|||

Everybody,

If you have any recordset object exists/present in your migrated DTS workflow, please manually convert those variables datatype into Object (If you are not able to modify the recordset variables, please re-create the variables with Object datatype). After changing all the recordset variables, most probabily you should be able to save the migrated SSIS workflow.

Thanks.

Regards,

Ezhilarasan Maharajan

|||

This seems to have solved my problem but I have some further testing to do.

Great catch. Thanks for responding to this.

|||I've finished my testing and this has defintely resolved my problem. I also updated my MS support issue with this information so hopefully a KB article and a fix in a future SP will be forthcoming.|||Thank you! It helps!

Failure saving package

Hello All,

I have a package in the SQL 2000 environment that works fine. I have migrated this DTS Package to a SSIS Package using the Visual Studio 2005.

After that, i made some changes in this package and now I'm trying to save it but I am facing with this error message below:

TITLE: Microsoft Visual Studio

Failure saving package.

ADDITIONAL INFORMATION:

Invalid at the top level of the document.
(Microsoft OLEDB Persistence Provider)

Invalid at the top level of the document.
(Microsoft OLEDB Persistence Provider)

BUTTONS:

OK

Could someone please help me with this ?

Thanks in advance.

Thiago

Has anybody seen this issue resolved? I am experiencing the exact same issue.|||

hi guys,

Probably not very helpful for you but a few months ago I suffered the same and my solution was make a DTSX from the beginning...

|||

That's what I am doing at present but there are a couple of hundred of these that I need to change. If I have to build them all from scratch the project time is going to blow out considerably. The migration is not perfect (as I expected) but it does considerably speed up the conversion process.

The funny thing is that a couple seem to have converted cleanly but the majority haven't.

I will be putting in a support issue with Microsoft and I will report back with any findings.

|||

Everybody,

If you have any recordset object exists/present in your migrated DTS workflow, please manually convert those variables datatype into Object (If you are not able to modify the recordset variables, please re-create the variables with Object datatype). After changing all the recordset variables, most probabily you should be able to save the migrated SSIS workflow.

Thanks.

Regards,

Ezhilarasan Maharajan

|||

This seems to have solved my problem but I have some further testing to do.

Great catch. Thanks for responding to this.

|||I've finished my testing and this has defintely resolved my problem. I also updated my MS support issue with this information so hopefully a KB article and a fix in a future SP will be forthcoming.|||Thank you! It helps!

Failure saving package

Hello All,

I have a package in the SQL 2000 environment that works fine. I have migrated this DTS Package to a SSIS Package using the Visual Studio 2005.

After that, i made some changes in this package and now I'm trying to save it but I am facing with this error message below:

TITLE: Microsoft Visual Studio

Failure saving package.

ADDITIONAL INFORMATION:

Invalid at the top level of the document.
(Microsoft OLEDB Persistence Provider)

Invalid at the top level of the document.
(Microsoft OLEDB Persistence Provider)

BUTTONS:

OK

Could someone please help me with this ?

Thanks in advance.

Thiago

Has anybody seen this issue resolved? I am experiencing the exact same issue.|||

hi guys,

Probably not very helpful for you but a few months ago I suffered the same and my solution was make a DTSX from the beginning...

|||

That's what I am doing at present but there are a couple of hundred of these that I need to change. If I have to build them all from scratch the project time is going to blow out considerably. The migration is not perfect (as I expected) but it does considerably speed up the conversion process.

The funny thing is that a couple seem to have converted cleanly but the majority haven't.

I will be putting in a support issue with Microsoft and I will report back with any findings.

|||

Everybody,

If you have any recordset object exists/present in your migrated DTS workflow, please manually convert those variables datatype into Object (If you are not able to modify the recordset variables, please re-create the variables with Object datatype). After changing all the recordset variables, most probabily you should be able to save the migrated SSIS workflow.

Thanks.

Regards,

Ezhilarasan Maharajan

|||

This seems to have solved my problem but I have some further testing to do.

Great catch. Thanks for responding to this.

|||I've finished my testing and this has defintely resolved my problem. I also updated my MS support issue with this information so hopefully a KB article and a fix in a future SP will be forthcoming.|||Thank you! It helps!

Failure Audit on domain controller account

I have SQL 2005 installed in a virtual (ESX) environment with a separate DC. Every minute or so an event shows up in the Application Event Log that says:

Type: Failure Audit

User: dgtest\dc1$

Computer: sql1

Source: MSSQLSERVER

Category: (4)

Event ID: 18456

Description:

Login failed for user 'dgtest\dc1$'. [Client: <ip address>]

Data includes: SQL1 master

Any idea what is causing this and how to fix it?

Thanks,
Mindy

Hi Mindy,

I have the same problem. I am running VS2005, SQL2005 in Win XP SP2. I am trying to install Biztalk Server 2006 and I get this error in the event viewer. Due to this error I cannot configure the Groups in Biztalk Server. Do you have any fix?

Thanks,

Sundar

|||Mindy, does this user exist on your box sql1?|||

Has any one found the solution for this problem

|||

I found the solution. It happens when you are specifying BizTalk Server Administrators and BizTalk Server Operators group as the local group. In this case the configuration qizard will try to find these user groups on the SQL machine. If the SQL machine is different from the BizTalk machine, it wil generate error.

To resolve this, just make these 2 groups as domain user groups and change these groups settings within the configuration wizard of BizTalk to domain groups.

|||

Sorry for the delayed response, I did not receive the thread notifications.

The user is actually the domain controller (dc1), not a regular user.

In my installation, there is no Biztalk, only MOSS.

The configuration of the environment (a test/dev environment) has changed significantly since I first posted, and the issue has gone away. Have other issues now, but they are not important ;-)

Mindy

Failure Audit on domain controller account

I have SQL 2005 installed in a virtual (ESX) environment with a separate DC. Every minute or so an event shows up in the Application Event Log that says:

Type: Failure Audit

User: dgtest\dc1$

Computer: sql1

Source: MSSQLSERVER

Category: (4)

Event ID: 18456

Description:

Login failed for user 'dgtest\dc1$'. [Client: <ip address>]

Data includes: SQL1 master

Any idea what is causing this and how to fix it?

Thanks,
Mindy

Hi Mindy,

I have the same problem. I am running VS2005, SQL2005 in Win XP SP2. I am trying to install Biztalk Server 2006 and I get this error in the event viewer. Due to this error I cannot configure the Groups in Biztalk Server. Do you have any fix?

Thanks,

Sundar

|||Mindy, does this user exist on your box sql1?|||

Has any one found the solution for this problem

|||

I found the solution. It happens when you are specifying BizTalk Server Administrators and BizTalk Server Operators group as the local group. In this case the configuration qizard will try to find these user groups on the SQL machine. If the SQL machine is different from the BizTalk machine, it wil generate error.

To resolve this, just make these 2 groups as domain user groups and change these groups settings within the configuration wizard of BizTalk to domain groups.

|||

Sorry for the delayed response, I did not receive the thread notifications.

The user is actually the domain controller (dc1), not a regular user.

In my installation, there is no Biztalk, only MOSS.

The configuration of the environment (a test/dev environment) has changed significantly since I first posted, and the issue has gone away. Have other issues now, but they are not important ;-)

Mindy

Failure Audit on domain controller account

I have SQL 2005 installed in a virtual (ESX) environment with a separate DC. Every minute or so an event shows up in the Application Event Log that says:

Type: Failure Audit

User: dgtest\dc1$

Computer: sql1

Source: MSSQLSERVER

Category: (4)

Event ID: 18456

Description:

Login failed for user 'dgtest\dc1$'. [Client: <ip address>]

Data includes: SQL1 master

Any idea what is causing this and how to fix it?

Thanks,
Mindy

Hi Mindy,

I have the same problem. I am running VS2005, SQL2005 in Win XP SP2. I am trying to install Biztalk Server 2006 and I get this error in the event viewer. Due to this error I cannot configure the Groups in Biztalk Server. Do you have any fix?

Thanks,

Sundar

|||Mindy, does this user exist on your box sql1?|||

Has any one found the solution for this problem

|||

I found the solution. It happens when you are specifying BizTalk Server Administrators and BizTalk Server Operators group as the local group. In this case the configuration qizard will try to find these user groups on the SQL machine. If the SQL machine is different from the BizTalk machine, it wil generate error.

To resolve this, just make these 2 groups as domain user groups and change these groups settings within the configuration wizard of BizTalk to domain groups.

|||

Sorry for the delayed response, I did not receive the thread notifications.

The user is actually the domain controller (dc1), not a regular user.

In my installation, there is no Biztalk, only MOSS.

The configuration of the environment (a test/dev environment) has changed significantly since I first posted, and the issue has gone away. Have other issues now, but they are not important ;-)

Mindy