Can Visual Studio map SQL Server to XSD Schema?

I am creating an annual XML document to submit to a government agency. They have published an XSD Schema. Our data is in SQL Server 2000.

I need some way of associating columns from tables in SQL Server 2000 with the elements from the XSD schema to produce a valid XML document.

It looks like I could use XMLSpy or Stylus Studio, but I think there must be some way of doing it in Visual Studio 2005. Does Visual Studio 2005 have tools to help me do this? Can anyone direct me to a WebCast or part of the documentation that would dexplain I can do this?

(P.S. If you are curious, this is for the CDFI CIIS)

SQLXML has support for mapping between SQL Server and XSD using annotations in the XSD schema. There is no tool to visualize the mapping. Here is an overview of mapping schemas:

http://msdn2.microsoft.com/en-us/library/ms171870(SQL.90).aspx

This article is about SQLXML 4, but also applies to SQLXML 3 which is available on msdn:

http://www.microsoft.com/downloads/details.aspx?FamilyID=51D4A154-8E23-47D2-A033-764259CFB53B&displaylang=en

|||Thank you for your response-- I'll check out the links.

Can Visual Studio map SQL Server to XSD Schema?

I am creating an annual XML document to submit to a government agency. They have published an XSD Schema. Our data is in SQL Server 2000.

I need some way of associating columns from tables in SQL Server 2000 with the elements from the XSD schema to produce a valid XML document.

It looks like I could use XMLSpy or Stylus Studio, but I think there must be some way of doing it in Visual Studio 2005. Does Visual Studio 2005 have tools to help me do this? Can anyone direct me to a WebCast or part of the documentation that would dexplain I can do this?

(P.S. If you are curious, this is for the CDFI CIIS)

SQLXML has support for mapping between SQL Server and XSD using annotations in the XSD schema. There is no tool to visualize the mapping. Here is an overview of mapping schemas:

http://msdn2.microsoft.com/en-us/library/ms171870(SQL.90).aspx

This article is about SQLXML 4, but also applies to SQLXML 3 which is available on msdn:

http://www.microsoft.com/downloads/details.aspx?FamilyID=51D4A154-8E23-47D2-A033-764259CFB53B&displaylang=en

|||Thank you for your response-- I'll check out the links.

Can Visual Studio 2005 BI co-exist with Visual Studio 2003?

I ask because I'm still looking for the source of interface problems I have in using the SSIS designer.

Yes. I have the two side by side and develop projects of most types in both.

Not sure if there is an official guide to this but I have found in the past that it always pays to install the older software first, followed by the later version.

|||Thanks Darren. Just wanted to make sure I wasn't making a fundamental mistake.|||Can Visual Studio Orcas and Visual Studio 2005 coexist?sql

Can Visual Studio 2005 BI co-exist with Visual Studio 2003?

I ask because I'm still looking for the source of interface problems I have in using the SSIS designer.

Yes. I have the two side by side and develop projects of most types in both.

Not sure if there is an official guide to this but I have found in the past that it always pays to install the older software first, followed by the later version.

|||Thanks Darren. Just wanted to make sure I wasn't making a fundamental mistake.|||Can Visual Studio Orcas and Visual Studio 2005 coexist?

Can user view objects they only have select permission on?

I have a user that belongs to a role. This role only has select permissions
on 10 views. When I log in as this user via Management Studio I cannot see
the views however I can execute queries against them.
On another server that I did not setup, that I'm supposed to be mimicking
the same security, this same user can see the views.
Any ideas what the difference is?
Thanks!Here's the commands that I'm executing in order:
CREATE ROLE [Customers_ROLE] Authorization dbo
CREATE SCHEMA [Customers_Schema] AUTHORIZATION [Customers_Role] Deny
View
Definition to [Customers_Role]
exec sp_adduser 'phenson', 'phenson', [Customers_Role]
GRANT SELECT ON [dbo].[PT_VIEW] TO [Customers_Role]
When I log in as phenson I do not see PT_View but I can query on it. I need
to be able to see it.
"SpankyATL" wrote:

> I have a user that belongs to a role. This role only has select permissio
ns
> on 10 views. When I log in as this user via Management Studio I cannot se
e
> the views however I can execute queries against them.
> On another server that I did not setup, that I'm supposed to be mimicking
> the same security, this same user can see the views.
> Any ideas what the difference is?
> Thanks!|||I thought I'd answer my own question for those of you who come across this
some day. I need to remove the "Deny View Definition" portion and that took
care of it. The user was able to see that view and execute it but could not
see the script.
"SpankyATL" wrote:
[vbcol=seagreen]
> Here's the commands that I'm executing in order:
> CREATE ROLE [Customers_ROLE] Authorization dbo
> CREATE SCHEMA [Customers_Schema] AUTHORIZATION [Customers_Role] De
ny View
> Definition to [Customers_Role]
> exec sp_adduser 'phenson', 'phenson', [Customers_Role]
> GRANT SELECT ON [dbo].[PT_VIEW] TO [Customers_Role]
>
> When I log in as phenson I do not see PT_View but I can query on it. I ne
ed
> to be able to see it.
> "SpankyATL" wrote:
>|||SpankyATL (SpankyATL@.discussions.microsoft.com) writes:
> Here's the commands that I'm executing in order:
> CREATE ROLE [Customers_ROLE] Authorization dbo
> CREATE SCHEMA [Customers_Schema] AUTHORIZATION [Customers_Role] De
ny View
> Definition to [Customers_Role]
> exec sp_adduser 'phenson', 'phenson', [Customers_Role]
> GRANT SELECT ON [dbo].[PT_VIEW] TO [Customers_Role]
>
> When I log in as phenson I do not see PT_View but I can query on it. I
> need to be able to see it.
Why then did you do DENY VIEW DEFINITION to a role that you made phenson a
member of?
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||I was working from a script that was given to me. The person who developed
it mistakenly thought deny view would only deny the user from viewing the
source code.
"Erland Sommarskog" wrote:

> SpankyATL (SpankyATL@.discussions.microsoft.com) writes:
> Why then did you do DENY VIEW DEFINITION to a role that you made phenson a
> member of?
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/pr...oads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodin...ions/books.mspx
>

Can the SQL Server Managament Studio connect to ODBC sources?

Hi,
Can the SQL Server Managament Studio connect to ODBC sources?
If so, how do you do it? I've not done much with ODBC before...
Thanks,
Alan
http://www.sadevelopment.com
Partition Boot Manager and Large Drive Tools utilities!SSMS does not use the ODBC API. However, you can connect to any SQL Server
via SSMS as long as you know the server name and login credentials. You can
get that information by viewing the properties of the existing SQL Server
ODBC data source or connection string.
Hope this helps.
Dan Guzman
SQL Server MVP
"Default User" <nospam38925@.forme.com> wrote in message
news:4623694e$0$23404$c3e8da3@.news.astraweb.com...
> Hi,
> Can the SQL Server Managament Studio connect to ODBC sources?
> If so, how do you do it? I've not done much with ODBC before...
> Thanks,
> Alan
> http://www.sadevelopment.com
> Partition Boot Manager and Large Drive Tools utilities!
>|||Hi Dan,

