DTS designer error

When I open my DTS package at my PC ( Client ) .There is an error message show like below .
DTR Designer Error.
There was a problem retriving the list of OLE DB providers.
No. Provider is selected .TO continue,you must select a valid provider.
Please helpHowdy

Delete the server registration in EM and re-register the server.

Post back if problems.

Cheers

SG.|||What is the level of service pack of SQL on the client machine?
Ensure to maintain similar service pack on Server and on client as well.|||Originally posted by sqlguy7777
Howdy

Delete the server registration in EM and re-register the server.

Post back if problems.

Cheers

SG.

I have already done as your mention but it still show the same error message

Any idea ??|||Originally posted by Satya
What is the level of service pack of SQL on the client machine?
Ensure to maintain similar service pack on Server and on client as well.

How can I check the service pack verion of both server and client ? Please introduce me

Thanks|||SELECT serverproperty('ProductLevel')

Regards!!|||select @.@.version;

This will give you the details of OS level as well as SQL Server level.|||This causes due to .DLL mismatch or even MDAC version between client and server machines, so ensure you have all the similar levels.

This @.@.Version or Serverproperty will give you version on server for SQL Server and on client machine ensure to run service pack for SQL again which might resolve the issue.

DTS - Write Exceptions to table?

Can DTS write exceptions to a database table? In the code
below, I copy fname, lname and (at the end) company from
the source to the destination. However, with title, if the
title is executive or president, the title is copied over;
if the title is ceo it is entered into the destination
table as ceo/chairman; if none of these conditions apply
(i.e. title is owner) I want the entire row written to a
new table.

If I use Main = DTSTransformStat_SkipRow, rows that meet
the title criteria are entered into the destination table,
and the rows that don't meet the criteria are not entered.
I can get DTS to output the exeption file to a text file,
however, with the large number of records that don't meet
the criteria, it would be better to have them in a new
table.

Thanks,

Jay

----------

Function Main()
DTSDestination("fname") = DTSSource("fname")
DTSDestination("lname") = DTSSource("lname")

'Check Titles
If lcase(DTSSource("title")) = "executive" then
DTSDestination("title") = DTSSource("title")
ElseIf lcase(DTSSource("title")) = "president" then
DTSDestination("title") = DTSSource("title")
ElseIf lcase(DTSSource("title")) = "ceo" then
DTSDestination("title") = "CEO/Chairman"
Else
Main = DTSTransformStat_ExceptionRow
'Main = DTSTransformStat_SkipRow
Exit Function
End if



DTSDestination("company") = DTSSource("company")
Main = DTSTransformStat_OK
End FunctionYou can break your task in 2 phases:

First Transformation Task:
Insert / Update all rows that meet the criteria

Second Transformation Task:
Insert rows that does not meet the criteria in a anther table

Remeber the you can have more than one transformatrion task between two connections|||Thanks - I will give that a try.

dtexec?

i am using dtexec in command prompt

it always prompt the path is not valid and error is 0x80070057

below is what i input

dtexec /dts c:\ssis\***\***.dtsx

what's wrong? thanks

dtexec /f "C:\ssis\**.dtsx" can working

so sorry

|||

try this, it should generate a log for you so you can view detailed errors:

dtexec /f "C:\SSIS\YourPackage.dtsx">>C:\SSIS\YourPackage.LOG

DSO.Dimension.DataSource fails in jscript

I have a jscript that I am using to create 2 new dimensions (see below). The problem that I am encountering is "object doesn't support this action". This occurs for the following line: inventoryProductDimension.DataSource = dsoDataSource;

First is this because of jscript and secondly is there anyway around this.

Thanks

Ron

Code Snippet

var serverName = config.GetOlapServerName();

var databaseName = config.GetOlapDataBaseName();

var server = new ActiveXObject("DSO.Server");

if (server == null) throw "Could not create DSO.Server object.";

// Connect to OLAP server specified in web.config file

server.Connect(serverName);

var database = new ActiveXObject("DSO.Database");

if (database == null) throw "Could not create DSO.Database object.";

// Retrieve database object from server

database = server.MDStores(databaseName);

// Create new Dimension

var inventoryProductDimension;

//if (inventoryProductDimension == null) throw "Could not create DSO.Dimension for InventoryProduct dimension.";

// Get database's datasource

var dsoDataSource ;

dsoDataSource = database.DataSources("DataMart");

inventoryProductDimension = database.Dimensions.AddNew("InventoryProduct");

// Add inventoryproduct dimension

inventoryProductDimension.DataSource = dsoDataSource;

inventoryProductDimension.FromClause ="\"dbo\".\"InventoryProductCategory\",\"dbo\".\"InventoryProduct\"";

inventoryProductDimension.JoinClause ="(\"dbo\".\"InventoryProductCategory\".\"SurrogateKey\" = \"dbo\".\"InventoryProduct\".\"FK_InventoryProductCategory\")";

// Add InventoryProduct Levels

update: Through research, I have determined that it is not recommended that you use a scripting language to perform DSO functions because the object hierarchy is based on the MDStores interface such that if you wanted to iterate through the collection of databases on server, then you would need to iterate through MDStores rather databases. This works because each MDStore for the Server object is a database object. Bottom-line is that the language must be capable of create object types and this is not case with JScript. In my case, I opted to try another scripting language,VBScript. This seems to function properly; however the collections created using CreateObject may not be available in future versions of DSO.

Thanks

Ron Cotton

DSO.Dimension.DataSource fails in jscript

I have a jscript that I am using to create 2 new dimensions (see below). The problem that I am encountering is "object doesn't support this action". This occurs for the following line: inventoryProductDimension.DataSource = dsoDataSource;

First is this because of jscript and secondly is there anyway around this.

Thanks

Ron

Code Snippet

var serverName = config.GetOlapServerName();

var databaseName = config.GetOlapDataBaseName();

var server = new ActiveXObject("DSO.Server");

if (server == null) throw "Could not create DSO.Server object.";

// Connect to OLAP server specified in web.config file

server.Connect(serverName);

var database = new ActiveXObject("DSO.Database");

if (database == null) throw "Could not create DSO.Database object.";

// Retrieve database object from server

database = server.MDStores(databaseName);

// Create new Dimension

var inventoryProductDimension;

//if (inventoryProductDimension == null) throw "Could not create DSO.Dimension for InventoryProduct dimension.";

// Get database's datasource

var dsoDataSource ;

dsoDataSource = database.DataSources("DataMart");

inventoryProductDimension = database.Dimensions.AddNew("InventoryProduct");

// Add inventoryproduct dimension

inventoryProductDimension.DataSource = dsoDataSource;

inventoryProductDimension.FromClause ="\"dbo\".\"InventoryProductCategory\",\"dbo\".\"InventoryProduct\"";

inventoryProductDimension.JoinClause ="(\"dbo\".\"InventoryProductCategory\".\"SurrogateKey\" = \"dbo\".\"InventoryProduct\".\"FK_InventoryProductCategory\")";

// Add InventoryProduct Levels

update: Through research, I have determined that it is not recommended that you use a scripting language to perform DSO functions because the object hierarchy is based on the MDStores interface such that if you wanted to iterate through the collection of databases on server, then you would need to iterate through MDStores rather databases. This works because each MDStore for the Server object is a database object. Bottom-line is that the language must be capable of create object types and this is not case with JScript. In my case, I opted to try another scripting language,VBScript. This seems to function properly; however the collections created using CreateObject may not be available in future versions of DSO.

Thanks

Ron Cotton