Hello,

I've been getting consistent errors in SQL Server 2000 Developer Edition
after opening DTS packages in Enterprise Manager recently, but I can't find
any descriptions of others with the same problem.

The nature of the problem has changed a little after troubleshooting. In
all cases, the error affects the user interface for DTS package editing.
Originally, I could open a package, edit, and save it without problem. When
I opened a second package though the package window was blank and I would
get an mmc error advising me to terminate the application. Each time I
restated EM I could open and work with one package. The SQL server service
was not affected.

I tried upgrading from SP3a to SP4, but that didn't help. Likewise,
uninstalling that instance (I also have an MSDE instance on the same machine
I didn't uninstall) and reinstalling into the same directories (and
reapplying SP4) didn't help. OS is Windows 2003 server SP2 with all patches
to date.

Under SP4 saving a package reported an error, and I was given a choice to
close the application (EM), ignore the error for he remainder of the
session, or ignore the error permanently. I was able to open and work with
packages repeatedly when choosing to ignore the error for the session, so I
finally decided to ignore the error permanently.


At this point DTS isn't complaining anymore, but MMC still is. It doesn't
matter what package I choose, or who I'm logged in as. Deleting
C:\Documents and Settings\<user name>\Application Data\Microsoft\MMC\SQL
Server Enterprise Manager caused a new file to be created when starting EM,
but that didn't help. The error happen with all packages in both instances,
and they started in both at the same time.

There is no corresponding error in the SQL logs.

The error report (automatically generated) when exiting EM states the error
code is 0xc0000005, which if memory serves is an access violation.

MMC.EXE is version 5.2.3790.2560

The event log contains events like the following:

Event Type: Error
Event Source: Microsoft Management Console
Event Category: None
Event ID: 1000
Date: 4/15/2006
Time: 1:59:18 PM
User: N/A
Computer: RYAN-J-NB3
Description:
The description for Event ID ( 1000 ) in Source ( Microsoft Management
Console ) cannot be found. The local computer may not have the necessary
registry information or message DLL files to display messages from a remote
computer. You may be able to use the /AUXSOURCE= flag to retrieve this
description; see Help and Support for details. The following information is
part of the event: mmc.exe, 5.2.3790.2560, unknown, 0.0.0.0, 02b35b50

Event Type: Error
Event Source: Microsoft Management Console
Event Category: None
Event ID: 1001
Date: 4/15/2006
Time: 1:26:40 PM
User: N/A
Computer: RYAN-J-NB3
Description:
The description for Event ID ( 1001 ) in Source ( Microsoft Management
Console ) cannot be found. The local computer may not have the necessary
registry information or message DLL files to display messages from a remote
computer. You may be able to use the /AUXSOURCE= flag to retrieve this
description; see Help and Support for details. The following information is
part of the event: 280573676.
Data:
0000: 42 75 63 6b 65 74 3a 20 Bucket:
0008: 32 38 30 35 37 33 36 37 28057367
0010: 36 0d 0a 6..

Event Type: Error
Event Source: Microsoft Management Console
Event Category: None
Event ID: 1000
Date: 4/15/2006
Time: 1:21:56 PM
User: N/A
Computer: RYAN-J-NB3
Description:
The description for Event ID ( 1000 ) in Source ( Microsoft Management
Console ) cannot be found. The local computer may not have the necessary
registry information or message DLL files to display messages from a remote
computer. You may be able to use the /AUXSOURCE= flag to retrieve this
description; see Help and Support for details. The following information is
part of the event: mmc.exe, 5.2.3790.2560, dtsui.dll, 2000.80.2039.0,
0005f9a1.



At this point the problem is more of an annoyance than anything else, but
I'd like to fix it if I can.

Thanks for any help,

John Ryan, MCDBA

Hello John,

You may want to follow the steps below to collect a Dr. Watson dump file
for further analysis:

1. Run "drwtsn32" (without the quotation marks) to open the 'Dr. Watson for
Windows' window:
Click start, click Run, type "drwtsn32" in open box.

2. Select the check box next to the Create Crash Dump File option.

3. Search the dump file under the folder indicated by the 'Crash Dump' edit
box. The default directory is "\Documents and Settings\All
Users\Application Data\Microsoft\Dr Watson" (user.dmp).

