Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
shishirkhandekar
Starting Member
23 Posts |
 Posted - 2008-07-18 : 16:39:26
|
| Need help running SQLDIAG from machine1 to monitor machine2. Machine 1 is 32bit Windows 2003 and SQL Server 2005Machine2 is 64 bit. Windows 2008 with 64bit SQL Server 2005 installed. I am using all defaults on the commandline (i.e. SQLDIAG.XML and the default output folder). SQLDIAG is registered as a service on machine2.Here's the error:2008/07/18 16:28:46.67 SQLDIAG Command line parameter SQLDIAG 2008/07/18 16:28:46.67 SQLDIAG Command line parameter /P 2008/07/18 16:28:46.67 SQLDIAG Collector version 2005.090.3042.00 2008/07/18 16:28:46.67 SQLDIAG © Microsoft Corp. All rights reserved.IMPORTANT: Please wait until you see "Collection started" before attempting to reproduce your issue 2008/07/18 16:28:46.67 SQLDIAG Output path: C:\SQL Server Utilities\PerfStatsScript1\SQLDIAG\ 2008/07/18 16:28:46.81 SQLDIAG Collecting from 1 logical machine(s) 2008/07/18 16:28:46.86 <machine2>\* Instances registry value not found (you can usually safely ignore this) . Function result: 2. Message: The system cannot find the file specified. 2008/07/18 16:28:46.88 <machine2>\* Error opening Microsoft key . Function result: 2. Message: The system cannot find the file specified. 2008/07/18 16:28:46.88 <machine2>\* No valid instances from which to collect data 2008/07/18 16:28:46.88 <machine2>\* Configuration file is corrupt or missing 2008/07/18 16:28:46.88 <machine2>\* Shutting down the collector |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-07-19 : 00:54:44
|
| How don't just run it locally? |
 |
|
|
|
|
|
SQLDIAG help tracing remote server