dbTalk Databases Forums  

MMC Error Taken

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts


Discuss MMC Error Taken in the microsoft.public.sqlserver.dts forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Mary
 
Posts: n/a

Default MMC Error Taken - 12-09-2003 , 04:05 PM






Hi All,

I am creating a DTS package to export a table to a text
file. After creating and saving the package, I noticed
that I selected the wrong table as the source. So I
change the source table and go to the Destination tab.
Selecting "Define Columns" and "populate from Source"
clears the list showing the column defs.
Selecting "Define Columns" again causes the error below
followed by being thrown out of Enterprise Manager.

- Any help would be greatly appreciated

---------------------------
mmc.exe - Application Error
---------------------------
The instruction at "0x4173d23a" referenced memory
at "0x020b1e90". The memory could not be "written".



Reply With Quote
  #2  
Old   
Darren Green
 
Posts: n/a

Default Re: MMC Error Taken - 12-09-2003 , 04:29 PM






In article <036501c3bea0$99a1d2f0$a401280a (AT) phx (DOT) gbl>, Mary
<anonymous (AT) discussions (DOT) microsoft.com> writes
Quote:
Hi All,

I am creating a DTS package to export a table to a text
file. After creating and saving the package, I noticed
that I selected the wrong table as the source. So I
change the source table and go to the Destination tab.
Selecting "Define Columns" and "populate from Source"
clears the list showing the column defs.
Selecting "Define Columns" again causes the error below
followed by being thrown out of Enterprise Manager.

- Any help would be greatly appreciated

---------------------------
mmc.exe - Application Error
---------------------------
The instruction at "0x4173d23a" referenced memory
at "0x020b1e90". The memory could not be "written".


I don't recognise the symptoms, but it sounds like a bug. Have you
applied the latest service pack to your (client) machine?
If you have applied SP 3 the it could be a bug in SP3 itself, in which
case apply MS03-031 as well, as this includes a rollup fix for this bug
as well as the security fixes.

http://support.microsoft.com/default...B;EN-US;814113

--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org



Reply With Quote
  #3  
Old   
Mary
 
Posts: n/a

Default Re: MMC Error Taken - 12-10-2003 , 09:53 AM



Instaling the rollup on the client worked!

I had installed the roll up only on the server. The
workstations, which only have the client tools, had Sp3a
installed. I guess it's important to install the rollup
packs on both clients & servers.

Thanks alot for your help.

- Mary

Reply With Quote
  #4  
Old   
Darren Green
 
Posts: n/a

Default Re: MMC Error Taken - 12-10-2003 , 12:57 PM



In article <0bbf01c3bf35$c05bcf00$a401280a (AT) phx (DOT) gbl>, Mary
<anonymous (AT) discussions (DOT) microsoft.com> writes
Quote:
Instaling the rollup on the client worked!

I had installed the roll up only on the server. The
workstations, which only have the client tools, had Sp3a
installed. I guess it's important to install the rollup
packs on both clients & servers.

Thanks alot for your help.

- Mary
Both DTS core objects and the designer are local, you need to patch
clients to get any updates for these. Same with data access components.

--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.