4. Search the log file under the folder indicated by the 'Log File Path'
edit box. The default directory is "\Documents and Settings\All
Users\Application Data\Microsoft\Dr Watson" (drwtsn32.log).

5. Select the check boxes next to the following options:

Dump All Thread Contexts.
Append to Existing Log File.
Create Crash Dump File.

6. Click OK.

7. Run "drwtsn32 -i" (without the quotation marks) to enable Dr. Watson as
the default debugger.

8. When the error message re-appears, you could find the dr.watson log and
dump files.

To find out the root cause of this issue we may need to analyze memory
dumps, this work has to be done by contacting Microsoft Product Support
Services. Therefore, we probably will not be able to resolve the issue
through the newsgroups. If the issue is urgent, I recommend that you open a
Support incident with Microsoft Product Support Services so that a
dedicated Support Professional can assist with this case. If you need any
help in this regard, please let me know.

For a complete list of Microsoft Product Support Services phone numbers,
please go to the following address on the World Wide Web:
http://support.microsoft.com/directory/overview.asp

To narrow down third party issue, you may troubleshoot the issue with a
selective startup. To do so:

1. Run the System Configuration Utility (msconfig.exe): Click Start->Run,
type "msconfig"(without quotation mark) in the open box, and click OK.

2. On the General tab, select "Selective Startup" and then deselect Load
Startup items, select the checks on other options.

3. On the Services tab, click Hide All Microsoft Services. Deselect all the
items left.

4. Click the Apply button.

5. Reboot your computer to test the situation.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

================================================== ===

This posting is provided "AS IS" with no warranties, and confers no rights.

John,

What ended up being your problem? I'm experiencing similar problems
and was wondering if/how you fixed your issues.

Thanks,

John

Hi John,

One of us is going to have to change our name

I just opened a case with product support this morning. I tried to get Dr
Watson to run per the excellent directions Peter posted (thank you Peter!),
but no luck I'm afraid. There is no log or dmp file generated. I can get a
log by drilling down into the XML file that would normally get transferred
to MS after the error report though. I sent that, plus numerous screen
captures, plus copies of the application and system event logs, plus copies
of the SQL log directory for both instances of SQL. I'm also sending
filemon and regmon captures. I'm tied up later today, but I should be
getting back with Product Support at 9:30 Monday morning.

You might also want to check out
http://www.dbtalk.net/microsoft-publ...ot-164257.html
from 08-22-2005 , 11:02 AM . That is from a posting originally in this
forum, but I don't seem to be able to find it here anymore. That may be a
problem with my Outlook Express though - I've had to unsubscribe and
re-subscribe in the past to restore "missing" posts. Anyway, we both found
filemon reporting a missing C:\Program Files\Common Files\Microsoft
Shared\MSDesigners98\mdt2dfENU.DLL. I checked for the file in image backups
made earlier this year and late last year - both well before the problem
started. No file either place, so I'm guessing the "error" is really just a
search for an optional file.

I'll post the results up here when we figure it out. It's nice to know I
have company. As of this morning I thought I was the only one affected.

Cheers,
John Ryan


"John" <John.Eisbrener (AT) gmail (DOT) com> wrote

I have just encountered this error as well, and I would appreciate any
feedback you might be able to give about your call to PSS.

Still in progress ...
Got transferred to a new group, starting Wednesday 3-May-06.

John Ryan

"ConfusedMCDBA" <ConfusedMCDBA (AT) discussions (DOT) microsoft.com> wrote

I generated a couple of memory dumps over the weekend using WinDBG, and was able to upload them to Microsoft. Got a response back from Product Support this afternoon.

Seem this is a known issue. Workaround is to use DTS Designer on Windows XP or Win2003 non-R2.

I don't remember reading this before installing R2. SQL Server 2000 is on the supported list for R2 (http://www.microsoft.com/windowsserv...pdetails.mspx). The "what's new" page for R2 (http://www.microsoft.com/windowsserv...tsnewinr2.mspx) doesn't mention breaking the DTS designer.

Searching the knowledge base for "Windows 2003 R2 mmc" leads me to KB907265, which describes an update to MMC included in R2. There are a couple of snap-ins known to cause problems (IIS 5 in kb915519, and SQL 2K analysis services in kb915091), but nothing about DTS. Solution is to ignore the problem, but for DTS that means you have to exit MMC after every DTS designer window opening. Not very convienient.

