error: 'Dts' does not exist in the namespace 'Microsoft.Sqlserver'

I tried to create a package from a C# program, and I copied this from SQL server online book:

using Microsoft.Sqlserver.Dts.Runtime;

But I got compilation error:
The type or namespace name 'Dts' does not exist in the namespace 'Microsoft.Sqlserver'(are you missing an asssembly reference?)
What am I missing?

Thanks a lot

Have you, in fact, set a reference to Microsoft.SqlServer.ManagedDTS ? This is the assembly that contains the Dts.Runtime namespace.

-Doug
|||How do I set a reference to ManagedDTS? by writting:
using Microsoft.SqlServer.ManagedDTS
?

In this case ManagedDTS can not be found by compiler

Thanks for the hint
|||Please consult the Books Online for support. For example, the following article mentions what DLLs need to be registered:

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/dtsref9/html/e44bcc70-32d3-43e8-a84b-29aef819d5d3.htm
regards,
ash|||found the solution: from visual studio, click Project->Add reference, then browse the assembly ManagedDTS.dll at directory c:\program files\microsoft sql server\90\SDK\Assemblies, this willl add ManagedDTS.dll to the project and solve the problem.

Thanks everyone!|||

Hello,

if you get this problem on your server. build your site in release mode and then you have this dll in your bin\release folder.

Either find this DLL and upload that in your server bin directory manually

error: 'Dts' does not exist in the namespace 'Microsoft.Sqlserver'

I tried to create a package from a C# program, and I copied this from SQL server online book:

using Microsoft.Sqlserver.Dts.Runtime;

But I got compilation error:
The type or namespace name 'Dts' does not exist in the namespace 'Microsoft.Sqlserver'(are you missing an asssembly reference?)
What am I missing?

Thanks a lotHave you, in fact, set a reference to Microsoft.SqlServer.ManagedDTS ? This is the assembly that contains the Dts.Runtime namespace.

-Doug|||How do I set a reference to ManagedDTS? by writting:
using Microsoft.SqlServer.ManagedDTS
?

In this case ManagedDTS can not be found by compiler

Thanks for the hint|||Please consult the Books Online for support. For example, the following article mentions what DLLs need to be registered:

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/dtsref9/html/e44bcc70-32d3-43e8-a84b-29aef819d5d3.htm
regards,
ash|||found the solution: from visual studio, click Project->Add reference, then browse the assembly ManagedDTS.dll at directory c:\program files\microsoft sql server\90\SDK\Assemblies, this willl add ManagedDTS.dll to the project and solve the problem.

Thanks everyone!|||

Hello,

if you get this problem on your server. build your site in release mode and then you have this dll in your bin\release folder.

Either find this DLL and upload that in your server bin directory manually

Error: Could not get a list of SSIS packages from the project.

Hello,

I have a SSIS package and I am trying to build it using devenv.com from command line. It gives me this error:

Error: Could not get a list of SSIS packages from the project.

However if I open the project in Visual Studio it builds properly. In project property I have set CreateDeploymentUtility=true.

This is what I do from command line:

devenv.com MySSIS.sln /Build "Development|Default"

Any idea what I should do ?

Thanks

Deval

Hello,

There is no solution to it as far as I know if we set CreateDeploymentUtility=true. If you uncheck it then it will work fine.

Thanks

Deval

Error: -2147024770 when i scheduled a package containing a custom task

I create a VB ActiveX DLL custom task, when i execute the package containing the DLL custom task, all is ok
But when i scheduled the package i receive the message "Error: -2147024770 The specified module could not be found"
In the code of the VB custom task i use the sysdtssteplog table from MSDB and it doesn't log anything
What's the problem
Thanks!Whenever I seen that error from VB - SQL it has always
been in the context that the SQL command run from VB has
not worked.
Try a trace to see exactly what SQL was processed.
J
>--Original Message--
>I create a VB ActiveX DLL custom task, when i execute the
package containing the DLL custom task, all is ok.
>But when i scheduled the package i receive the
message "Error: -2147024770 The specified module could
not be found".
>In the code of the VB custom task i use the sysdtssteplog
table from MSDB and it doesn't log anything.
>What's the problem?
>Thanks!
>.
>|||Jay,
When you run it, what context (login, machine, etc) are you running under?
When you schedule it (I assume through SQL Agent), what context (login,
machine, etc) are you running under?
I suspect that the SQL Server account (either the account running the SQL
Server service or the SQL Agent proxy account) does not have rights to the
location where the DLL is stored. Make sure that the DLL can be reached by
the SQL Server.
Russell Fields
"JayF" <anonymous@.discussions.microsoft.com> wrote in message
news:025B1AE0-EDC9-482C-B93E-788775D19D24@.microsoft.com...
> I create a VB ActiveX DLL custom task, when i execute the package
containing the DLL custom task, all is ok.
> But when i scheduled the package i receive the message
Error: -2147024770 The specified module could not be found".
> In the code of the VB custom task i use the sysdtssteplog table from MSDB
and it doesn't log anything.
> What's the problem?
> Thanks!

