Home Dashboard Directory Help
Search

dcexec.exe - Unable to Locate Component by Tommy.Bollhofer


Status: 

Closed
 as Not Reproducible Help for as Not Reproducible


0
0
Sign in
to vote
Type: Bug
ID: 482976
Opened: 8/14/2009 5:33:28 AM
Access Restriction: Public
2
Workaround(s)
view
0
User(s) can reproduce this bug

Description

While configuring the MDW in 2008 R2 the following error is raised. I've reproduced this on a couple of x86 systems.

dcexec.exe - Unable to Locate Component
This application has failed to start because SqlTDiagN.dll was not found. Re-installing the application may fix this problem.
Details
Sign in to post a comment.
Posted by Microsoft on 9/21/2009 at 1:52 PM
Hi,

We have not been able to reproduce this problem in our internal testing and without the additional information requested cannot investigate this further. If you continue encountering this problem feel free to reopen this issue and attach the requested information.

Regards,
Mike Wachal
SQL Server
Posted by Microsoft on 9/16/2009 at 9:59 AM
Hi,

I'm still hoping you can provide the setup logs as requested earlier, we really need this information to analyze the problem you're seeing as we've not been able to reproduce this issue in house.

You can ignore the request to run the PowerShell script, that was meant for a different issue and got mis-entered into this Connect item, sorry.

Regards,
Mike Wachal
SQL Server
Posted by Microsoft on 9/9/2009 at 11:11 AM
Thank you for reporting this issue. We think this problem may be related to an error when retrieving the extended properties from the MDW database but need some additional information to validate this.

Make sure the server that is hosting the MDW database is in the same state underwhich you encounter the error (i.e. the second database is disconnected from the mirror) and run the following script agasint that server:

#############
#### Script Start
# Open powershell.exe and paste following commands
# for a different instance name replace "(local)" with "server\instance"

[reflection.assembly]::LoadWithPartialName("Microsoft.SqlServer.Smo")
$sqlServer = new-object ("Microsoft.SqlServer.Management.Smo.Server") "(local)"
#list of databases and Db status
foreach($db in $sqlServer.Databases) { $db.Name, $db.IsSystemObject, $db.Status}

#list of databases, compat level, extended property list
foreach($db in $sqlServer.Databases) { $db.Name, $db.IsSystemObject, $db.CompatibilityLevel,$db.ExtendedProperties}
#### Script End
#############

This script attempts to return two sets of database properties. If the problem is with the extended properies the first call should return fine, but the second call should fail.

Thank you for your help,
Mike Wachal
SQL Server
Posted by Microsoft on 9/9/2009 at 9:38 AM
Thank you for reporting this issue, some additional information will help us investigate this problem. Please collect the instal logs from one of the computers where you are experiencing the problem and attach them to this report. You can find the instal logs at C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log in a folder named for the date/time when you did your installation. There may already be a CAB archive available that you can send. If there is no CAB, please send us the summary log and the details log.

Also, could you please examine your install location to see if the SqlTDiagN.DLL is there? You should find it at C:\Program Files\Microsoft SQL Server\100\DTS\Binn.

Regards,
Mike Wachal
SQL Server
Posted by Microsoft on 9/9/2009 at 9:21 AM
Thank you for reporting this issue, some additional information will help us investigate this problem. Please collect the instal logs from one of the computers where you are experiencing the problem and attach them to this report. You can find the instal logs at C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log in a folder named for the date/time when you did your installation. There may already be a CAB archive available that you can send. If there is no CAB, please send us the summary log and the details log.

Also, could you please examine your install location to see if the SqlTDiagN.DLL is there? You should find it at C:\Program Files\Microsoft SQL Server\100\DTS\Binn.

Regards,
Mike Wachal
SQL Server
Sign in to post a workaround.
Posted by Levi Justus on 9/24/2010 at 3:07 PM
I hope you got the "file not found" error while trying to run the dcexec command from the command line. Because either query window or the the SQL Job would not report this error.

Basically your Path variable is tampered.
Add the path where SQLTDiagN.dll exist (C:\Program Files\Microsoft SQL Server\100\DTS\Binn) to your existing path variable. Reboot the machine.
Path variable can be tampered by third party applications. The issue does not repro on a fresh install of SQL Server
I have a repro, please let me know if you need additional information
Posted by Mat_t1 on 8/28/2009 at 10:56 PM
I encountered same error after setting up MDW on SS08 SP1. a possible workaround..

1) disabled MDW through SSMS
2) deleted MDW database
3) rebooted
4) re-enabled MDW and reconfigured it, created new database etc.

After that all 3 of my data collect sets are working, no errors like last time. I can RC them and run a collect now and upload which returns successful. Reports are working.