Showing posts with label manager. Show all posts
Showing posts with label manager. Show all posts

Friday, March 30, 2012

MSSQL 2000- Backup Activity on a Network Machine

Hi,
I am using an Enterprise Manager and i have created a Database Maintainance Plan, can anybody guide me as to how to create backup on a remote machine.

I also mapped that device(say M/c B) onto my server box(M/c A) but i am not able to see that particular location in my backup activity screen.

Can this be done in the first place ?

Regards,
Tahirwe need some clarification.

do you want to backup databases on machine A to machine B or do you want to manage backups of databases that are on machine B from machine A?|||Yes i want to backup databases on machine A to machine B through Enterprize manager.|||While doing the backup on a networked remote machine which has been given full rights the job fails giving this error

BACKUP failed to complete the command BACKUP DATABASE [qa_tm_bdr_fix2] TO DISK = N'\\192.168.156.7\DBBackup\MUMSV075\qa_tm_bdr_fix2 _db_200612262300.BAK' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT|||Is your SQL Instance on A running under the system-account? The system account had no rights on B.

But there should be a more useful messge somewhere about why the job fails. Maybe in the errorlog? Have looked at the details in the jobhistory?|||Lexiflex is right. Make sure that the service account running the SQL server on B has enough permissions on the share (on A) where it should write the backup file. So in your case the account under which SQL Server B is running should have the permissions on the \\192.168.156.7\DBBackup share. I assume you allready shared the folder ... The problem Lexiflex is referring to is that the 'local system account' from machine A is not the same as the 'local system account' on machine B ... although it looks like it's the same one, it's definitely not ! You shouldn't run SQL Server under the local system account ... ever.

Been there, done that, worked fine.

Gr,
Yveau|||I am betting this is the problem as well. You will need to change the sql server and sql agent accounts to run under a domain account that has rights to your backup location.|||Thanks a lot for all ur help......it works......

Regards,
Tahir

Friday, March 23, 2012

msmsql.exe is eating my resources during backup.

I had the task manager open on Windows Small Business Server 2000 during the
last half of the backup and I took a peek every so often. In the last 15
minutes the backup started copying the sql databases on the Small Business
Server. The free memory went from 68% to 10% and stays at 10% after the
backup has finished. The CPU usage also soared to 100% during the backup of
these databases (which took maybe 5 to 7 minutes).
When I switched over to the processes tab sure enough sqlservr.exe was the
one eating up all the resources. After the databases were finished the cpu
usage went back to normal as it finished the rest of the backup but the mem
usage is still the same, even well after the backup finished.
The Backup Exec 9.1 server with backup exec sp3 is a Windows 2000 terminal
server box. I have the SQL backup portion of the backup job configured as
follows:
Backup Method: Full - Back up entire database or filegroup
Consistency Check before Backup: Full check, including indexes
Continue with backup if consistency check fails: checked
Consistency Check after Backup: Full check, including indexes
The backups are succeeding though, and several backups without any reboots
doesn't seem to lower my resources much more. The SBS server currently has 7
%
virtual memory, 280mb of free ram (out of 4gigs) and the cpu usage is 15% to
20%. After the backups. My sqlserv.exe on the SBS server is currently using
1% to 2% of the cpu, 1.7gigs of ram, and 1.7gigs of virtual memory. This is
all after I think two succesful 5-hour full backups with no reboots.
My concern here is that the sql service is eating up more memory than it
needs to because it’s not releasing it when its done the backup. I've trie
d
running a ram defragmenter/washer but the most effective solution is a reboo
t
after each backup. Is there anything I can do to either in Backup Exec, or o
n
the SBS SQL server so that the resources are released when the backup is
complete, or is there a way to stop sql from eating all the resources in the
first place?
Both servers have sql sp3a and the symantec sasser identification tool I ran
claims both servers are secure so I've already elininated that obvious
suggestion for you.
I'm looking for some sort of tweak solution, not necessarily reboot, or
start and stop mssql services before and after the reboot, so If you can
help, I'd greatly appreciate the assistance, because Veritas is doing little
to help me.
And yes, I'm inquiring about this because this is creating performance
issues that sometimes causes the servers to hang or network connectivity to
be lost.Hi
Have a look at this
http://support.microsoft.com/defaul...kb;en-us;321363
It is by design. Once other applications ask for memory, SQL Server gives it
back.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Ryan" <Ryan@.discussions.microsoft.com> wrote in message
news:20F4D8B6-EC0B-455B-94B7-38EBFADDC892@.microsoft.com...
>I had the task manager open on Windows Small Business Server 2000 during
>the
> last half of the backup and I took a peek every so often. In the last 15
> minutes the backup started copying the sql databases on the Small Business
> Server. The free memory went from 68% to 10% and stays at 10% after the
> backup has finished. The CPU usage also soared to 100% during the backup
> of
> these databases (which took maybe 5 to 7 minutes).
> When I switched over to the processes tab sure enough sqlservr.exe was the
> one eating up all the resources. After the databases were finished the cpu
> usage went back to normal as it finished the rest of the backup but the
> mem
> usage is still the same, even well after the backup finished.
> The Backup Exec 9.1 server with backup exec sp3 is a Windows 2000 terminal
> server box. I have the SQL backup portion of the backup job configured as
> follows:
> Backup Method: Full - Back up entire database or filegroup
> Consistency Check before Backup: Full check, including indexes
> Continue with backup if consistency check fails: checked
> Consistency Check after Backup: Full check, including indexes
> The backups are succeeding though, and several backups without any reboots
> doesn't seem to lower my resources much more. The SBS server currently has
> 7%
> virtual memory, 280mb of free ram (out of 4gigs) and the cpu usage is 15%
> to
> 20%. After the backups. My sqlserv.exe on the SBS server is currently
> using
> 1% to 2% of the cpu, 1.7gigs of ram, and 1.7gigs of virtual memory. This
> is
> all after I think two succesful 5-hour full backups with no reboots.
> My concern here is that the sql service is eating up more memory than it
> needs to because it's not releasing it when its done the backup. I've
> tried
> running a ram defragmenter/washer but the most effective solution is a
> reboot
> after each backup. Is there anything I can do to either in Backup Exec, or
> on
> the SBS SQL server so that the resources are released when the backup is
> complete, or is there a way to stop sql from eating all the resources in
> the
> first place?
> Both servers have sql sp3a and the symantec sasser identification tool I
> ran
> claims both servers are secure so I've already elininated that obvious
> suggestion for you.
> I'm looking for some sort of tweak solution, not necessarily reboot, or
> start and stop mssql services before and after the reboot, so If you can
> help, I'd greatly appreciate the assistance, because Veritas is doing
> little
> to help me.
> And yes, I'm inquiring about this because this is creating performance
> issues that sometimes causes the servers to hang or network connectivity
> to
> be lost.