Error: -2147024770 when i scheduled a package containing a custom task

I create a VB ActiveX DLL custom task, when i execute the package containing
the DLL custom task, all is ok.
But when i scheduled the package i receive the message "Error: -2147024770
The specified module could not be found".
In the code of the VB custom task i use the sysdtssteplog table from MSDB an
d it doesn't log anything.
What's the problem?
Thanks!Jay,
When you run it, what context (login, machine, etc) are you running under?
When you schedule it (I assume through SQL Agent), what context (login,
machine, etc) are you running under?
I suspect that the SQL Server account (either the account running the SQL
Server service or the SQL Agent proxy account) does not have rights to the
location where the DLL is stored. Make sure that the DLL can be reached by
the SQL Server.
Russell Fields
"JayF" <anonymous@.discussions.microsoft.com> wrote in message
news:025B1AE0-EDC9-482C-B93E-788775D19D24@.microsoft.com...

quote:

---

> I create a VB ActiveX DLL custom task, when i execute the package

---

containing the DLL custom task, all is ok.

quote:

---

> But when i scheduled the package i receive the message

---

Error: -2147024770 The specified module could not be found".

quote:

---

> In the code of the VB custom task i use the sysdtssteplog table from MSDB

---

and it doesn't log anything.

quote:

---

> What's the problem?
> Thanks!

---

sql

Error Working With DTS -- "Class Not Registered"

I have a DTS package (stored in a .dts file) that was created in SQL Server 2000 and I am trying to work with it in SQL 2005. When I try to import it into the Legacy > Data Transformation Services node in Management Studio, I get a window that reads "Class Not Registered (Microsoft Data Transformation Services (DTS) Package)". I get the same error if I try to just execute the package itself from a query window.

I have Legacy Support installed, and I also have Integration Services installed.

Any ideas? We have three installations of SQL 2005 and I am getting the same error on all of them.

Have you installed Microsoft SQL Server 2000 DTS Designer Components from here:

http://www.microsoft.com/downloads/details.aspx?FamilyID=df0ba5aa-b4bd-4705-aa0a-b477ba72a9cb&displaylang=en

The DTS designer does not get installed with SSIS.

Thanks.

Error with schedule a DTS package...

Hi experts...

I'm trying to schedule a DTS package (import some tables from Mysql database) but there is
an error and I don't know how to resolve it.

The error is always the same...
"The job failed. The Job was invoked by Schedule 24 (Import RT data). The last step to run was step 1 (Import RT data)."

I have tried changing the all the parameters in the job properties, but I always obtein the same message.

The DTS package works fine, I can execute and it works, the problem is the schedule...

Thanks in advanced...What account is the scheduled task running under? Normally if you run it yourself and it works, you are running the DTS package with YOUR permissions. However, if you run the DTS package under a schedule, it is using the standard SQL Server account (which is either Local System or another specified account). You need to change the account the schedule runs under to have enough permissions to run properly.|||Thanks for your reply...

I have one more question... How can i change the account of the schedule task?... I don't know how can I change it.

The strange thing is that I've done the same with another databases, only one thing is different, the source, the schedules that work fine are between SQL databases and this is from Mysql to sql database... but this is not the problem becouse as I said I can execute it and it works fine.

thanks again.|||If you schedule a job in SQL Server, then on the Job Properties dialog window, click the Steps tab. Highlight the step (here, executing the DTS package job) that you want, and click Edit or properties. In the Job Step properties dialog window, click the Advanced tab, and there is a Run as user dropdownlist. Try changing that to your credentials.|||Hi Again,

