Showing posts with label compatibility. Show all posts
Showing posts with label compatibility. Show all posts

Sunday, February 26, 2012

DTS - ActiveXScripting Not Working on 64bit AMD Cluster on SQL Server 2005 SP2

I have a problem with DTS - ActiveXScripting that it cannot initialize the script engine, I have the backward compatibility stuff installed, even tried a repair but still does not work.

Many thanks for any help you can provide on this problem.

Paul

Error Information below:

Date 17/04/2007 13:07:32
Log Job History (Test ActiveX Script)

Step ID 1
Server GBCONV1A002V03
Job Name Test ActiveX Script
Step Name Step 1: Exec TestActiveX script
Duration 00:00:01
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0

Message
Executed as user: WW004\ConSrvSQLAgentA002. ...TSStep_DTSActiveScriptTask_1 DTSRun OnError: DTSStep_DTSActiveScriptTask_1, Error = -2147220487 (800403F9) Error string: ActiveX Scripting was not able to initialize the script execution engine. Error source: Microsoft Data Transformation Services (DTS) Package Help file: sqldts80.hlp Help context: 4500 Error Detail Records: Error: -2147220487 (800403F9); Provider Error: 0 (0) Error string: ActiveX Scripting was not able to initialize the script execution engine. Error source: Microsoft Data Transformation Services (DTS) Package Help file: sqldts80.hlp Help context: 4500 DTSRun OnFinish: DTSStep_DTSActiveScriptTask_1 Error: -2147220440 (80040428); Provider Error: 0 (0) Error string: Package failed because Step 'DTSStep_DTSActiveScriptTask_1' failed. Error source: Microsoft Data Transformation Services (DTS) Package Help file: ... Process Exit Code 1. The step failed.

Try asking in the DTS usenet group.

http://groups.google.com/group/microsoft.public.sqlserver.dts?lnk=srg

Friday, February 17, 2012

DTA Compatibility

Runing the next query using DTA:

selectLTrim(RTrim(CodCtaCte))as CodCtaCte, Nombre from CtaCtes where CuePrefi ='C'orderby Nombre

with SQL Server 2000 SP4 instance, I got this error:

"Tuning process exit unexpectedly"

Now, the same DTA and query but using SQL Server 2005 SP2 instances, works fine.

Both insances are in the same Server with Windows 2003.

Any clue?

Moving to the SQL Server forums from Katmai. The Katmai forums are for SQL Server 2008.

Thanks,
Phil|||May be my lack of English is the reason for this move.

In my original post I was talking about Katmai or SQL Server 2008.

Thanks,

Luis

DTA Compatibility

Phil move this post to SQL 2005 forum.

I suppose my lack of English was the reason, so I post it again.

I'm working with DTA Katmai SQL Server 2008.

Runing the next query using DTA:

selectLTrim(RTrim(CodCtaCte))as CodCtaCte, Nombre from CtaCtes where CuePrefi ='C'orderby Nombre

with SQL Server 2000 SP4 instance, I got this error:

"Tuning process exit unexpectedly"

Now, the same DTA and query but using SQL Server 2005 SP2 instances, works fine.

Both insances are in the same Server with Windows 2003.

Any clue?

Luis

I guess there was bug within SQL 2005 too working with DTA as that was found to be a bug in DTA in dealing with indexed views, in your case I woudln't take a guess that you are using Indexed views or any of them are involved or not.

|||Satya (old friend),

I never had a problem with DTA 2005 and SQL 2000.
If fact, DTA 2005 provide better indexes than ITW.
May be is a Katmai bug.|||So, I have to understand Katmai will not support sql 2000. I'm right?|||

From your posting it seems that DTA Katmai against Shiloh fails while DTA Katmai against Yukon works.Is this correct?

Potentially this is hitting a bug when DTA tries to analyze the showplan_parsing output for a query . This is not a problem in SQL Server 2005 since we use the more robust showplan_xml interface.

Can you check if there are any dtaengine mini dumps in the ErrorDumps Folder ? (typically the path is C:\Program Files\Microsoft SQL Server\100\Shared\ErrorDumps) .If so we can take a look at the minidumps

Please let me know

Manoj

|||Your first question is correct.