msmsql.exe is eating my resources during backup.

I had the task manager open on Windows Small Business Server 2000 during the
last half of the backup and I took a peek every so often. In the last 15
minutes the backup started copying the sql databases on the Small Business
Server. The free memory went from 68% to 10% and stays at 10% after the
backup has finished. The CPU usage also soared to 100% during the backup of
these databases (which took maybe 5 to 7 minutes).
When I switched over to the processes tab sure enough sqlservr.exe was the
one eating up all the resources. After the databases were finished the cpu
usage went back to normal as it finished the rest of the backup but the mem
usage is still the same, even well after the backup finished.
The Backup Exec 9.1 server with backup exec sp3 is a Windows 2000 terminal
server box. I have the SQL backup portion of the backup job configured as
follows:
Backup Method: Full - Back up entire database or filegroup
Consistency Check before Backup: Full check, including indexes
Continue with backup if consistency check fails: checked
Consistency Check after Backup: Full check, including indexes
The backups are succeeding though, and several backups without any reboots
doesn't seem to lower my resources much more. The SBS server currently has 7%
virtual memory, 280mb of free ram (out of 4gigs) and the cpu usage is 15% to
20%. After the backups. My sqlserv.exe on the SBS server is currently using
1% to 2% of the cpu, 1.7gigs of ram, and 1.7gigs of virtual memory. This is
all after I think two succesful 5-hour full backups with no reboots.
My concern here is that the sql service is eating up more memory than it
needs to because it’s not releasing it when its done the backup. I've tried
running a ram defragmenter/washer but the most effective solution is a reboot
after each backup. Is there anything I can do to either in Backup Exec, or on
the SBS SQL server so that the resources are released when the backup is
complete, or is there a way to stop sql from eating all the resources in the
first place?
Both servers have sql sp3a and the symantec sasser identification tool I ran
claims both servers are secure so I've already elininated that obvious
suggestion for you.
I'm looking for some sort of tweak solution, not necessarily reboot, or
start and stop mssql services before and after the reboot, so If you can
help, I'd greatly appreciate the assistance, because Veritas is doing little
to help me.
And yes, I'm inquiring about this because this is creating performance
issues that sometimes causes the servers to hang or network connectivity to
be lost.
Hi
Have a look at this
http://support.microsoft.com/default...b;en-us;321363
It is by design. Once other applications ask for memory, SQL Server gives it
back.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Ryan" <Ryan@.discussions.microsoft.com> wrote in message
news:20F4D8B6-EC0B-455B-94B7-38EBFADDC892@.microsoft.com...
>I had the task manager open on Windows Small Business Server 2000 during
>the
> last half of the backup and I took a peek every so often. In the last 15
> minutes the backup started copying the sql databases on the Small Business
> Server. The free memory went from 68% to 10% and stays at 10% after the
> backup has finished. The CPU usage also soared to 100% during the backup
> of
> these databases (which took maybe 5 to 7 minutes).
> When I switched over to the processes tab sure enough sqlservr.exe was the
> one eating up all the resources. After the databases were finished the cpu
> usage went back to normal as it finished the rest of the backup but the
> mem
> usage is still the same, even well after the backup finished.
> The Backup Exec 9.1 server with backup exec sp3 is a Windows 2000 terminal
> server box. I have the SQL backup portion of the backup job configured as
> follows:
> Backup Method: Full - Back up entire database or filegroup
> Consistency Check before Backup: Full check, including indexes
> Continue with backup if consistency check fails: checked
> Consistency Check after Backup: Full check, including indexes
> The backups are succeeding though, and several backups without any reboots
> doesn't seem to lower my resources much more. The SBS server currently has
> 7%
> virtual memory, 280mb of free ram (out of 4gigs) and the cpu usage is 15%
> to
> 20%. After the backups. My sqlserv.exe on the SBS server is currently
> using
> 1% to 2% of the cpu, 1.7gigs of ram, and 1.7gigs of virtual memory. This
> is
> all after I think two succesful 5-hour full backups with no reboots.
> My concern here is that the sql service is eating up more memory than it
> needs to because it's not releasing it when its done the backup. I've
> tried
> running a ram defragmenter/washer but the most effective solution is a
> reboot
> after each backup. Is there anything I can do to either in Backup Exec, or
> on
> the SBS SQL server so that the resources are released when the backup is
> complete, or is there a way to stop sql from eating all the resources in
> the
> first place?
> Both servers have sql sp3a and the symantec sasser identification tool I
> ran
> claims both servers are secure so I've already elininated that obvious
> suggestion for you.
> I'm looking for some sort of tweak solution, not necessarily reboot, or
> start and stop mssql services before and after the reboot, so If you can
> help, I'd greatly appreciate the assistance, because Veritas is doing
> little
> to help me.
> And yes, I'm inquiring about this because this is creating performance
> issues that sometimes causes the servers to hang or network connectivity
> to
> be lost.

