Page 1 of 1
MSDTC Error
Posted: Fri Nov 15, 2013 3:54 pm
by skrusty
Hi, I've installed sip-sorcery 1.2 on an AWS instance connected to MSSQL RDS instance for testing.
Everything has been fine for about a week, until last night i noticed the log files full of the following error(s):
Code: Select all
Exception ExpireBindings Delete. Network access for Distributed Transaction Manager (MSDTC) has been disabled. Please enable DTC for network access in the security configuration for MSDTC using the Component Services Administrative tool.
and
Code: Select all
Exception MSSQLAssetPersistor Delete (for SIPRegistrarBinding). Network access for Distributed Transaction Manager (MSDTC) has been disabled. Please enable DTC for network access in the security configuration for MSDTC using the Component Services Administrative tool.
Can anyone shed any light on this? Why it's happening now and not before and how I can prevent it? Amazon RDS doesn't support DTC.
Is this an issue with the release on codeplex? Do I need to compile from src myself a newer version?
Thanks in advance for any help.
Ben
Re: MSDTC Error
Posted: Sat Nov 16, 2013 8:36 am
by Aaron
The sipsorcery application has never used distributed transactions so that error is a bit mystifying. It does use database transactions but that should not require any special firewall configuration. For the want of a better suggestion I'd try rebooting the instance.
Re: MSDTC Error
Posted: Sun Nov 17, 2013 7:41 pm
by skrusty
That didn't help, but I am wondering if the problem stems from another issue i encountered with the SQL Script for MSSQL.
When running the SQL Script to generate the db, i got the following error:
Code: Select all
Msg 1785, Level 16, State 0, Line 149
Introducing FOREIGN KEY constraint 'FK__sipprovid__provi__3A81B327' on table 'sipproviderbindings' may cause cycles or multiple cascade paths. Specify ON DELETE NO ACTION or ON UPDATE NO ACTION, or modify other FOREIGN KEY constraints.
Msg 1750, Level 16, State 0, Line 149
Could not create constraint. See previous errors.
I fixed it by removing part of the cascade, but maybe this created more issues than it solved?
Any pointers on how i should correct the issue with the SQL Script?
Thanks again for you help, and for creating such a great product!
Re: MSDTC Error
Posted: Mon Nov 18, 2013 9:33 am
by skrusty
FYI, by removing the following from the sipaccounts table:
Code: Select all
on delete cascade on update cascade,
I was able to run the SQL Script. This also fixed the MSDTC errors!
Re: MSDTC Error
Posted: Mon Nov 18, 2013 10:18 am
by Aaron
I haven't tested the MSSQL script for a long time in fact I'd be worried it wouldn't work with the latest code.
As for the SQL script change fixing the MSDTC error that's very strange and I couldn't hazard a guess on the reason.
Re: MSDTC Error
Posted: Mon Nov 18, 2013 10:21 am
by skrusty
What backend are you using then? MySQL as a standard now? There only errors i've seen on the latest code are relating to:
Code: Select all
Invalid column name 'CRMPersonName'.
Invalid column name 'CRMCompanyName'.
Invalid column name 'CRMPictureURL'.
Exception MonitorCalls Monitoring. Invalid column name 'SwitchboardLineName'.
Re: MSDTC Error
Posted: Mon Nov 18, 2013 10:38 am
by Aaron
Yes I use MySQL for testing and for the sipsorcery.com service.
Re: MSDTC Error
Posted: Mon Nov 18, 2013 11:37 am
by skrusty
I spoke too soon! Seems the MSDTC errors are back. After seemingly solving it last night, i looked at the log this morning and they've come back. So confusing...
Code: Select all
Exception MSSQLAssetPersistor Delete (for SIPRegistrarBinding). Network access for Distributed Transaction Manager (MSDTC) has been disabled. Please enable DTC for network access in the security configuration for MSDTC using the Component Services Administrative tool.
Exception ExpireBindings Delete. Network access for Distributed Transaction Manager (MSDTC) has been disabled.
Please enable DTC for network access in the security configuration for MSDTC using the Component Services Administrative tool.
I will look at this further today, but if all else fails, I may consider moving to MySQL for sip sorcery!