> SSMS does not use the ODBC API. However, you can connect to any SQL
> Server via SSMS as long as you know the server name and login credentials.
> You can get that information by viewing the properties of the existing SQL
> Server ODBC data source or connection string.
Too bad, I was hoping to connect to ODBC with it. Does anyone have any idea
what tool or tools I could use to connect and troubleshoot ODBC...
Alan
http://www.sadevelopment.com
Partition Boot Manager and Large Drive Tools utilities!|||Can you elaborate on what you mean by "connect and troubleshoot ODBC"? If
you are trying to test ODBC data source connectivity, the ODBC data source
setup has a button to test the connection.
Hope this helps.
Dan Guzman
SQL Server MVP
"Default User" <nospam38925@.forme.com> wrote in message
news:4623b9c6$0$873$c3e8da3@.news.astraweb.com...
> Hi Dan,
>
> Too bad, I was hoping to connect to ODBC with it. Does anyone have any
> idea what tool or tools I could use to connect and troubleshoot ODBC...
> Alan
> http://www.sadevelopment.com
> Partition Boot Manager and Large Drive Tools utilities!
>|||Hi,

> Can you elaborate on what you mean by "connect and troubleshoot ODBC"? If
> you are trying to test ODBC data source connectivity, the ODBC data source
> setup has a button to test the connection.
Yes, I'm looking for a tool that lets you connect to ODBC and use it much
the way the SQL management studio lets you connect to MSSQL...
Thanks,
Alan|||> Yes, I'm looking for a tool that lets you connect to ODBC and use it much
> the way the SQL management studio lets you connect to MSSQL...
So you need to query ODBC data sources other than Micosoft SQL Server? If
you need only SQL Server, I still don't understand why you have the ODBC
requirement.
Hope this helps.
Dan Guzman
SQL Server MVP
"Default User" <nospam38925@.forme.com> wrote in message
news:4627a5d7$0$4674$c3e8da3@.news.astraweb.com...
> Hi,
>
> Yes, I'm looking for a tool that lets you connect to ODBC and use it much
> the way the SQL management studio lets you connect to MSSQL...
> Thanks,
> Alan
>

Can the SQL Server Managament Studio connect to ODBC sources?

Hi,
Can the SQL Server Managament Studio connect to ODBC sources?
If so, how do you do it? I've not done much with ODBC before...
Thanks,
Alan
http://www.sadevelopment.com
Partition Boot Manager and Large Drive Tools utilities!
SSMS does not use the ODBC API. However, you can connect to any SQL Server
via SSMS as long as you know the server name and login credentials. You can
get that information by viewing the properties of the existing SQL Server
ODBC data source or connection string.
Hope this helps.
Dan Guzman
SQL Server MVP
"Default User" <nospam38925@.forme.com> wrote in message
news:4623694e$0$23404$c3e8da3@.news.astraweb.com...
> Hi,
> Can the SQL Server Managament Studio connect to ODBC sources?
> If so, how do you do it? I've not done much with ODBC before...
> Thanks,
> Alan
> http://www.sadevelopment.com
> Partition Boot Manager and Large Drive Tools utilities!
>
|||Hi Dan,

> SSMS does not use the ODBC API. However, you can connect to any SQL
> Server via SSMS as long as you know the server name and login credentials.
> You can get that information by viewing the properties of the existing SQL
> Server ODBC data source or connection string.
Too bad, I was hoping to connect to ODBC with it. Does anyone have any idea
what tool or tools I could use to connect and troubleshoot ODBC...
Alan
http://www.sadevelopment.com
Partition Boot Manager and Large Drive Tools utilities!
|||Can you elaborate on what you mean by "connect and troubleshoot ODBC"? If
you are trying to test ODBC data source connectivity, the ODBC data source
setup has a button to test the connection.
Hope this helps.
Dan Guzman
SQL Server MVP
"Default User" <nospam38925@.forme.com> wrote in message
news:4623b9c6$0$873$c3e8da3@.news.astraweb.com...
> Hi Dan,
>
> Too bad, I was hoping to connect to ODBC with it. Does anyone have any
> idea what tool or tools I could use to connect and troubleshoot ODBC...
> Alan
> http://www.sadevelopment.com
> Partition Boot Manager and Large Drive Tools utilities!
>
|||Hi,

> Can you elaborate on what you mean by "connect and troubleshoot ODBC"? If
> you are trying to test ODBC data source connectivity, the ODBC data source
> setup has a button to test the connection.
Yes, I'm looking for a tool that lets you connect to ODBC and use it much
the way the SQL management studio lets you connect to MSSQL...
Thanks,
Alan
|||> Yes, I'm looking for a tool that lets you connect to ODBC and use it much
> the way the SQL management studio lets you connect to MSSQL...
So you need to query ODBC data sources other than Micosoft SQL Server? If
you need only SQL Server, I still don't understand why you have the ODBC
requirement.
Hope this helps.
Dan Guzman
SQL Server MVP
"Default User" <nospam38925@.forme.com> wrote in message
news:4627a5d7$0$4674$c3e8da3@.news.astraweb.com...
> Hi,
>
> Yes, I'm looking for a tool that lets you connect to ODBC and use it much
> the way the SQL management studio lets you connect to MSSQL...
> Thanks,
> Alan
>

Can the SQL Server Managament Studio connect to ODBC sources?