There is a problem with this solution... the step type is CmdExec and you can't see this option unless you choose SQL Script type... I don't understand what's happening, I have read the documentation about Package Scheduling and Security Issues but I don't know how to change who invoked the job...

thanks again...|||That's an operating-system command or executable program command step. I'm not familiar with that. Is there any way to change the security context in the DTS package designer?|||Hi again...

The step is an operating system command... but as I said this job is similar to other... the only I can see related to the security context is the owner, and it's the same in all jobs that I have done (and they work fine).

thanks for your interest.|||Aha, I found this from databasejournal.com (link

You can also schedule execution of DTS packages using SQL Server Agent jobs. This ability is granted by default to the public group, based on permissions to execute sp_add_job and sp_add_jobschedule stored procedures in the MSDB database (this applies to all SQL Server Agent jobs, not just the ones that invoke DTS packages). Typically, it is recommended to restrict access to them to a limited number of privileged logins. While jobs typically execute in the security contexts of their owner, in the case of DTS packages this might be different. The reason is the fact that a task that contains invocation of a DTS package accomplishes this by the running DTSRun command line utility, which involves, in turn, the use of CmdExec. If you limit permissions to launch CmdExec jobs to members of the SysAdmin fixed server role (which is the default behavior), jobs will still execute in the same security context as their owners. However, you can change this default in the SQL Server Agent Properties dialog box, accessible by selecting the Properties option from the SQL Server Agent node under the Management folder in the SQL Server Enterprise Manager console. In the Job System tab, you need to clear the checkbox next to the "Only users with SysAdmin privileges can execute CmdExec and ActiveScripting job steps" and provide a Proxy Account name and password. The proxy account provides the security context for execution of DTS packages, so ensure that it has access to all relevant data stores, file system paths or COM components, which might be used by ActiveX scripting tasks. Remember, however, that at the same time you allow users without SysAdmin privileges to run potentially dangerous ActiveScripting jobs.|||Thanks a lot, but I haven't resolved the problem, I have seen this choice, and I put an administration user, but It didn't work... I don't know...

Sorry about your lost time.|||An administrative user for the box, or an administrative user on the domain? Domain permissions could be the problem.

You could also try posting to the Microsoft newsgroups, specifically the sqlserver.dts one:

http://communities.microsoft.com/newsgroups/default.asp

Then look for sqlserver.dts in the left frame after it downloads (it takes a while).

error with Execute package task

Hi,

We have used an execute package task in our master package to execute a child package and we have set the execute out of process=false. This master package is running fine in 32 bit server but is failing in 64 bit server. is there any settings to be done in the server or is it the problem with the property setting(execute out of process)

Vivek S

sorry for posting in SSRS category. Has been reposted in SSIS

Error while using a slowly changing dimension transformation

I have a SSIS package which contains a number of slowly changing dimension transformations. While the majority work I have one which gives me the following error 'Error: The variable "System::LocaleID" is already on the read list. A variable may only be added once to either the read lock list or the write lock list. '. This error only occurs if the destination table holds data. If I truncate the table and reload the data then the package complete successful. The only difference I can see between this dimension transformation and the other dimension transforms is that the one in question has 2 business keys while the rest have 1.

Can anyone shed light on this?

Thanks

Have you installed SP1 and the hot fixes or SP2?

There was a bug in the variable handling which caused this error.
Although, the bug was not specifically for the SCD but variables in script task and derived columns and variables in general (so it would seem)|||

Yeah I've got SP2 installed.

Does this bug have a negative effect on the execution of the package? Has far has I can tell the package is completing. What is further confusing is if I empty the target dimension table I dont get the error. It only occurs on subsequent runs of the package when theres data present.

Error while using a slowly changing dimension transformation

I have a SSIS package which contains a number of slowly changing dimension transformations. While the majority work I have one which gives me the following error 'Error: The variable "System::LocaleID" is already on the read list. A variable may only be added once to either the read lock list or the write lock list. '. This error only occurs if the destination table holds data. If I truncate the table and reload the data then the package complete successful. The only difference I can see between this dimension transformation and the other dimension transforms is that the one in question has 2 business keys while the rest have 1.

Can anyone shed light on this?

Thanks

Have you installed SP1 and the hot fixes or SP2?

There was a bug in the variable handling which caused this error.
Although, the bug was not specifically for the SCD but variables in script task and derived columns and variables in general (so it would seem)|||

Yeah I've got SP2 installed.

Does this bug have a negative effect on the execution of the package? Has far has I can tell the package is completing. What is further confusing is if I empty the target dimension table I dont get the error. It only occurs on subsequent runs of the package when theres data present.

Error while trying to deploy SSIS Package

Hi,
I am trying to deploy a DTSX package to 32-bit SQL Server 2005 in a 64-bit machine from my installer.
I am getting the following error in the SaveToSQLServer method:
The SaveToSQLServer method has encountered OLE DB Error code 0x80004005 (Communication Link Failure). The SQL statement that was issued has failed.
However I am not facing this problem when I try to deploy the DTSX package to a 32-bit SQL Server 2005 in a 32-bit machine.
Can anyone tell me why this happens and how this could be solved?
Thanks,
Sandhya

It sounds like you're doing this through BIDS now, which is fine but as a debug step will Management Studio even let you import the package in? That will prove you have connectivity to the SSIS service. You'll need port 135 open to the server to your box if you haven't already done so. Another tactic is to create a deployment utility and deploy the entire project. You may already know that one but just in case, here's a video to walk you through that series of steps: http://www.jumpstarttv.com/Media.aspx?vid=28.

Brian

|||

Hi,

I tried importing the packages. I was able to do that successfully. Still when I tried to install, the packages were not gettign deployed. So I reinstalled SQL server 2005 and tried. It worked. But when I try installing my solution repeatedly, the same error occurs. Why does this happen?

Error while trying to deploy SSIS Package

Hi,
I am trying to deploy a DTSX package to 32-bit SQL Server 2005 in a 64-bit machine from my installer.
I am getting the following error in the SaveToSQLServer method:
The SaveToSQLServer method has encountered OLE DB Error code 0x80004005 (Communication Link Failure). The SQL statement that was issued has failed.
However I am not facing this problem when I try to deploy the DTSX package to a 32-bit SQL Server 2005 in a 32-bit machine.
Can anyone tell me why this happens and how this could be solved?
Thanks,
Sandhya

It sounds like you're doing this through BIDS now, which is fine but as a debug step will Management Studio even let you import the package in? That will prove you have connectivity to the SSIS service. You'll need port 135 open to the server to your box if you haven't already done so. Another tactic is to create a deployment utility and deploy the entire project. You may already know that one but just in case, here's a video to walk you through that series of steps: http://www.jumpstarttv.com/Media.aspx?vid=28.

Brian

|||

Hi,

I tried importing the packages. I was able to do that successfully. Still when I tried to install, the packages were not gettign deployed. So I reinstalled SQL server 2005 and tried. It worked. But when I try installing my solution repeatedly, the same error occurs. Why does this happen?

Error While Scheduling the SSIS Package

Hello Everyone,
When i try to scedule a job on SQL Server Management Studio it gives the Following Error:

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectkey'.(Micorsoft.SqlServer.Smo)

Can anyone tell me why ?

MS SQL Server Details:

Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86) Oct 14 2005 00:33:37 Copyright (c) 1988-2005 Microsoft Corporation Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2)