msmsql.exe is eating my resources during backup.

I had the task manager open on Windows Small Business Server 2000 during the
last half of the backup and I took a peek every so often. In the last 15
minutes the backup started copying the sql databases on the Small Business
Server. The free memory went from 68% to 10% and stays at 10% after the
backup has finished. The CPU usage also soared to 100% during the backup of
these databases (which took maybe 5 to 7 minutes).
When I switched over to the processes tab sure enough sqlservr.exe was the
one eating up all the resources. After the databases were finished the cpu
usage went back to normal as it finished the rest of the backup but the mem
usage is still the same, even well after the backup finished.
The Backup Exec 9.1 server with backup exec sp3 is a Windows 2000 terminal
server box. I have the SQL backup portion of the backup job configured as
follows:
Backup Method: Full - Back up entire database or filegroup
Consistency Check before Backup: Full check, including indexes
Continue with backup if consistency check fails: checked
Consistency Check after Backup: Full check, including indexes
The backups are succeeding though, and several backups without any reboots
doesn't seem to lower my resources much more. The SBS server currently has 7%
virtual memory, 280mb of free ram (out of 4gigs) and the cpu usage is 15% to
20%. After the backups. My sqlserv.exe on the SBS server is currently using
1% to 2% of the cpu, 1.7gigs of ram, and 1.7gigs of virtual memory. This is
all after I think two succesful 5-hour full backups with no reboots.
My concern here is that the sql service is eating up more memory than it
needs to because itâ's not releasing it when its done the backup. I've tried
running a ram defragmenter/washer but the most effective solution is a reboot
after each backup. Is there anything I can do to either in Backup Exec, or on
the SBS SQL server so that the resources are released when the backup is
complete, or is there a way to stop sql from eating all the resources in the
first place?
Both servers have sql sp3a and the symantec sasser identification tool I ran
claims both servers are secure so I've already elininated that obvious
suggestion for you.
I'm looking for some sort of tweak solution, not necessarily reboot, or
start and stop mssql services before and after the reboot, so If you can
help, I'd greatly appreciate the assistance, because Veritas is doing little
to help me.
And yes, I'm inquiring about this because this is creating performance
issues that sometimes causes the servers to hang or network connectivity to
be lost.Hi
Have a look at this
http://support.microsoft.com/default.aspx?scid=kb;en-us;321363
It is by design. Once other applications ask for memory, SQL Server gives it
back.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Ryan" <Ryan@.discussions.microsoft.com> wrote in message
news:20F4D8B6-EC0B-455B-94B7-38EBFADDC892@.microsoft.com...
>I had the task manager open on Windows Small Business Server 2000 during
>the
> last half of the backup and I took a peek every so often. In the last 15
> minutes the backup started copying the sql databases on the Small Business
> Server. The free memory went from 68% to 10% and stays at 10% after the
> backup has finished. The CPU usage also soared to 100% during the backup
> of
> these databases (which took maybe 5 to 7 minutes).
> When I switched over to the processes tab sure enough sqlservr.exe was the
> one eating up all the resources. After the databases were finished the cpu
> usage went back to normal as it finished the rest of the backup but the
> mem
> usage is still the same, even well after the backup finished.
> The Backup Exec 9.1 server with backup exec sp3 is a Windows 2000 terminal
> server box. I have the SQL backup portion of the backup job configured as
> follows:
> Backup Method: Full - Back up entire database or filegroup
> Consistency Check before Backup: Full check, including indexes
> Continue with backup if consistency check fails: checked
> Consistency Check after Backup: Full check, including indexes
> The backups are succeeding though, and several backups without any reboots
> doesn't seem to lower my resources much more. The SBS server currently has
> 7%
> virtual memory, 280mb of free ram (out of 4gigs) and the cpu usage is 15%
> to
> 20%. After the backups. My sqlserv.exe on the SBS server is currently
> using
> 1% to 2% of the cpu, 1.7gigs of ram, and 1.7gigs of virtual memory. This
> is
> all after I think two succesful 5-hour full backups with no reboots.
> My concern here is that the sql service is eating up more memory than it
> needs to because it's not releasing it when its done the backup. I've
> tried
> running a ram defragmenter/washer but the most effective solution is a
> reboot
> after each backup. Is there anything I can do to either in Backup Exec, or
> on
> the SBS SQL server so that the resources are released when the backup is
> complete, or is there a way to stop sql from eating all the resources in
> the
> first place?
> Both servers have sql sp3a and the symantec sasser identification tool I
> ran
> claims both servers are secure so I've already elininated that obvious
> suggestion for you.
> I'm looking for some sort of tweak solution, not necessarily reboot, or
> start and stop mssql services before and after the reboot, so If you can
> help, I'd greatly appreciate the assistance, because Veritas is doing
> little
> to help me.
> And yes, I'm inquiring about this because this is creating performance
> issues that sometimes causes the servers to hang or network connectivity
> to
> be lost.sql

