Showing posts with label ctp. Show all posts
Showing posts with label ctp. Show all posts

Monday, March 19, 2012

Can't save package to Server (No description found)

I'm getting an error, "No description found", when trying to save my package to the SQL Server (2005).

It was created under the Sept. CTP (SQL 2005) and the matching BI tools, which saved fine. But now with the RTM version I'm getting this error when saving.

I'm in the process of trying different variations, i.e. saving from Sept CTP to current server.... Unforetunately I have clients in next week for training, so I have to find a quick fix or reload the Sept. CTP for training

Anybody else have this issue?

f.y.i.
I'm getting the same error when trying to save maintenance plans on the server.

Versions:
Microsoft SQL Server Management Studio 9.00.1399.00
Microsoft Analysis Services Client Tools 2005.090.1399.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 6.0.2900.2180
Microsoft .NET Framework 2.0.50727.42
Operating System 5.1.2600

Sounds like something is missing, which was not required in Sep CTP, but is now mandatory for RTM. I would expect the RTM tools to fix this. Open the package with the RTM tools (BIDS), and save it again. The reload with upgrade option from the context menu within the solution explorer would also be worth a go.

What method are you using to save to SQL Server?

I have taken plenty of Sep CTP Packages and used them in RTM tools and saved to SQL, but I have worked on them first in BIDS.

|||After building a package and debugging, I'd just use the "Save Copy As" to save it to the server.

I verified it was just my machine. From the server itself and other machines in the office, I could save fine.

I had to re-image my machine so I could get back to work. Everything works fine now.

Checking versions before and after showed the same versions across the board.

Thanks for any suggestions.|||

You did listed the version of IS components.
The error you reported is consistent with older CTP.

|||

I believe it might be due to not having a Visio Service Patch:

http://support.microsoft.com/kb/922546/en-us

Can't save package to Server (No description found)

I'm getting an error, "No description found", when trying to save my package to the SQL Server (2005).

It was created under the Sept. CTP (SQL 2005) and the matching BI tools, which saved fine. But now with the RTM version I'm getting this error when saving.

I'm in the process of trying different variations, i.e. saving from Sept CTP to current server.... Unforetunately I have clients in next week for training, so I have to find a quick fix or reload the Sept. CTP for training

Anybody else have this issue?

f.y.i.
I'm getting the same error when trying to save maintenance plans on the server.

Versions:
Microsoft SQL Server Management Studio 9.00.1399.00
Microsoft Analysis Services Client Tools 2005.090.1399.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 6.0.2900.2180
Microsoft .NET Framework 2.0.50727.42
Operating System 5.1.2600

Sounds like something is missing, which was not required in Sep CTP, but is now mandatory for RTM. I would expect the RTM tools to fix this. Open the package with the RTM tools (BIDS), and save it again. The reload with upgrade option from the context menu within the solution explorer would also be worth a go.

What method are you using to save to SQL Server?

I have taken plenty of Sep CTP Packages and used them in RTM tools and saved to SQL, but I have worked on them first in BIDS.

|||After building a package and debugging, I'd just use the "Save Copy As" to save it to the server.

I verified it was just my machine. From the server itself and other machines in the office, I could save fine.

I had to re-image my machine so I could get back to work. Everything works fine now.

Checking versions before and after showed the same versions across the board.

Thanks for any suggestions.|||

You did listed the version of IS components.
The error you reported is consistent with older CTP.

|||

I believe it might be due to not having a Visio Service Patch:

http://support.microsoft.com/kb/922546/en-us

Thursday, February 16, 2012

Can't install SQL Server 2005 Mobile Edition Server Tools Beta 1

I'm working with VS.NET 2005 Beta2 and SQL Server 2005 April CTP. My
SQL Server 2005 installation was more or less full, that is, I
installed everything related to Client Connectivity. I was bound to
build a merge replication scenario when I've noticed I needed "SQL
Server 2005 Mobile Edition Server Tools Beta 1".
Download the installer and execute it, obtaining the following error:
"You must first install the Replication Components for SQL Server 2000
SP 3a or higher or the SQL Server 2005 Client Connectivity Components."
What is the problem here if I have installed all Client components?
Any help will be greatly appreciated.
Instead of downloading "SQL Server 2005 Mobile Edition Server Tools
Beta 1" from Microsoft, which still warns me that I cannot replicate
with SQL Server 2005 because I don't have Client Connectivity
Components installed, I finally read this on MSDN2:
http://msdn2.microsoft.com/en-us/library/ms171908
The setup file is "sqlce30setupen.msi", located at "C:\Program
Files\Microsoft SQL Server\90\Tools\binn\VSShell\Common7\IDE". This
setup process went ok and did not warn me about anything.
Hope it helps people having the same problem.
PS: How does MS redirect developers to download Server Tools Beta 1 in
order to setup replication and then setup fails or warns the user
wihout any logical reason. Incredible! Can anybody explain me this?

Tuesday, February 14, 2012

Can't install Express June CTP?!

Hey all, I'm trying to install SQL Server 2005 Express June CTP on a windows 2003 Web Edition Server (With SP1).

I've had an old version of the .NET 2.0 Framework installed, so I downloaded the one mentioned next to the SQL Express download (this one: http://go.microsoft.com/fwlink/?linkid=48448).

Each and every time I run the setup I encounter this error:
The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
There is not even any sort of SQL Server service in the list of services, what should I do?
Regards,

Hendrik BehrensI've also tried the same on Windows XP Professional SP2. I had to uninstall a previous version of .NET 2.0 and VWD Express/VB Express Beta 2 are installed.

I get the same error message?! - The service is not there and the setup just fails with that message.

I've had SQL Express April CTP installed on a windows 2003 Enterprise *trial*, which worked, the update to Junce CTP... right, fails with the same message.
Any proposals?|||Did you look for the log files?

-Euan|||Yes I did, and I found the problem: My windows XP Professional and Windows Server 2003 Web Edition are both german - the setup fails on non-english langauge versions with default settings, this german article describes the problem and how to solve it (for everyone else who encounters this):

http://www.microsoft.com/germany/msdn/vs2005/installvs2005beta.mspx
(basically, remove the tick "Hide advanced configuration Options" and select "Local System" as the service account, instead of "Network Service", which is the default.)