Hi,
Can the SQL Server Managament Studio connect to ODBC sources?
If so, how do you do it? I've not done much with ODBC before...
Thanks,
Alan
http://www.sadevelopment.com
Partition Boot Manager and Large Drive Tools utilities!SSMS does not use the ODBC API. However, you can connect to any SQL Server
via SSMS as long as you know the server name and login credentials. You can
get that information by viewing the properties of the existing SQL Server
ODBC data source or connection string.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Default User" <nospam38925@.forme.com> wrote in message
news:4623694e$0$23404$c3e8da3@.news.astraweb.com...
> Hi,
> Can the SQL Server Managament Studio connect to ODBC sources?
> If so, how do you do it? I've not done much with ODBC before...
> Thanks,
> Alan
> http://www.sadevelopment.com
> Partition Boot Manager and Large Drive Tools utilities!
>|||Hi Dan,
> SSMS does not use the ODBC API. However, you can connect to any SQL
> Server via SSMS as long as you know the server name and login credentials.
> You can get that information by viewing the properties of the existing SQL
> Server ODBC data source or connection string.
Too bad, I was hoping to connect to ODBC with it. Does anyone have any idea
what tool or tools I could use to connect and troubleshoot ODBC...
Alan
http://www.sadevelopment.com
Partition Boot Manager and Large Drive Tools utilities!|||Can you elaborate on what you mean by "connect and troubleshoot ODBC"? If
you are trying to test ODBC data source connectivity, the ODBC data source
setup has a button to test the connection.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Default User" <nospam38925@.forme.com> wrote in message
news:4623b9c6$0$873$c3e8da3@.news.astraweb.com...
> Hi Dan,
>> SSMS does not use the ODBC API. However, you can connect to any SQL
>> Server via SSMS as long as you know the server name and login
>> credentials. You can get that information by viewing the properties of
>> the existing SQL Server ODBC data source or connection string.
> Too bad, I was hoping to connect to ODBC with it. Does anyone have any
> idea what tool or tools I could use to connect and troubleshoot ODBC...
> Alan
> http://www.sadevelopment.com
> Partition Boot Manager and Large Drive Tools utilities!
>|||Hi,
> Can you elaborate on what you mean by "connect and troubleshoot ODBC"? If
> you are trying to test ODBC data source connectivity, the ODBC data source
> setup has a button to test the connection.
Yes, I'm looking for a tool that lets you connect to ODBC and use it much
the way the SQL management studio lets you connect to MSSQL...
Thanks,
Alan|||> Yes, I'm looking for a tool that lets you connect to ODBC and use it much
> the way the SQL management studio lets you connect to MSSQL...
So you need to query ODBC data sources other than Micosoft SQL Server? If
you need only SQL Server, I still don't understand why you have the ODBC
requirement.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Default User" <nospam38925@.forme.com> wrote in message
news:4627a5d7$0$4674$c3e8da3@.news.astraweb.com...
> Hi,
>> Can you elaborate on what you mean by "connect and troubleshoot ODBC"?
>> If you are trying to test ODBC data source connectivity, the ODBC data
>> source setup has a button to test the connection.
> Yes, I'm looking for a tool that lets you connect to ODBC and use it much
> the way the SQL management studio lets you connect to MSSQL...
> Thanks,
> Alan
>

Can SQL express be accessed by Oracle Transparent Gateway ?

Able to access SQL express remotely using SQL mgt Studio after certain configuration.

But notice that I must use IP address/SQLEXPRESS for server name in order for connection to work. What is this "/SQLEXPRESS" ? Is it a standard surfix for SQL Express ?

I have installed the Oracle Transparent Gateway on the machine with SQL Express and setup the tnsname for SQL Express. For the tnsname, have used IP address/SQLEXPRESS as the host name but it gave this error :

ORA-28545: NCRO Failed to make RSLV connection

Tried with just the IP address and it gives the same error.

Any idea ? ? Help !

Hi,

What is this "/SQLEXPRESS"

That si the instance name, as you can deploy several instances (liek in Oracle on one machine, with the difference that one instance can have more than one database :-) ), the instances are bound to a port, if it is not the default port (1433), you have to specify it, either within the connectionstring are in your Gui.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de
|||I check the SQL Server configuration manager and it shows that the instance name is MSSQL.1. So which one is the instance name ?

Can SQL 2008 coexist with SQL2005?

I have a SQL 2005 installed on my laptop with Windows XP Media Center Edition with the following components:

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.1318
Operating System 5.1.2600

Is upgrade the only option or can SQL 2008 can exist with SQL2005?

Any help in instlling this would be helpful.

(Jayaram Krishnaswamy@.discussions.microsoft.com) writes: > I have a SQL 2005 installed on my laptop with Windows XP Media Center > Edition with the following components: > > > > 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.1318 > Operating System 5.1.2600 > > > > Is upgrade the only option or can SQL 2008 can exist with SQL2005? You should be able to do a side-by-side installation, since you only have the client tools. But I strongly recommend that you install Katmai, or any other beta software, on a virtual machine, or a machine that you can afford to scrap and reformat. And do definitely not upgrade, if you want to keep the machine. By the way, I notice that you have the RTM version of the SQL 2005 tools. I would recommend that you get hold of SP2 and install that. It does bring quite a few improvements. -- Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se Books Online for SQL Server 2005 at http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx Books Online for SQL Server 2000 at http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx|||Thamk you very much. Could you rpovide me with links for setting up on a virtual machine?|||(Jayaram Krishnaswamy@.discussions.microsoft.com) writes: > Thamk you very much. Could you rpovide me with links for setting up on a > virtual machine? It's not difficult at all. There's two products on the market I know of, Virtual PC from Microsoft and VMware. I stick to VMware myself. You can download VMware worksation from http://www.vmware.com. The most difficult part is probably the amount for the license... Once you have it installed, you use the wizard to create a new machine. To install the OS, just insert the OS in your DVD player, and VMware will pick it up. From there, it's very much like a regular install. VMware also has a VMware Player which is free. I'm uncertain whether it's good for creating new machines. Virtual PC comes with MSDN, so financially you may find it more attractive. I never used VPC myself, but rumour has it that VMware is a little more able. A tip when you set up your virtual machine, you first install the OS, activates it, and also add other programs that you don't want to be without. Before you actually slap any beta software on it, clone the machine, and install the beta software on the clone. That is, keep a template machine, so that you don't have to install the OS for each new CTP that comes out. A second tip is to make sure that you have sufficient with memory in your host machine. 1.5 GB is a minimum, if you give 250 MB to the virtual machine. -- Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se Books Online for SQL Server 2005 at http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx Books Online for SQL Server 2000 at http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx|||

Thanks for the advice. Much obliged

Can SQL 2000 Enterprise Manager & SQL 2005 Mgnt Studio coexist ?

Hi,
I have SQL 2000 Client (Enterprise Manager, QA etc) installed on my PC. I
would like to install SQL 2005 native client (Mgnt Studio etc) on the same PC.
Can they be coexisted and both can be used ? OR
I have to uninstall 2000 client first.
Regards,
Johnny
Hello,
They can co-exist. Make sure you installl the software in seperate
directory.
Thanks
Hari
"Johnny" <Johnny@.discussions.microsoft.com> wrote in message
news:F553693B-19D1-4EA7-9EEC-062287EE1628@.microsoft.com...
> Hi,
> I have SQL 2000 Client (Enterprise Manager, QA etc) installed on my PC. I
> would like to install SQL 2005 native client (Mgnt Studio etc) on the same
> PC.
> Can they be coexisted and both can be used ? OR
> I have to uninstall 2000 client first.
> Regards,
> Johnny
|||Johnny (Johnny@.discussions.microsoft.com) writes:
> I have SQL 2000 Client (Enterprise Manager, QA etc) installed on my PC.
> I would like to install SQL 2005 native client (Mgnt Studio etc) on the
> same PC.
> Can they be coexisted and both can be used ? OR
> I have to uninstall 2000 client first.
They can co-exist as Hari said.
I just like to make a clafication: SQL Native Client is a single DLL
which contains an updated ODBC driver and an updated OLE DB provider
for SQL 2005. SQL Native is a redistributable component. SQL Native is
about the first which is installed when you run the SQL Server installation.
You are apparently thinking of the Workstation components, of which some
may use SQL Native Client, but far from all do. Management Studio, for
instance, uses SqlClient, a .Net provider. ("Native" in SQL Native Client
refers to that it is in native code, as opposed to the managed code of
..Net.)
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