MSMQ did not make MQIS database in SQL 2000

I believe this is why I am having a error at boot from the Service = Control Manager:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7022
Date: 12/14/2004
Time: 1:54:04 AM
User: N/A
Computer: HESTER
Description:
The Microsoft Search service hung on starting.
It hangs but has started when I get to the desktop. This started = immediately after I installed the Windows 2000
Component MSMQ. I did not do it with Routing and I lessened = permissions. This on the domain controller. According to this article:
http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;193510
I should have an ODBC System DSN called MQIS pointing to a database in = SQL that was made by the
installation of MSMQ called MQIS. Well I have the DSN but I don't have = the database. It was not made. SQL 2000 SP3. How do I fix this? Is = there some kind of sp which I can run in Query Manager that will in fact = make this database the MSMQ is expecting?
Thanks.
-- George Hester
_________________________________Well that's the end of the Op sys. It's been hosed. Thanks MSMQ.
-- George Hester
_________________________________
"George Hester" <hesterloli@.hotmail.com> wrote in message =news:u#DZi2a4EHA.2452@.TK2MSFTNGP14.phx.gbl...
I believe this is why I am having a error at boot from the Service =Control Manager:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7022
Date: 12/14/2004
Time: 1:54:04 AM
User: N/A
Computer: HESTER
Description:
The Microsoft Search service hung on starting.
It hangs but has started when I get to the desktop. This started =immediately after I installed the Windows 2000
Component MSMQ. I did not do it with Routing and I lessened =permissions. This on the domain controller. According to this article:
http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;193510
I should have an ODBC System DSN called MQIS pointing to a database in =SQL that was made by the
installation of MSMQ called MQIS. Well I have the DSN but I don't have =the database. It was not made. SQL 2000 SP3. How do I fix this? Is =there some kind of sp which I can run in Query Manager that will in fact =make this database the MSMQ is expecting?
Thanks.
-- George Hester
_________________________________sql

