Hello, I am using SQL Server 2000 sp3a. I have a DTS
package that has been running fine every day for over a
year. Today I opened the package in the DTS Designer and
modified one query in an Execute SQL Task. When I clicked
the Save button, I got the following error:

Package Error
Error Source : Microsoft OLE DB Provider for SQL Server
Error Description : Unspecified error

and the modifications were not saved. The package is saved
in location option "SQL Server". I have tried logging off
and back on again as a Cluster Administrator user, but I
get the same error every time.

Any ideas what is causing this and how to fix?

Can you create a brand new package on that server and save?

If not then have look at reregistering the dtspkg.dll.



--

----------------------------

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org


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

Yes, when I create a brand new package, I can save it
successfully.

OK then are you running into this issue?

Package Ownership Issues
(http://www.sqldts.com/default.aspx?212)

--

----------------------------

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org


<anonymous (AT) discussions (DOT) microsoft.com> wrote

There should not be a problem with the package owner - we
have not changed any permissions or security settings
regarding the owner for months.

I think this is part of a wider series of problems on the
server. All day I have been getting various errors
(e.g. "701 insufficient system memory"; unable to log into
Query Analyser "login failed for user (null). Reason: not
associated with a trusted connection" among others)

I tried taking all the SQL Server resources offline and
back online, and trying saving the package again - same
thing happens.

Then just out of interest, I tried changing the owner of
the package using the method in the web page above. Once
again, I couldn't save any changes to the DTS package,
even after taking all the SQL Server resources offline and
back online again.

Now for the weird part - after spending a couple of hours
searching the web for advice on these symptoms, I tried
saving the package again, and it worked! But I have
noticed that the owner of the package has now changed back
to the original owner, and is NOT the owner I changed it
to earlier. And I know for a fact that I only changed it
once... Does the process of saving a package change the
Oner to the Creator?