can some one please tell me about the server name?

this is my first time to leave messange at here . I wish someone can tell me how to sign in at sql server management studio express CTP s server name .plsssssssssssssssssssssssssssssssssssssssssssssss

This is the SSIS forum. You should try and post the the management tools forum.

Thanks,

Matt

Can Not View Report Server Web Pages

I have installed the Business Intelligence Studio on my PC and had no
problems creating a report, but when I go to http:\\localhost\reportserver,
I just see a directory listing in the browser instead of the web interface.
Where should I look to troubleshoot?
TIA
Dean> Where should I look to troubleshoot?
No place -- you're prolly fine.
Try http://localhost/reports if you want the Report Manager interface...
>L<
"Dean" <deanl144@.hotmail.com.nospam> wrote in message
news:%23p6kzVcqHHA.1220@.TK2MSFTNGP04.phx.gbl...
>I have installed the Business Intelligence Studio on my PC and had no
>problems creating a report, but when I go to http:\\localhost\reportserver,
>I just see a directory listing in the browser instead of the web interface.
>Where should I look to troubleshoot?
> TIA
> Dean
>

Can not see server components during setup

Hi,
I an trying to install Reporting Service 2000 on my machine, it has Windows
XP with SP1, SQL 2000 Developer edition with SP3a, Visual Studio.Net 2003.
This is the first time I try Reporting Services, I am going to make my
machine a Report Server and for reports authoring.
However during the setup, I only see Client Components, Server Components do
not show at all. I even read rssetup,chm on the CD, it confirms that there
are server components to be installed.
What am I missing here?
TIAYou need to have IIS installed for server components to be installed. XP
does not have it running by default. RS is a asp.net application.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Danny Ni" <dnd@.yahoo.com> wrote in message
news:OmExS1Q4FHA.3636@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I an trying to install Reporting Service 2000 on my machine, it has
> Windows
> XP with SP1, SQL 2000 Developer edition with SP3a, Visual Studio.Net
> 2003.
> This is the first time I try Reporting Services, I am going to make my
> machine a Report Server and for reports authoring.
> However during the setup, I only see Client Components, Server Components
> do
> not show at all. I even read rssetup,chm on the CD, it confirms that there
> are server components to be installed.
> What am I missing here?
> TIA
>|||I am sorry to give out wrong information last time. The OS is Windows XP Pro
with SP1, so it does have IIS.
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:%239j3$CU4FHA.1140@.tk2msftngp13.phx.gbl...
> You need to have IIS installed for server components to be installed. XP
> does not have it running by default. RS is a asp.net application.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Danny Ni" <dnd@.yahoo.com> wrote in message
> news:OmExS1Q4FHA.3636@.TK2MSFTNGP09.phx.gbl...
> > Hi,
> >
> > I an trying to install Reporting Service 2000 on my machine, it has
> > Windows
> > XP with SP1, SQL 2000 Developer edition with SP3a, Visual Studio.Net
> > 2003.
> > This is the first time I try Reporting Services, I am going to make my
> > machine a Report Server and for reports authoring.
> >
> > However during the setup, I only see Client Components, Server
Components
> > do
> > not show at all. I even read rssetup,chm on the CD, it confirms that
there
> > are server components to be installed.
> >
> > What am I missing here?
> >
> > TIA
> >
> >
>|||Yes, but is it running? By default IIS is not running with XP Pro.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Danny Ni" <dnd@.yahoo.com> wrote in message
news:%23OwFibd4FHA.2872@.TK2MSFTNGP15.phx.gbl...
>I am sorry to give out wrong information last time. The OS is Windows XP
>Pro
> with SP1, so it does have IIS.
>
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:%239j3$CU4FHA.1140@.tk2msftngp13.phx.gbl...
>> You need to have IIS installed for server components to be installed. XP
>> does not have it running by default. RS is a asp.net application.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "Danny Ni" <dnd@.yahoo.com> wrote in message
>> news:OmExS1Q4FHA.3636@.TK2MSFTNGP09.phx.gbl...
>> > Hi,
>> >
>> > I an trying to install Reporting Service 2000 on my machine, it has
>> > Windows
>> > XP with SP1, SQL 2000 Developer edition with SP3a, Visual Studio.Net
>> > 2003.
>> > This is the first time I try Reporting Services, I am going to make my
>> > machine a Report Server and for reports authoring.
>> >
>> > However during the setup, I only see Client Components, Server
> Components
>> > do
>> > not show at all. I even read rssetup,chm on the CD, it confirms that
> there
>> > are server components to be installed.
>> >
>> > What am I missing here?
>> >
>> > TIA
>> >
>> >
>>
>|||Yes. IIS is running. I actually created several ASP.Net web applications
using VS.Net 2003.
Thanks Again
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:Ol5dr7h4FHA.2532@.TK2MSFTNGP09.phx.gbl...
> Yes, but is it running? By default IIS is not running with XP Pro.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Danny Ni" <dnd@.yahoo.com> wrote in message
> news:%23OwFibd4FHA.2872@.TK2MSFTNGP15.phx.gbl...
> >I am sorry to give out wrong information last time. The OS is Windows XP
> >Pro
> > with SP1, so it does have IIS.
> >
> >
> > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> > news:%239j3$CU4FHA.1140@.tk2msftngp13.phx.gbl...
> >> You need to have IIS installed for server components to be installed.
XP
> >> does not have it running by default. RS is a asp.net application.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >>
> >> "Danny Ni" <dnd@.yahoo.com> wrote in message
> >> news:OmExS1Q4FHA.3636@.TK2MSFTNGP09.phx.gbl...
> >> > Hi,
> >> >
> >> > I an trying to install Reporting Service 2000 on my machine, it has
> >> > Windows
> >> > XP with SP1, SQL 2000 Developer edition with SP3a, Visual Studio.Net
> >> > 2003.
> >> > This is the first time I try Reporting Services, I am going to make
my
> >> > machine a Report Server and for reports authoring.
> >> >
> >> > However during the setup, I only see Client Components, Server
> > Components
> >> > do
> >> > not show at all. I even read rssetup,chm on the CD, it confirms that
> > there
> >> > are server components to be installed.
> >> >
> >> > What am I missing here?
> >> >
> >> > TIA
> >> >
> >> >
> >>
> >>
> >
> >
>|||OK, I believe the only version that is supported on XP Pro is the developer
edition of RS (the trial version works as well).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Danny Ni" <dnd@.yahoo.com> wrote in message
news:%23R8p7%23C5FHA.2396@.TK2MSFTNGP14.phx.gbl...
> Yes. IIS is running. I actually created several ASP.Net web applications
> using VS.Net 2003.
> Thanks Again
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:Ol5dr7h4FHA.2532@.TK2MSFTNGP09.phx.gbl...
>> Yes, but is it running? By default IIS is not running with XP Pro.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Danny Ni" <dnd@.yahoo.com> wrote in message
>> news:%23OwFibd4FHA.2872@.TK2MSFTNGP15.phx.gbl...
>> >I am sorry to give out wrong information last time. The OS is Windows XP
>> >Pro
>> > with SP1, so it does have IIS.
>> >
>> >
>> > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> > news:%239j3$CU4FHA.1140@.tk2msftngp13.phx.gbl...
>> >> You need to have IIS installed for server components to be installed.
> XP
>> >> does not have it running by default. RS is a asp.net application.
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >>
>> >> "Danny Ni" <dnd@.yahoo.com> wrote in message
>> >> news:OmExS1Q4FHA.3636@.TK2MSFTNGP09.phx.gbl...
>> >> > Hi,
>> >> >
>> >> > I an trying to install Reporting Service 2000 on my machine, it has
>> >> > Windows
>> >> > XP with SP1, SQL 2000 Developer edition with SP3a, Visual
>> >> > Studio.Net
>> >> > 2003.
>> >> > This is the first time I try Reporting Services, I am going to make
> my
>> >> > machine a Report Server and for reports authoring.
>> >> >
>> >> > However during the setup, I only see Client Components, Server
>> > Components
>> >> > do
>> >> > not show at all. I even read rssetup,chm on the CD, it confirms that
>> > there
>> >> > are server components to be installed.
>> >> >
>> >> > What am I missing here?
>> >> >
>> >> > TIA
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>>
>