There is a download available for KB 907265, bu it states it is for Windows 2003 SP1. Doesn't say to apply it to Windows 2003 R2. The version of mmc.exe in the download (32 bit X86) is 5.2.3790.2617. My mmc.exe is 5.2.3790.2560, so the download is more recent than what I got in R2. I don't know if it should be applied to R2 though. Even if it is applied, the notes say it isn't needed for mmc 2.0 snap-ins, so it may not help. There is a version compatibility problem with older MMC snap-ins that can be resolved by deleting registry information, but as the snap-in I need is presumably one of the old ones I wonder if that will just render the old snap-ins unusable.

Anyway, I've asked if there is a way to restore components from the pre-R2 upgrade, or at least roll back to pre-R2.

I'll post what I find out.

John Ryan

I am running MMC version 3 on my Windows XP station, which is experiencing
the same issue. I checked, and the version of MMC.exe I am using is
5.2.3790.2612, so I doubt that the patch will do you much good. The errors I
am receiving are slightly different, so I'll list them here in case they are
of any help to anyone:

Event Type: Error
Event Source: Microsoft Management Console
Event Category: None
Event ID: 1000
Date: 5/1/2006
Time: 2:53:46 PM
User: N/A
Computer: <MYComputer>
Description:
The description for Event ID ( 1000 ) in Source ( Microsoft Management
Console ) cannot be found. The local computer may not have the necessary
registry information or message DLL files to display messages from a remote
computer. You may be able to use the /AUXSOURCE= flag to retrieve this
description; see Help and Support for details. The following information is
part of the event: sqlmmc.dll, 2000.80.2039.0, comctl32.dll, 5.82.2900.2180,
000065f8.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 73 71 6c ure sql
0018: 6d 6d 63 2e 64 6c 6c 20 mmc.dll
0020: 32 30 30 30 2e 38 30 2e 2000.80.
0028: 32 30 33 39 2e 30 20 69 2039.0 i
0030: 6e 20 63 6f 6d 63 74 6c n comctl
0038: 33 32 2e 64 6c 6c 20 35 32.dll 5
0040: 2e 38 32 2e 32 39 30 30 .82.2900
0048: 2e 32 31 38 30 20 61 74 .2180 at
0050: 20 6f 66 66 73 65 74 20 offset
0058: 30 30 30 30 36 35 66 38 000065f8
0060: 0d 0a ..

Event Type: Error
Event Source: Microsoft Management Console
Event Category: None
Event ID: 1001
Date: 5/1/2006
Time: 2:53:58 PM
User: N/A
Computer: <MYComputer>
Description:
The description for Event ID ( 1001 ) in Source ( Microsoft Management
Console ) cannot be found. The local computer may not have the necessary
registry information or message DLL files to display messages from a remote
computer. You may be able to use the /AUXSOURCE= flag to retrieve this
description; see Help and Support for details. The following information is
part of the event: 243693452.
Data:
0000: 42 75 63 6b 65 74 3a 20 Bucket:
0008: 32 34 33 36 39 33 34 35 24369345
0010: 32 0d 0a 2..


When I enter DTS the first time, everything is fine, but if I exit DTS and
then go back into it, it gives me the MMC detected an error message. If I
try to ignore, it shuts down anyway, as John described. I would uninstall
MMC 3, but I need it for another application.

Thanks. The event log differences might be due to the difference in the
versions we're running.

At this point it looks like the problem is an incompatibility between MMC
3.0 and several older snap-ins, with DTS being one of them. I got my copy
of MMC 3.0 with Win 2003 R2, which can't be uninstalled. I've been told to
try the MMC 3.0 update (after my next full backup), but I agree it doesn't
seem likely to help. I'm still hoping for either an MMC patch, a DTS
snap-in patch, or a way to force an install of MMC 2.0 as a replacement for
3.0. Either of the first two choices would be preferable of course.

John Ryan


"ConfusedMCDBA" <ConfusedMCDBA (AT) discussions (DOT) microsoft.com> wrote

I installed the MMC 3.0 update from KB907265. No problems, but no help
either. My event log entries look more like yours now though. It's back to
Microsoft.

John Ryan