Also there is no problem with DTA 2008 and SQL 2005.

There is nothing in ErrorDumps.

Thanks.|||

Hi Luis

Given that there are no user mode dumps the best way to proceed would be to file the problem as a bug using the connect program. It will be easier to debug if you have a representative database and workload.

Let us know if you have any questions on how to proceed

Manoj

DTA Compatibility

Phil move this post to SQL 2005 forum.

I suppose my lack of English was the reason, so I post it again.

I'm working with DTA Katmai SQL Server 2008.

Runing the next query using DTA:

select LTrim(RTrim(CodCtaCte)) as CodCtaCte, Nombre from CtaCtes where CuePrefi = 'C' order by Nombre

with SQL Server 2000 SP4 instance, I got this error:

"Tuning process exit unexpectedly"

Now, the same DTA and query but using SQL Server 2005 SP2 instances, works fine.

Both insances are in the same Server with Windows 2003.

Any clue?

Luis

I guess there was bug within SQL 2005 too working with DTA as that was found to be a bug in DTA in dealing with indexed views, in your case I woudln't take a guess that you are using Indexed views or any of them are involved or not.

|||Satya (old friend),

I never had a problem with DTA 2005 and SQL 2000.
If fact, DTA 2005 provide better indexes than ITW.
May be is a Katmai bug.|||So, I have to understand Katmai will not support sql 2000. I'm right?|||

From your posting it seems that DTA Katmai against Shiloh fails while DTA Katmai against Yukon works.Is this correct?

Potentially this is hitting a bug when DTA tries to analyze the showplan_parsing output for a query . This is not a problem in SQL Server 2005 since we use the more robust showplan_xml interface.

Can you check if there are any dtaengine mini dumps in the ErrorDumps Folder ? (typically the path is C:\Program Files\Microsoft SQL Server\100\Shared\ErrorDumps) .If so we can take a look at the minidumps

Please let me know

Manoj

|||Your first question is correct.

Also there is no problem with DTA 2008 and SQL 2005.

There is nothing in ErrorDumps.

Thanks.|||

Hi Luis

Given that there are no user mode dumps the best way to proceed would be to file the problem as a bug using the connect program. It will be easier to debug if you have a representative database and workload.

Let us know if you have any questions on how to proceed

Manoj

DTA Compatibility

Phil move this post to SQL 2005 forum.

I suppose my lack of English was the reason, so I post it again.

I'm working with DTA Katmai SQL Server 2008.

Runing the next query using DTA:

select LTrim(RTrim(CodCtaCte)) as CodCtaCte, Nombre from CtaCtes where CuePrefi = 'C' order by Nombre

with SQL Server 2000 SP4 instance, I got this error:

"Tuning process exit unexpectedly"

Now, the same DTA and query but using SQL Server 2005 SP2 instances, works fine.

Both insances are in the same Server with Windows 2003.

Any clue?

Luis

I guess there was bug within SQL 2005 too working with DTA as that was found to be a bug in DTA in dealing with indexed views, in your case I woudln't take a guess that you are using Indexed views or any of them are involved or not.

|||Satya (old friend),

I never had a problem with DTA 2005 and SQL 2000.
If fact, DTA 2005 provide better indexes than ITW.
May be is a Katmai bug.|||So, I have to understand Katmai will not support sql 2000. I'm right?|||

From your posting it seems that DTA Katmai against Shiloh fails while DTA Katmai against Yukon works.Is this correct?

Potentially this is hitting a bug when DTA tries to analyze the showplan_parsing output for a query . This is not a problem in SQL Server 2005 since we use the more robust showplan_xml interface.

Can you check if there are any dtaengine mini dumps in the ErrorDumps Folder ? (typically the path is C:\Program Files\Microsoft SQL Server\100\Shared\ErrorDumps) .If so we can take a look at the minidumps

Please let me know

Manoj

|||Your first question is correct.

Also there is no problem with DTA 2008 and SQL 2005.

There is nothing in ErrorDumps.

Thanks.|||

Hi Luis

Given that there are no user mode dumps the best way to proceed would be to file the problem as a bug using the connect program. It will be easier to debug if you have a representative database and workload.

Let us know if you have any questions on how to proceed

Manoj