Can not open SQL Management Studio

All of a sudden out of the blue today, Sql Server Management Studio refuses to load and open.

I'm running Windows XP x64.

Sql Server Dev. Edition x64. (Release version.. There were never Beta versions on the machine)

When I open the program this dialog opens:

Microsoft SQL Server Management Studio

Package 'Microsoft SQL Management Studio Package' failed to load.

OK

(It appears twice and then the UI fails to open)

Also, in Visual Studio 2005, when I try to make a database connection in Server Explorer, I get this error

Microsoft Visual Studio

Could not load file or assembly 'Microsoft.VisualStudio.Data, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Failed to grant minimum permission requests. (Exception from HRESULT: 0x80131417)

OK

These problems have not been encountered before and I have been using my current setup for months. Cannot thikn of anything that has changed today to cause this.

Ideas?

Did you try the repair option from the Add and Remove PRograms?|||

I ended up un-installing every .Net Fx 2.0 related and installed all over again.

(SQL Server 2005, Visual Studio 2005 etc)

That was a waste of a day.. But it works again.

|||I'm experiencing the exact same problem. Uninstalling and re-installing VS .NET fixed the Visual Studio error, but the SQL Management Studio problem persists. I tried uninstalling and reinstalling the management componenets, but that did not work. Even so, re-installation is a workaround, and one I'm not willing to do everytime a problem creeps up. Does anyone have any permenant solutions?

Thank you.|||

The most likely cause of this is if a file has been deleted or corrupted. Does repairing the SQL Server management tools fix the problem?

Repairing SQL Server is a command-line operation. You can repair by inserting the installation media into the disk drive and typing the following:

start /wait <CD or DVD Drive>\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

You can find more information on installing SQL Server from the command line here: http://msdn2.microsoft.com/en-us/library/ms144259.aspx

Hope this helps,
Steve

|||I just installed SP1 for SQL Server 2005. However, this problem persists.|||Ok. I just figured out both the errors in SQL Management Studio and Visual Studio. It was really stupid. Somehow, the shortcut icons on the desktop were altered. Instead of having the path to the executables of each application be "c:\program files\....", the path read "\\computername\c$\program files\...". Therefore, the two applications, based on .NET themselves were running as intranet zoned applications. Therefore, they were unable to make data connections because of the default setup for the intranet zone CAS. I changed the paths back to c:\ and it worked fine.

I have no idea how they got like this because I just dragged them out of the start menu and dropped them on the desktop like I've done for every other application. I checked my other shortcuts and they are all OK. Got me...|||I reinstalled .Net 2.0 and that fixed it for me.|||

Somehow this has happened to me again. Following the repair instructions

start /wait d:\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

fixed the problem.

I didn't notice the other post about checking out the shortcuts until after I did this, so I dont know if that was the problem.

|||

I want to comment on Jetgunner's post.

I have found that my shortcuts have changed just as his has.. instead of C:\... they were \\machine\c\....

I have no idea why they are like that either.

|||

I also encountered the error Package 'Microsoft SQL Server Management Studio' failed to load (even with my shortcut correctly pointing to "C:\program files....") but have discovered that it was caused by .NET permission settings. I had changed the My_Computer_Zone code group permission set from "FullTrust" to "Everything" (for the local Machine policy). Changing it back to FullTrust fixed it and Management Studio fired up ok.

Tom.

|||

Running that worked for me.

Thanks so much...

start /wait E:\apps\SQL2005\Tools\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

|||

Hey Jetgunner,

Not sure if you're still going to see that there has been anything posted to this thread, as it was a year ago. But I wanted to ask if you had been using Virtual PC on the same machine you were having this issue.

I have several virtual PC installations with SQL server 2005, and that's the reason I think the shortcut gets the "c$" accidently carried over into it. It has to be either something to do with Virtual PC or something to do with Remote Desktop. Those are the two things I use quite a bit and might have effected my shortcut to SQL Management Studio.

Can anyone else confirm or deny this?

Thanks,

Doug

|||

Package 'Microsoft SQL Management Studio Package' failed to load.

-

I tried to reinstall .NET 2.0 framework and IT WORKED FOR ME***********

Scenario-->In a virtual machine (Vmware) copied from another one,sql server management studio was throwing the error [Package 'Microsoft SQL Management Studio Package' failed to load.]

|||

***WORKED FOR ME TOO***

Thanks,

Deepesh

Can not open SQL Management Studio

All of a sudden out of the blue today, Sql Server Management Studio refuses to load and open.

I'm running Windows XP x64.

Sql Server Dev. Edition x64. (Release version.. There were never Beta versions on the machine)

When I open the program this dialog opens:

Microsoft SQL Server Management Studio

Package 'Microsoft SQL Management Studio Package' failed to load.

OK

(It appears twice and then the UI fails to open)

Also, in Visual Studio 2005, when I try to make a database connection in Server Explorer, I get this error

Microsoft Visual Studio

Could not load file or assembly 'Microsoft.VisualStudio.Data, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Failed to grant minimum permission requests. (Exception from HRESULT: 0x80131417)

OK

These problems have not been encountered before and I have been using my current setup for months. Cannot thikn of anything that has changed today to cause this.

Ideas?

Did you try the repair option from the Add and Remove PRograms?|||

I ended up un-installing every .Net Fx 2.0 related and installed all over again.

(SQL Server 2005, Visual Studio 2005 etc)