Hi,

Do you have this file?

C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies\Microsoft.SqlServer.Smo.dll

Regards,

Janos

|||Yes, File is there on the specified path.

|||

Well, I got the same error one time, as far as I remember, I repaired my installation of SQL Server client tool.

Try to repair it please.

regards,

Janos

|||thanks janos,

i have a local server installed on my workstation along with sp2.
Do you really think reinstalling the server will work ?
|||

Well, It worked for me

Maybe you just repair your installation will be enough.

Regards,

Janos

|||Is there any option for repairing the server ?
Coz i haven't seen any while installing.
|||Did you manage to find a solution for this problem? I get the same error when trying to create an Agent job. I've repaired the SQL Native Client but to no avail. I still get the error.
|||No, not yet !!! I am still working on it.
One of the forum member advised me to repair the server but for you if it did not work, then i am doubtful.
|||You can repair the application from "Programs and Features" (Vista) or "Add/Remove Programs" (XP) in control panel|||

Hi Vick,

I just realized something. I saw the error message contains the SQL build w/o service pack, but you wrote you have SP2 installed (but maybe just for database services and SSMS or just SSIS). Have you tried to install the SP2 to the SSIS or those, where not installed?

Regards,

Janos

|||No, Its not working even after repairing the server.

Thanks
Janos
|||Sorry Vick, I'm out of ideas. I tried to recreate the same error on a virtual machine, but no luck. I'm sorry.|||Hi Janos,