MSMQ Connection Manager and input into a data flow

Firstly the disclaimer: im a total SSIS bunny.
Ok, with that out of the way...
What i want to do is have data read from an MSMQ message (which will be a simple XML message) and have it transformed and inserted into a simple table. Sound simple, but i cant work out how to do it.

I started a new Integration Services Project and dropped a Data Flow task on the Control flow tab, then double-click it to go to the data flow tab. I have added a MSMQ connection manager which points at my private queue and i can hit the test button and it sees it tests ok. How do i wire that into my data flow?

On my dataflow tab i have a SQL Server Destination (set to the local SQl server instance) and ive been trying a DataReader source and try setting the Advanced Editor "Connection Manager" column on IDBConnection row to point to my MSMQ connection manager. I get some error "cannot aquire a managed connection from the run-time connection manager". How do i get a Data Flow source which reads the XML message off my MSMQ connection manager?

On the Control Flow tab you can add a Message Queue Task and i can bind it to my MSMQ connection manager and set it up as a recieve task etc, but how do i use that?

Help!

Well, like yourself I am a complete MSMQ bunny but nevertheless....

You are right that the MSMQ Task will be of help here. I don't know much about it but I am guessing that it allows you to save the message to a Variable. Am I correct? If so you can do that and then manipulate the data that is in the variable.

That is as much as I know. Like I say I don't have any experience of using MSMQ with SSIS.

-Jamie

|||Hi, yer, i think i can save the message data to a variable, but im a bit lost on which component ill need to transform that message - the XML one would seem the logical choice but i cant seem to bind it to that variable.
|||

Hi

im new in msmQ TASK

I already configured the msmque task for sending. - > connected to dataflowtask -> msmque task for recieving is this the proper way to implement?

MSMQ Connection Manager and input into a data flow

Firstly the disclaimer: im a total SSIS bunny.
Ok, with that out of the way...
What i want to do is have data read from an MSMQ message (which will be a simple XML message) and have it transformed and inserted into a simple table. Sound simple, but i cant work out how to do it.

I started a new Integration Services Project and dropped a Data Flow task on the Control flow tab, then double-click it to go to the data flow tab. I have added a MSMQ connection manager which points at my private queue and i can hit the test button and it sees it tests ok. How do i wire that into my data flow?

On my dataflow tab i have a SQL Server Destination (set to the local SQl server instance) and ive been trying a DataReader source and try setting the Advanced Editor "Connection Manager" column on IDBConnection row to point to my MSMQ connection manager. I get some error "cannot aquire a managed connection from the run-time connection manager". How do i get a Data Flow source which reads the XML message off my MSMQ connection manager?

On the Control Flow tab you can add a Message Queue Task and i can bind it to my MSMQ connection manager and set it up as a recieve task etc, but how do i use that?

Help!

Well, like yourself I am a complete MSMQ bunny but nevertheless....

You are right that the MSMQ Task will be of help here. I don't know much about it but I am guessing that it allows you to save the message to a Variable. Am I correct? If so you can do that and then manipulate the data that is in the variable.

That is as much as I know. Like I say I don't have any experience of using MSMQ with SSIS.

-Jamie

|||Hi, yer, i think i can save the message data to a variable, but im a bit lost on which component ill need to transform that message - the XML one would seem the logical choice but i cant seem to bind it to that variable.
|||

Hi

im new in msmQ TASK

I already configured the msmque task for sending. - > connected to dataflowtask -> msmque task for recieving is this the proper way to implement?

Saturday, February 25, 2012

MSDTC error