That was a waste of a day.. But it works again.

|||I'm experiencing the exact same problem. Uninstalling and re-installing VS .NET fixed the Visual Studio error, but the SQL Management Studio problem persists. I tried uninstalling and reinstalling the management componenets, but that did not work. Even so, re-installation is a workaround, and one I'm not willing to do everytime a problem creeps up. Does anyone have any permenant solutions?

Thank you.
|||

The most likely cause of this is if a file has been deleted or corrupted. Does repairing the SQL Server management tools fix the problem?

Repairing SQL Server is a command-line operation. You can repair by inserting the installation media into the disk drive and typing the following:

start /wait <CD or DVD Drive>\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

You can find more information on installing SQL Server from the command line here: http://msdn2.microsoft.com/en-us/library/ms144259.aspx

Hope this helps,
Steve

|||I just installed SP1 for SQL Server 2005. However, this problem persists.
|||Ok. I just figured out both the errors in SQL Management Studio and Visual Studio. It was really stupid. Somehow, the shortcut icons on the desktop were altered. Instead of having the path to the executables of each application be "c:\program files\....", the path read "\\computername\c$\program files\...". Therefore, the two applications, based on .NET themselves were running as intranet zoned applications. Therefore, they were unable to make data connections because of the default setup for the intranet zone CAS. I changed the paths back to c:\ and it worked fine.

I have no idea how they got like this because I just dragged them out of the start menu and dropped them on the desktop like I've done for every other application. I checked my other shortcuts and they are all OK. Got me...
|||I reinstalled .Net 2.0 and that fixed it for me.|||

Somehow this has happened to me again. Following the repair instructions

start /wait d:\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

fixed the problem.

I didn't notice the other post about checking out the shortcuts until after I did this, so I dont know if that was the problem.

|||

I want to comment on Jetgunner's post.

I have found that my shortcuts have changed just as his has.. instead of C:\... they were \\machine\c\....

I have no idea why they are like that either.

|||

I also encountered the error Package 'Microsoft SQL Server Management Studio' failed to load (even with my shortcut correctly pointing to "C:\program files....") but have discovered that it was caused by .NET permission settings. I had changed the My_Computer_Zone code group permission set from "FullTrust" to "Everything" (for the local Machine policy). Changing it back to FullTrust fixed it and Management Studio fired up ok.

Tom.

|||

Running that worked for me.

Thanks so much...

start /wait E:\apps\SQL2005\Tools\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

|||

Hey Jetgunner,

Not sure if you're still going to see that there has been anything posted to this thread, as it was a year ago. But I wanted to ask if you had been using Virtual PC on the same machine you were having this issue.

I have several virtual PC installations with SQL server 2005, and that's the reason I think the shortcut gets the "c$" accidently carried over into it. It has to be either something to do with Virtual PC or something to do with Remote Desktop. Those are the two things I use quite a bit and might have effected my shortcut to SQL Management Studio.

Can anyone else confirm or deny this?

Thanks,

Doug

|||

Package 'Microsoft SQL Management Studio Package' failed to load.

-

I tried to reinstall .NET 2.0 framework and IT WORKED FOR ME***********

Scenario-->In a virtual machine (Vmware) copied from another one,sql server management studio was throwing the error [Package 'Microsoft SQL Management Studio Package' failed to load.]

|||

***WORKED FOR ME TOO***

Thanks,

Deepesh

Can not open SQL Management Studio

All of a sudden out of the blue today, Sql Server Management Studio refuses to load and open.

I'm running Windows XP x64.

Sql Server Dev. Edition x64. (Release version.. There were never Beta versions on the machine)

When I open the program this dialog opens:

Microsoft SQL Server Management Studio

Package 'Microsoft SQL Management Studio Package' failed to load.

OK

(It appears twice and then the UI fails to open)

Also, in Visual Studio 2005, when I try to make a database connection in Server Explorer, I get this error

Microsoft Visual Studio

Could not load file or assembly 'Microsoft.VisualStudio.Data, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Failed to grant minimum permission requests. (Exception from HRESULT: 0x80131417)

OK

These problems have not been encountered before and I have been using my current setup for months. Cannot thikn of anything that has changed today to cause this.

Ideas?

Did you try the repair option from the Add and Remove PRograms?|||

I ended up un-installing every .Net Fx 2.0 related and installed all over again.

(SQL Server 2005, Visual Studio 2005 etc)

That was a waste of a day.. But it works again.

|||I'm experiencing the exact same problem. Uninstalling and re-installing VS .NET fixed the Visual Studio error, but the SQL Management Studio problem persists. I tried uninstalling and reinstalling the management componenets, but that did not work. Even so, re-installation is a workaround, and one I'm not willing to do everytime a problem creeps up. Does anyone have any permenant solutions?

Thank you.
|||

The most likely cause of this is if a file has been deleted or corrupted. Does repairing the SQL Server management tools fix the problem?

Repairing SQL Server is a command-line operation. You can repair by inserting the installation media into the disk drive and typing the following:

start /wait <CD or DVD Drive>\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

You can find more information on installing SQL Server from the command line here: http://msdn2.microsoft.com/en-us/library/ms144259.aspx

Hope this helps,
Steve

|||I just installed SP1 for SQL Server 2005. However, this problem persists.
|||Ok. I just figured out both the errors in SQL Management Studio and Visual Studio. It was really stupid. Somehow, the shortcut icons on the desktop were altered. Instead of having the path to the executables of each application be "c:\program files\....", the path read "\\computername\c$\program files\...". Therefore, the two applications, based on .NET themselves were running as intranet zoned applications. Therefore, they were unable to make data connections because of the default setup for the intranet zone CAS. I changed the paths back to c:\ and it worked fine.

I have no idea how they got like this because I just dragged them out of the start menu and dropped them on the desktop like I've done for every other application. I checked my other shortcuts and they are all OK. Got me...
|||I reinstalled .Net 2.0 and that fixed it for me.|||

Somehow this has happened to me again. Following the repair instructions

start /wait d:\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

fixed the problem.

I didn't notice the other post about checking out the shortcuts until after I did this, so I dont know if that was the problem.

|||

I want to comment on Jetgunner's post.

I have found that my shortcuts have changed just as his has.. instead of C:\... they were \\machine\c\....

I have no idea why they are like that either.

|||

I also encountered the error Package 'Microsoft SQL Server Management Studio' failed to load (even with my shortcut correctly pointing to "C:\program files....") but have discovered that it was caused by .NET permission settings. I had changed the My_Computer_Zone code group permission set from "FullTrust" to "Everything" (for the local Machine policy). Changing it back to FullTrust fixed it and Management Studio fired up ok.

Tom.

|||

Running that worked for me.

Thanks so much...

start /wait E:\apps\SQL2005\Tools\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

|||

Hey Jetgunner,

Not sure if you're still going to see that there has been anything posted to this thread, as it was a year ago. But I wanted to ask if you had been using Virtual PC on the same machine you were having this issue.