Sp2 is not specific to the service you are using. It upgrades all the services of server (EE, DE, SE, etc).

Check out the link
http://www.microsoft.com/downloads/details.aspx?familyid=d07219b2-1e23-49c8-8f0c-63fa18f26d3a&displaylang=en
|||check out the post.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1793362&SiteID=1

check if you are experiencing the same.

Error while running the "Execute SQL task"

hi frnds,

Till last week my SSIS package was running fine.

now it is throwing the below mentioned error:

SSIS package "DNB_GMS_PO_Transition.dtsx" starting.

Error: 0xC0202009 at DNB_GMS_PO_Transition, Connection manager "CTSINNVLSDNB1\SQLEXPRESS.cedprod.cedprod": An OLE DB error has occurred. Error code: 0x80040E4D.

An OLE DB record is available.Source: "Microsoft SQL Native Client"Hresult: 0x80040E4DDescription: "Login failed for user 'cedprod'.".

Error: 0xC00291EC at Takingbackup of the affected tables, Execute SQL Task: Failed to acquire connection "CTSINNVLSDNB1\SQLEXPRESS.cedprod.cedprod". Connection may not be configured correctly or you may not have the right permissions on this connection.

Task failed: Takingbackup of the affected tables

Warning: 0x80019002 at DNB_GMS_PO_Transition: The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.

SSIS package "DNB_GMS_PO_Transition.dtsx" finished: Failure.

i was unable to figure it out.but i had connected correctly to Database.

if i run those queries in the Query analyser with the same DB connection its running fine.

its urgent.

please tell me the soultion.

And in that Query Analyzer session you were logging in a "CEDPROD"?|||ya i was able to log in the CEDPROD and l logged in the Query Analyser too|||Did you choose to "save the password" in the connection manager when setting it up? Have you promoted this package to SQL Server and are trying to run it there?|||ya i selected the " save my password " and its running fine in SQL Server 2000

Error while executing SSIS package from other SSIS package

Hi,

In our project we have two SSIS package.

And there is a task (Execute SSIS package) in First package that calls the execution of second package.

I m continuously receiving an error "Failed to decrypt protected XML node "PackagePassword" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available."

As we are running first package by job, job runs successfully logging above error

The protection level of second package is set to "EncryptSensitiveWithUserKey"

Can anybody please suggest how to handle it?

If these DTSX has been saved on the MSDB you could use 'Server Storage' as protection level.

EncryptSensitive.. is the default protection level for the packages.

|||

If protection level property of the package has EncryptSensitive WithUSerKey means that only the author of the package is allowed to run it. This KB offers diffrent alternatives to solve your issue:

An SSIS package does not run when you call the SSIS package from a SQL Server Agent job step:

http://support.microsoft.com/kb/918760

|||

Admin,

This topic is a good candidate for a "sticky" for the forum.

This question is asked once a day... we could come up with a synopsis on package encryption

|||

The DTSX is not saved in the MSDB,

its at disk only.

Error While DTS Execution from ASP

I ahve created a DTS package & was able to execute it
from backend but while trying to execute DTS Package
created in local Packages in sql client gets error.
Error Number 2147287038T
Error Description :The system cannot find the file
specified.
package Name :FSPETLISASUpload_DevServer1
Code used
set objDTSPackage = Server.CreateObject("DTS.Package")
on error resume next
objDTSPackage.LoadFromSQLServer "Moody", "fspapp", "w4wmm"
,
DTSSQLStgFlag_Default, "", "", "", "FSPETLISASUpload_DevSe
rver1"
Response.Write err.number & err.Description
Thanks in advance
As a test you may want to try the script (change the obvious variables),
contained at the following link:
http://support.microsoft.com/default...b;en-us;252987
Steve
"Aparna" <nandi_aparna@.yahoo.com> wrote in message
news:02d201c49aa1$d1cef530$a401280a@.phx.gbl...
> I ahve created a DTS package & was able to execute it
> from backend but while trying to execute DTS Package
> created in local Packages in sql client gets error.
>
> Error Number 2147287038T
> Error Description :The system cannot find the file
> specified.
> package Name :FSPETLISASUpload_DevServer1
> Code used
> set objDTSPackage = Server.CreateObject("DTS.Package")
> on error resume next
> objDTSPackage.LoadFromSQLServer "Moody", "fspapp", "w4wmm"
> ,
> DTSSQLStgFlag_Default, "", "", "", "FSPETLISASUpload_DevSe
> rver1"
> Response.Write err.number & err.Description
>
> Thanks in advance
>