Hi,
I have econnection code in front end app to do the update. I got the
following error,
The transaction manager has disabled its support for remote/network
transaction...
I checked app server the MSDTC has enabled
Any ideas why?
ThanksRead the replies...think youre answer in there.
Just google my friend ;)
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=230390&SiteID=1
First verify the "Distribute Transaction Coordinator" Service is
running on both database server computer and client computers
1. Go to "Administrative Tools > Services"
2. Turn on the "Distribute Transaction Coordinator" Service if it is
not running
If it is running and client application is not on the same computer as
the database server, on the computer running database server
1. Go to "Administrative Tools > Component Services"
2. On the left navigation tree, go to "Component Services > Computers
> My Computer" (you may need to double click and wait as some nodes
need time to expand)
3. Right click on "My Computer", select "Properties"
4. Select "MSDTC" tab
5. Click "Security Configuration"
6. Make sure you check "Network DTC Access", "Allow Remote Client",
"Allow Inbound/Outbound", "Enable TIP" (Some option may not be
necessary, have a try to get your configuration)
7. The service will restart
8. BUT YOU MAY NEED TO REBOOT YOUR SERVER IF IT STILL DOESN'T WORK
(This is the thing drove me crazy before)
On your client computer use the same above procedure to open the
"Security Configuration" setting, make sure you check "Network DTC
Access", "Allow Inbound/Outbound" option, restart service and computer
if necessary.
On you SQL server service manager, click "Service" dropdown, select
"Distribute Transaction Coordinator", it should be also running on
your server computer.
Hope it helps,|||the server is virtual server running window 2000 terminal
"mecn" <mecn2002@.yahoo.com> wrote in message
news:%23myijFJ8HHA.1484@.TK2MSFTNGP06.phx.gbl...
> Hi,
> I have econnection code in front end app to do the update. I got the
> following error,
> The transaction manager has disabled its support for remote/network
> transaction...
> I checked app server the MSDTC has enabled
> Any ideas why?
> Thanks
>

Monday, February 20, 2012

MSDTC - The Transaction Manager is not available

I am trying to do something simple to test TransactionOption. I have a ScriptTask (out of the box), which runs fine. To test TransactionOption, I set the Package Properties TransactionOption = Required. Straight away the package fails with the following message

Error: The SSIS Runtime has failed to start the distributed transaction due to error 0x8004D01B "The Transaction Manager is not available.". The DTC transaction failed to start. This could occur because the MSDTC Service is not running.

I am running this on my Laoptop, which has XP Pro with SP2.

I checked the services and MSDTC and it is running fine. I have checked the Event Viewer and saw the following messages... One is Information and the other is Error

Information (Disk - Event ID 2444)
-
MSDTC started with the following settings:
Security Configuration (OFF = 0 and ON = 1):
Network Administration of Transactions = 0,
Network Clients = 0,
Inbound Distributed Transactions using Native MSDTC Protocol = 1,
Outbound Distributed Transactions using Native MSDTC Protocol = 1,
Transaction Internet Protocol (TIP) = 0,
XA Transactions = 0

Error (Devices - Event ID 4437)
The account that the MS DTC service is running under is invalid. This can happen if the service account information has been changed using the Services snap-in in Microsoft Management Console (MMC). MS DTC service will continue to start. Please make sure that the MS DTC service account information is updated using the Component Services Explorer.

I have checked Component Services. All looks fine from what I can see.

Anyone else came across this?

Thanks

Sutha

Sutha,

Try this: http://blogs.conchango.com/jamiethomson/archive/2005/11/02/2339.aspx

-Jamie

|||

Jamie

Thanks. I have read most of the blogs and tried all options suggested.

I dont have Windows Firewall Turned on. Its always off. I have got Norton on. I have disabled Norton and tried it as well. No luck.

Thanks

Sutha

|||

have you tried the tools that I suggested at the bottom of the blog post?

-Jamie

|||

No Jamie, I didn't try those tools, but I have downloaded them. Before that I uninstalled Norton from my laptop and restarted the machine, all worked fine. So in your case it was Windows Firewall, in my case Norton. What a pain, atleast I have identified the problem.

Thanks Jamie

Sutha

|||

Well that makes sense. Norton has a firewall as well doesn't it?

Have you tried opening up the DTC port (can't remember which one it is) on the firewall rather than just disabling it completely?

-Jamie

|||

Jamie

I disabled the Firewall within Norton and tried still didnt work, but didnt try the port. When I uninstall fully it worked. I think it is 185 ( I could be wrong), will try next week.

Thanks

Sutha