MSDTC issues
-
@JasGot said in MSDTC issues:
We use MSDTC heavily and this is a daily nuisance for 1 or 2 users, but rarely the same users.
The users are using SQL Server directly, or via an application that others users are using too?
-
What I'm really looking for is to determine if the issue is likely related to an account, or to a behaviour.
-
@scottalanmiller said in MSDTC issues:
What I'm really looking for is to determine if the issue is likely related to an account, or to a behaviour.
Behavior, as in task or action? Or operator error type of behavior?
-
@scottalanmiller said in MSDTC issues:
The users are using SQL Server directly, or via an application that others users are using too?
An application. 100 users. 1 suite of applications, all talking to a variety of dbs at the same sql server.
-
@scottalanmiller said in MSDTC issues:
related to an account
Most occurrences are with two users, but it has happened with several. These two users do most of the transactions that are suffering.
-
@JasGot said in MSDTC issues:
@scottalanmiller said in MSDTC issues:
The users are using SQL Server directly, or via an application that others users are using too?
An application. 100 users. 1 suite of applications, all talking to a variety of dbs at the same sql server.
If there is just one application, then it's "the user" so the accounts won't be a factor. So that tells us that it must be behaviour based.
-
@JasGot said in MSDTC issues:
@scottalanmiller said in MSDTC issues:
What I'm really looking for is to determine if the issue is likely related to an account, or to a behaviour.
Behavior, as in task or action? Or operator error type of behavior?
Task or action. It's not "who they are" but rather "what they are doing" that must be causing it. I assume that those users do some different task or do the same task differently than other people not experiencing the problem.
-
@JasGot said in MSDTC issues:
@scottalanmiller said in MSDTC issues:
related to an account
Most occurrences are with two users, but it has happened with several. These two users do most of the transactions that are suffering.
Seems most likely to be something like a poorly written query that they are most likely to be the ones running.
-
Well, we found how to fix the symptom, be we do not know why it is so.
This network is 10.1.10.0/23
The only users having trouble were on the 10.1.11.0 portion of the network.
There are no configuration mishaps anywhere in the workstation, servers, switches or routers.
It's just weird.
But the MSDTC errors have stopped, and the staff who were suffering are happy.
-
@JasGot said in MSDTC issues:
Well, we found how to fix the symptom, be we do not know why it is so.
This network is 10.1.10.0/23
The only users having trouble were on the 10.1.11.0 portion of the network.
There are no configuration mishaps anywhere in the workstation, servers, switches or routers.
It's just weird.
But the MSDTC errors have stopped, and the staff who were suffering are happy.
It sure does sound like a netmask error.
10.1.11.0 defined as /24 somewhere. Or even 10.1.10.0 set to /24 somewhere.
Since it was different users I would guess DHCP. Maybe dual DHCP servers on the net. I've ran into something like that and it was a real headache, very intermittent.
Wiresharkto the rescue when having problems like this. -
@JasGot said in MSDTC issues:
Well, we found how to fix the symptom, be we do not know why it is so.
This network is 10.1.10.0/23
The only users having trouble were on the 10.1.11.0 portion of the network.
There are no configuration mishaps anywhere in the workstation, servers, switches or routers.
It's just weird.
But the MSDTC errors have stopped, and the staff who were suffering are happy.
I'm in a network transition myself, and I've run along a sorta similar issue.. definitely a PITA to troubleshoot and solve...
