Package 'Microsoft SQL Management Studio Package' failed to load

i am working on sql server 2005. i removed dotnet framework 2.0 from my
system and again i installed it . Now i am getting a message Package 'Microsoft SQL Management Studio Package' failed to load , if i click
on ok it is closing.
so please give a solution and it is a trail version of 180 from
microsoft technologies

Quote:

Originally Posted by chandrasekharallu

i am working on sql server 2005. i removed dotnet framework 2.0 from my
system and again i installed it . Now i am getting a message Package 'Microsoft SQL Management Studio Package' failed to load , if i click
on ok it is closing.
so please give a solution and it is a trail version of 180 from
microsoft technologies

It wasn't a wise decision to uninstall .NET 2.0, as SQL Server is deeply integrated with .NET 2.0.

Try reinstalling SQL Server, but I'm not sure if it will correctly identify your trial period.

Package doesn't run anymore on SP2

Hi all,

I've installed SP2 on my server. If I run the package on the server, the package worked there before the installation of SP2. Now with SP2 it doesn't work anymore. In VS2005 on my computer the package works before and after the installation of SP2.

He gives an error with the execution of a sql-task on an oracle server:

Error :Executing the query "insert into cube_content values (trim(?), trim(?), trim(?), trim(?), trim(?), sysdate) failed with the following error: "ORA-01401: inserted value too large for column". Possible failure reasons: Problems with the query, "ResultSet property not set correctly, parameters not set correctly, or connection not established correctly.

Anybody an idea?

Thanks,

Dennis

That error appears to be from the Oracle server, not SSIS related. It looks like you are inserting a value too big for the field.

Look at the table definition and the data you are trying to insert.

|||

It seems as though the interface to Oracle has changed. Do you use the Microsoft OLE DB Provider for Oracle? My best guess is that something in SP2 has changed the provider or something. That's my best guess.

Build a new package using the same SQL statement against Oracle and see if it sets it up with different metadata to what is in your existing package.

-Jamie

OWC in Windows 98 connect to Analysis Services 2005

Is there a posibility to make OWC installed in Windows 98 connect to Analysis Services 2005?

The thing is we cannot install the OLE DB Provider 9.0 for Analysis Services 2005, because it needs Windows Installer 3.1, and we really need to connect OWC to 2005, because we could do it with Analysis Services 2000.

How can we do?

Thanks in advance.

If you want to use OWC, you must have the OLEDB provider 9.0 for Analysis Services. OWC executes on the client and uses OLEDB to talk to the SSAS server.

Unfortunately the only options I can think of if you cannot get the OLEDB provider installed is to either upgrade the client or to look at using something other than OWC. Some of the commercial "thin client" solutions would probably work. Mosha has a list on his site at www.mosha.com/msolap .