Board index MS SQL Server

Problems with Packages after applying ServicePack2 to SQL7

Problems with Packages after applying ServicePack2 to SQL7

Post by Mark Locket » Thu, 14 Sep 2000 15:55:05



We have been running SQL7 for about 1 and a half years, and it is great.
It is running on a PC with NT Server4.0, service pack 6a
There are a couple of nice features in Service Pack 2 (cell-level security in
OLAP), so I installed it yesterday

The installation went very smoothly for the SQL7 portion.
There are 2 complaints:
When installing the OLAP portion of the Service Pack, it failed with a message
about C:\NTSRV4\SYSTEM32\MSCAL.OCX , which it said was probably in use.  I cannot
see why.

Even more important: next day I discovered that none of my Local DTS Packages
will run:  On entering Package | Designer or Package | Execute, I get a message:
"Error occurred during creation of a DTS package" [Ok].

If I try to create a new package, I get:
"Could not create Component Categories Manager" [Ok]
followed by "Error occurred during creation of a DTS package" [Ok].

Kind regards
Mark Lockett

 
 
 
Top

Problems with Packages after applying ServicePack2 to SQL7

Post by Paul Bowma » Sat, 16 Sep 2000 04:00:00


Funny, we have the same behaviour on our SQL Servers here. But only when
accessing them "remotely" via Enterprise Manager on a networked machine.
When we actually use the server directly we can create and execute packages
normally. So we end up having to use pcAnywhere or Terminal Services Client
to connect to the server in question to create and administer DTS packages.
Also when connected "directly" to one of the servers, you can create
packages on other servers that we've set up access for on said servers
Enterprise Manager. ANy news you get on this annoying feature would be much
appreciated.


We have been running SQL7 for about 1 and a half years, and it is great.
It is running on a PC with NT Server4.0, service pack 6a
There are a couple of nice features in Service Pack 2 (cell-level security
in
OLAP), so I installed it yesterday

The installation went very smoothly for the SQL7 portion.
There are 2 complaints:
When installing the OLAP portion of the Service Pack, it failed with a
message
about C:\NTSRV4\SYSTEM32\MSCAL.OCX , which it said was probably in use.  I
cannot
see why.

Even more important: next day I discovered that none of my Local DTS
Packages
will run:  On entering Package | Designer or Package | Execute, I get a
message:
"Error occurred during creation of a DTS package" [Ok].

If I try to create a new package, I get:
"Could not create Component Categories Manager" [Ok]
followed by "Error occurred during creation of a DTS package" [Ok].

Kind regards
Mark Lockett

 
 
 
Top

Problems with Packages after applying ServicePack2 to SQL7

Post by Mark Locket » Mon, 18 Sep 2000 04:00:00


Hi Paul

Your behaviour seems a bit different if I have got, if I understand you
correctly:  It seems to me if your behaviour is what one would expect if the
server has the SP2 applied (which converts all the packages to the new SP2
format), and the clients are still on SP1, which would not be able to see the new
packages.  this much is documented.  I am no getting very far with Microsoft,
yet  

Kind regards
Mark Lockett

.

 
 
 
Top

1. MSDE servicepack2 addnew update problem

Anybody please help!

I am writing do a database using ADO AddNew Update, using MSDE as a
temporary database engine.  This has worked fine for a long time,
however, as I upgraded the MSDE with service pack 2, my code seems
broken.

This fails whether I am using Visual C++ or Visual Basic and even with
the examples that are included in Microsoft documentation on adding
records to the pubs database.  Update fails with
Run-time error '-2147217887 (80040e21)': Errors occurred.

SQL INSERT INTO still works fine.

According to KB article Q189220 there are some problems in some
contexts with AddNew and shaping of SQL queries.  However, if I trace
the queries using the profiler, it does not even use SQL insert to add
fields to the database, but some other script language.  Neither does
it seem to help to relabel my columns.

To access the database, I am using the SQLOLEDB driver.

Suggestions anyone?

KH

Sent via Deja.com http://www.deja.com/
Before you buy.

2. Accessing DAO as the Data Control Does

3. Windows DNA Questions

4. Access: "Query too complex"

5. How does SQL7 apply filters?

6. Using a TTable in a DLL

7. xp_sendmail hangs in SQL7.0 when after applying SR2 for Outlook

8. Error when applying SP3 to SQL7 - EXCEPTION_FLT_UNDERFLOW

9. MSDTC not work after apply SQL7 SP3 on cluster

10. Installing Pervasive ServicePack2

11. DTS problem SQL7->DTS->Excel->DTS->SQL7


All times are UTC
Board index