I have several virtual PC installations with SQL server 2005, and that's the reason I think the shortcut gets the "c$" accidently carried over into it. It has to be either something to do with Virtual PC or something to do with Remote Desktop. Those are the two things I use quite a bit and might have effected my shortcut to SQL Management Studio.

Can anyone else confirm or deny this?

Thanks,

Doug

|||

Package 'Microsoft SQL Management Studio Package' failed to load.

-

I tried to reinstall .NET 2.0 framework and IT WORKED FOR ME***********

Scenario-->In a virtual machine (Vmware) copied from another one,sql server management studio was throwing the error [Package 'Microsoft SQL Management Studio Package' failed to load.]

|||

***WORKED FOR ME TOO***

Thanks,

Deepesh

Can not open SQL Management Studio

All of a sudden out of the blue today, Sql Server Management Studio refuses to load and open.

I'm running Windows XP x64.

Sql Server Dev. Edition x64. (Release version.. There were never Beta versions on the machine)

When I open the program this dialog opens:

Microsoft SQL Server Management Studio

Package 'Microsoft SQL Management Studio Package' failed to load.

OK

(It appears twice and then the UI fails to open)

Also, in Visual Studio 2005, when I try to make a database connection in Server Explorer, I get this error

Microsoft Visual Studio

Could not load file or assembly 'Microsoft.VisualStudio.Data, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Failed to grant minimum permission requests. (Exception from HRESULT: 0x80131417)

OK

These problems have not been encountered before and I have been using my current setup for months. Cannot thikn of anything that has changed today to cause this.

Ideas?

Did you try the repair option from the Add and Remove PRograms?|||

I ended up un-installing every .Net Fx 2.0 related and installed all over again.

(SQL Server 2005, Visual Studio 2005 etc)

That was a waste of a day.. But it works again.

|||I'm experiencing the exact same problem. Uninstalling and re-installing VS .NET fixed the Visual Studio error, but the SQL Management Studio problem persists. I tried uninstalling and reinstalling the management componenets, but that did not work. Even so, re-installation is a workaround, and one I'm not willing to do everytime a problem creeps up. Does anyone have any permenant solutions?

Thank you.
|||

The most likely cause of this is if a file has been deleted or corrupted. Does repairing the SQL Server management tools fix the problem?

Repairing SQL Server is a command-line operation. You can repair by inserting the installation media into the disk drive and typing the following:

start /wait <CD or DVD Drive>\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

You can find more information on installing SQL Server from the command line here: http://msdn2.microsoft.com/en-us/library/ms144259.aspx

Hope this helps,
Steve

|||I just installed SP1 for SQL Server 2005. However, this problem persists.
|||Ok. I just figured out both the errors in SQL Management Studio and Visual Studio. It was really stupid. Somehow, the shortcut icons on the desktop were altered. Instead of having the path to the executables of each application be "c:\program files\....", the path read "\\computername\c$\program files\...". Therefore, the two applications, based on .NET themselves were running as intranet zoned applications. Therefore, they were unable to make data connections because of the default setup for the intranet zone CAS. I changed the paths back to c:\ and it worked fine.

I have no idea how they got like this because I just dragged them out of the start menu and dropped them on the desktop like I've done for every other application. I checked my other shortcuts and they are all OK. Got me...
|||I reinstalled .Net 2.0 and that fixed it for me.|||

Somehow this has happened to me again. Following the repair instructions

start /wait d:\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

fixed the problem.

I didn't notice the other post about checking out the shortcuts until after I did this, so I dont know if that was the problem.

|||

I want to comment on Jetgunner's post.

I have found that my shortcuts have changed just as his has.. instead of C:\... they were \\machine\c\....

I have no idea why they are like that either.

|||

I also encountered the error Package 'Microsoft SQL Server Management Studio' failed to load (even with my shortcut correctly pointing to "C:\program files....") but have discovered that it was caused by .NET permission settings. I had changed the My_Computer_Zone code group permission set from "FullTrust" to "Everything" (for the local Machine policy). Changing it back to FullTrust fixed it and Management Studio fired up ok.

Tom.

|||

Running that worked for me.

Thanks so much...

start /wait E:\apps\SQL2005\Tools\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

|||

Hey Jetgunner,

Not sure if you're still going to see that there has been anything posted to this thread, as it was a year ago. But I wanted to ask if you had been using Virtual PC on the same machine you were having this issue.

I have several virtual PC installations with SQL server 2005, and that's the reason I think the shortcut gets the "c$" accidently carried over into it. It has to be either something to do with Virtual PC or something to do with Remote Desktop. Those are the two things I use quite a bit and might have effected my shortcut to SQL Management Studio.

Can anyone else confirm or deny this?

Thanks,

Doug

|||

Package 'Microsoft SQL Management Studio Package' failed to load.

-

I tried to reinstall .NET 2.0 framework and IT WORKED FOR ME***********

Scenario-->In a virtual machine (Vmware) copied from another one,sql server management studio was throwing the error [Package 'Microsoft SQL Management Studio Package' failed to load.]

|||

***WORKED FOR ME TOO***

Thanks,

Deepesh

Can not open SQL Management Studio

All of a sudden out of the blue today, Sql Server Management Studio refuses to load and open.

I'm running Windows XP x64.

Sql Server Dev. Edition x64. (Release version.. There were never Beta versions on the machine)

When I open the program this dialog opens:

Microsoft SQL Server Management Studio

Package 'Microsoft SQL Management Studio Package' failed to load.

OK

(It appears twice and then the UI fails to open)

Also, in Visual Studio 2005, when I try to make a database connection in Server Explorer, I get this error

Microsoft Visual Studio

Could not load file or assembly 'Microsoft.VisualStudio.Data, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Failed to grant minimum permission requests. (Exception from HRESULT: 0x80131417)

OK

These problems have not been encountered before and I have been using my current setup for months. Cannot thikn of anything that has changed today to cause this.

Ideas?

Did you try the repair option from the Add and Remove PRograms?|||

I ended up un-installing every .Net Fx 2.0 related and installed all over again.

(SQL Server 2005, Visual Studio 2005 etc)

That was a waste of a day.. But it works again.

|||I'm experiencing the exact same problem. Uninstalling and re-installing VS .NET fixed the Visual Studio error, but the SQL Management Studio problem persists. I tried uninstalling and reinstalling the management componenets, but that did not work. Even so, re-installation is a workaround, and one I'm not willing to do everytime a problem creeps up. Does anyone have any permenant solutions?

Thank you.
|||

The most likely cause of this is if a file has been deleted or corrupted. Does repairing the SQL Server management tools fix the problem?

Repairing SQL Server is a command-line operation. You can repair by inserting the installation media into the disk drive and typing the following:

start /wait <CD or DVD Drive>\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

You can find more information on installing SQL Server from the command line here: http://msdn2.microsoft.com/en-us/library/ms144259.aspx