Error while debugging the script task

I am getting an while trying to run the script task in debug mode in SSIS package.

"SQL Server Integration Services Script Task has encountered a problem and needs to close. We are sorry for the inconvenience."

Any idea why i am getting this error.

Thanks,

Deepak,

Did you ever find a solution to your issue? I'm having the same thing.

Thanks,
Todd

|||I don't know what the problem is, but I had the same problem as you. I found that I had some Breakpoints sit in other script tasks. When you select the Debug Menu -> Delete All Breakpoints, I assumed it deleted all breakpoints. However, it doesn't seem to clear them out of the script tasks very well. Anyway, I went into every Script Task .NET code and explicity looked and removed all breakpoints. Then, I executed the package. Finally, I added my desired breakpoints back into the particular script task I was debugging. I hope that helps.

Error while debugging the script task

I am getting an while trying to run the script task in debug mode in SSIS package.

"SQL Server Integration Services Script Task has encountered a problem and needs to close. We are sorry for the inconvenience."

Any idea why i am getting this error.

Thanks,

Deepak,

Did you ever find a solution to your issue? I'm having the same thing.

Thanks,
Todd

|||I don't know what the problem is, but I had the same problem as you. I found that I had some Breakpoints sit in other script tasks. When you select the Debug Menu -> Delete All Breakpoints, I assumed it deleted all breakpoints. However, it doesn't seem to clear them out of the script tasks very well. Anyway, I went into every Script Task .NET code and explicity looked and removed all breakpoints. Then, I executed the package. Finally, I added my desired breakpoints back into the particular script task I was debugging. I hope that helps.

Error while debugging the script task

I am getting an while trying to run the script task in debug mode in SSIS package.

"SQL Server Integration Services Script Task has encountered a problem and needs to close. We are sorry for the inconvenience."

Any idea why i am getting this error.

Thanks,

Deepak,

Did you ever find a solution to your issue? I'm having the same thing.

Thanks,
Todd

|||I don't know what the problem is, but I had the same problem as you. I found that I had some Breakpoints sit in other script tasks. When you select the Debug Menu -> Delete All Breakpoints, I assumed it deleted all breakpoints. However, it doesn't seem to clear them out of the script tasks very well. Anyway, I went into every Script Task .NET code and explicity looked and removed all breakpoints. Then, I executed the package. Finally, I added my desired breakpoints back into the particular script task I was debugging. I hope that helps.

Error while creating credentials

Hi guys

I am trying to run an SSIS package by creating a credential. When I try to create a credential thorugh the Mgmt Studio I get the following error:

An error occurred during encryption. (Microsoft SQL Server, Error: 15467)

I tried doing it with the following SQL statement and still have the same error:

CREATE CREDENTIAL JayTest WITH IDENTITY = 'domain\username', SECRET = 'password';

GO

My SQL Server 2005 instance is installed on a Windows Server 2003 box and is running under my NT Account as of now.

Thanks
Jay

Can you please indicate the SQL Server version that you are using (copy-paste the results of 'select @.@.version')?

Credential secrets are encrypted by the service master key (SMK), so it looks like this encryption is failing. We'll need a little more information to figure out what is the cause of the failure:

1) Please check if the SMK exists in your server:

use master
go
select * from sys.symmetric_keys where symmetric_key_id = 102
go

2) If the SMK exists, see if it can be used. You can try creating a master key in a new database or regenerating the SMK:

a)

create database testsmk
go
use testsmk
go
create database master key encryption by password = 'some_password'
go
use master
go
drop database testsmk
go

b)

alter service master key regenerate
go

If there is a problem with the SMK, these two should fail. Let us know what errors you get, if any.

3) Finally, check if there is a user profile directory created for the SQL Server service account.

Also, let us know if you changed the service account for SQL Server; this was not supported and would cause problems, although I would expect a decryption error instead of an encryption error in this case.

Thanks
Laurentiu