Hope this helps,
Steve

|||I just installed SP1 for SQL Server 2005. However, this problem persists.
|||Ok. I just figured out both the errors in SQL Management Studio and Visual Studio. It was really stupid. Somehow, the shortcut icons on the desktop were altered. Instead of having the path to the executables of each application be "c:\program files\....", the path read "\\computername\c$\program files\...". Therefore, the two applications, based on .NET themselves were running as intranet zoned applications. Therefore, they were unable to make data connections because of the default setup for the intranet zone CAS. I changed the paths back to c:\ and it worked fine.

I have no idea how they got like this because I just dragged them out of the start menu and dropped them on the desktop like I've done for every other application. I checked my other shortcuts and they are all OK. Got me...
|||I reinstalled .Net 2.0 and that fixed it for me.|||

Somehow this has happened to me again. Following the repair instructions

start /wait d:\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

fixed the problem.

I didn't notice the other post about checking out the shortcuts until after I did this, so I dont know if that was the problem.

|||

I want to comment on Jetgunner's post.

I have found that my shortcuts have changed just as his has.. instead of C:\... they were \\machine\c\....

I have no idea why they are like that either.

|||

I also encountered the error Package 'Microsoft SQL Server Management Studio' failed to load (even with my shortcut correctly pointing to "C:\program files....") but have discovered that it was caused by .NET permission settings. I had changed the My_Computer_Zone code group permission set from "FullTrust" to "Everything" (for the local Machine policy). Changing it back to FullTrust fixed it and Management Studio fired up ok.

Tom.

|||

Running that worked for me.

Thanks so much...

start /wait E:\apps\SQL2005\Tools\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

|||

Hey Jetgunner,

Not sure if you're still going to see that there has been anything posted to this thread, as it was a year ago. But I wanted to ask if you had been using Virtual PC on the same machine you were having this issue.

I have several virtual PC installations with SQL server 2005, and that's the reason I think the shortcut gets the "c$" accidently carried over into it. It has to be either something to do with Virtual PC or something to do with Remote Desktop. Those are the two things I use quite a bit and might have effected my shortcut to SQL Management Studio.

Can anyone else confirm or deny this?

Thanks,

Doug

|||

Package 'Microsoft SQL Management Studio Package' failed to load.

-

I tried to reinstall .NET 2.0 framework and IT WORKED FOR ME***********

Scenario-->In a virtual machine (Vmware) copied from another one,sql server management studio was throwing the error [Package 'Microsoft SQL Management Studio Package' failed to load.]

|||

***WORKED FOR ME TOO***

Thanks,

Deepesh

Can not open SQL Management Studio

All of a sudden out of the blue today, Sql Server Management Studio refuses to load and open.

I'm running Windows XP x64.

Sql Server Dev. Edition x64. (Release version.. There were never Beta versions on the machine)

When I open the program this dialog opens:

Microsoft SQL Server Management Studio

Package 'Microsoft SQL Management Studio Package' failed to load.

OK

(It appears twice and then the UI fails to open)

Also, in Visual Studio 2005, when I try to make a database connection in Server Explorer, I get this error

Microsoft Visual Studio

Could not load file or assembly 'Microsoft.VisualStudio.Data, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Failed to grant minimum permission requests. (Exception from HRESULT: 0x80131417)

OK

These problems have not been encountered before and I have been using my current setup for months. Cannot thikn of anything that has changed today to cause this.

Ideas?

Did you try the repair option from the Add and Remove PRograms?|||

I ended up un-installing every .Net Fx 2.0 related and installed all over again.

(SQL Server 2005, Visual Studio 2005 etc)

That was a waste of a day.. But it works again.

|||I'm experiencing the exact same problem. Uninstalling and re-installing VS .NET fixed the Visual Studio error, but the SQL Management Studio problem persists. I tried uninstalling and reinstalling the management componenets, but that did not work. Even so, re-installation is a workaround, and one I'm not willing to do everytime a problem creeps up. Does anyone have any permenant solutions?

Thank you.
|||

The most likely cause of this is if a file has been deleted or corrupted. Does repairing the SQL Server management tools fix the problem?

Repairing SQL Server is a command-line operation. You can repair by inserting the installation media into the disk drive and typing the following:

start /wait <CD or DVD Drive>\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

You can find more information on installing SQL Server from the command line here: http://msdn2.microsoft.com/en-us/library/ms144259.aspx

Hope this helps,
Steve

|||I just installed SP1 for SQL Server 2005. However, this problem persists.
|||Ok. I just figured out both the errors in SQL Management Studio and Visual Studio. It was really stupid. Somehow, the shortcut icons on the desktop were altered. Instead of having the path to the executables of each application be "c:\program files\....", the path read "\\computername\c$\program files\...". Therefore, the two applications, based on .NET themselves were running as intranet zoned applications. Therefore, they were unable to make data connections because of the default setup for the intranet zone CAS. I changed the paths back to c:\ and it worked fine.

I have no idea how they got like this because I just dragged them out of the start menu and dropped them on the desktop like I've done for every other application. I checked my other shortcuts and they are all OK. Got me...
|||I reinstalled .Net 2.0 and that fixed it for me.|||

Somehow this has happened to me again. Following the repair instructions

start /wait d:\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

fixed the problem.

I didn't notice the other post about checking out the shortcuts until after I did this, so I dont know if that was the problem.

|||

I want to comment on Jetgunner's post.

I have found that my shortcuts have changed just as his has.. instead of C:\... they were \\machine\c\....

I have no idea why they are like that either.

|||

I also encountered the error Package 'Microsoft SQL Server Management Studio' failed to load (even with my shortcut correctly pointing to "C:\program files....") but have discovered that it was caused by .NET permission settings. I had changed the My_Computer_Zone code group permission set from "FullTrust" to "Everything" (for the local Machine policy). Changing it back to FullTrust fixed it and Management Studio fired up ok.

Tom.

|||

Running that worked for me.

Thanks so much...

start /wait E:\apps\SQL2005\Tools\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

|||

Hey Jetgunner,

Not sure if you're still going to see that there has been anything posted to this thread, as it was a year ago. But I wanted to ask if you had been using Virtual PC on the same machine you were having this issue.

I have several virtual PC installations with SQL server 2005, and that's the reason I think the shortcut gets the "c$" accidently carried over into it. It has to be either something to do with Virtual PC or something to do with Remote Desktop. Those are the two things I use quite a bit and might have effected my shortcut to SQL Management Studio.

Can anyone else confirm or deny this?

Thanks,

Doug

|||

Package 'Microsoft SQL Management Studio Package' failed to load.

-

I tried to reinstall .NET 2.0 framework and IT WORKED FOR ME***********

Scenario-->In a virtual machine (Vmware) copied from another one,sql server management studio was throwing the error [Package 'Microsoft SQL Management Studio Package' failed to load.]

|||

***WORKED FOR ME TOO***

Thanks,

Deepesh