Problem in installing SQL express

If you know how to fix my problem , pls let me know. I am trying to install SQL express version with XP SP2 . iIt stops at the screen of "Detecting Installed IIS" . I have tried the same installation in server 2003. It is ok.

I too have the exact same problem. I've got a case logged into MS support and I'll post back whenever they get around to returning my call.
|||OK - I resolved the problem on two identicial clean machines, but we were not sure what exactly resolved the problem. First off, I have two, out-of-the-box Dell 9150s and both came with a Norton Internet Security installed with 'Personnal Firwewall' turned ON. I turned the firewall off and also installed the service packs listed below and I was able to install SQL Express without issue on both machines.

I hope this helps.
Security Update for Windows XP (KB890859)

- Update for Windows XP (KB894391)

- Security Update for Windows XP (KB896428)

- Security Update for Windows XP (KB905749)

- Security Update for Windows XP (KB904706)

- Security Update for Microsoft .NET Framework, Version 1.1 Service Pack 1 (KB886903)

- Critical Update for Windows XP (KB886185)

- Security Update for Windows XP (KB900725)

- Security Update for Windows XP (KB888302)

- Security Update for Windows XP (KB905414)

- Security Update for Windows XP (KB899589)

- Security Update for Windows XP (KB893066)

- Cumulative Security Update for Internet Explorer for Windows XP (KB896688)

- Security Update for Windows XP (KB890046)

- Security Update for Windows XP (KB902400)

- Security Update for Microsoft Windows (KB898458)

- Security Update for Windows XP (KB896358)

- Update for Windows XP (KB887742)

- Security Update for Windows XP (KB896423)

- Security Update for Windows XP (KB893756)

- Security Update for Windows XP (KB896424)

|||

I was having the same problem with the install haning up at the IIS detection on my laptop. I didn't have any problem installing it on my desktop. Both machines are running XP Home. The difference is the desktop has ZoneAlarms as a firewall, while the laptop is running the Norton firewall.

I couldn't install on the laptop either from the download or from a SQL Server Standard Edition CD. They both stopped at the IIS detection.

I turned off the Norton firewall, downloaded the install to my desktop, ran it from there and it installed very quickly.

Problem creating report server project in VS2005 and SQL Server Reporting Services 2000 SP

Hi,
I have SQL Server Reporting Services 2000 (SP2) installed.
If I try and create a Report Server project in Visual Studio 2005, I get the
error:
Project Factory is unable to create an instance of :
Microsoft.ReportDesigner.Project.ReportProjectManager ...
If I try and do this in VS.NET - things seem to work just fine. Is there
anything I can do?
Thanks in advance,
Michael PNo. VS 2003 works wtih RS 2000 designer, VS2005 works with RS 2005 designer.
You can create a RS 2000 report and deploy to a RS 2005 server. You cannot
create a 2005 report and deploy to RS 2000.
RS 2000 is a framework 1.1 app, RS 2005 is a framework 2.0 app. Also, they
both have hooks into the respective IDEs.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Michael P." <michaelpnospam@.ascentium.com> wrote in message
news:ugUG0Gr9FHA.2696@.TK2MSFTNGP11.phx.gbl...
> Hi,
> I have SQL Server Reporting Services 2000 (SP2) installed.
> If I try and create a Report Server project in Visual Studio 2005, I get
> the error:
> Project Factory is unable to create an instance of :
> Microsoft.ReportDesigner.Project.ReportProjectManager ...
> If I try and do this in VS.NET - things seem to work just fine. Is there
> anything I can do?
> Thanks in advance,
> Michael P
>|||Very helpful - thanks.
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:u%23haSKr9FHA.2268@.TK2MSFTNGP15.phx.gbl...
> No. VS 2003 works wtih RS 2000 designer, VS2005 works with RS 2005
> designer.
> You can create a RS 2000 report and deploy to a RS 2005 server. You cannot
> create a 2005 report and deploy to RS 2000.
> RS 2000 is a framework 1.1 app, RS 2005 is a framework 2.0 app. Also, they
> both have hooks into the respective IDEs.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Michael P." <michaelpnospam@.ascentium.com> wrote in message
> news:ugUG0Gr9FHA.2696@.TK2MSFTNGP11.phx.gbl...
>> Hi,
>> I have SQL Server Reporting Services 2000 (SP2) installed.
>> If I try and create a Report Server project in Visual Studio 2005, I get
>> the error:
>> Project Factory is unable to create an instance of :
>> Microsoft.ReportDesigner.Project.ReportProjectManager ...
>> If I try and do this in VS.NET - things seem to work just fine. Is there
>> anything I can do?
>> Thanks in advance,
>> Michael P
>

Problem creating database diagram

I have both SQL Server 2000 and SQL Server 2005 installed on my PC running windows XP SP2.

In the Microsoft SQL Server Management Studio, when I right click Database Diagram in the Object Explorer, I cannot find any option to create a database diagram. What is given is "Working with SQL Server 2000 diagrams".

How can I fix my configuration so that I am able to create database diagrams in the SQL Server 2005?

Did you expand the database diagrams folder first to get the support objects created in the database?

What menu items do you get when you right click on the database diagrams folder?

Also in Help -> about, what version of SQL Server Management Studio do you have installed?

|||1. There isn't anything to expand under the database diagrams folder.
2. Right clicking on this folder gives three items:
a. Working with SQL Server 2000 diagrams
b. Reports --> Custom Report ...
c. Refresh
3. Version info:
Microsoft SQL Server Management Studio 9.00.3042.00
Microsoft Analysis Services Client Tools 2005.090.3042.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 6.0
Microsoft Internet Explorer 6.0.2900.2180
Microsoft .NET Framework 2.0.50727.42
Operating System 5.1.2600

Hope these info help. Thanks.

Problem connection to Express Edition with C#

I'm using .NET 2.0 and SQL Server 2005 Express Edition on WinXP SP2. I'm
using System.Data.SqlClient to connect to the server which is on the same
machine. The SQL Server service is set to log on as "Built-in account: Local
System" and the connection string I'm passing to the constructor is "Data
Source=(local);Initial Catalog=TestDB;" everything else is set to defaults.
I get the following error: "System.Data.SqlClient.SqlException: An error has
occurred while establishing a connection to the server. When connecting to
SQL Server 2005, this failure may be caused by the fact that under the
default settings SQL Server does not allow remote connections. (provider:
Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)"
Any help would be greatly appreciated.
I was fiddling around with different connection strings and this one finally
allowed me to connect: "Data Source=.\\SQLEXPRESS;Initial
Catalog=TestDB;Integrated Security=SSPI;"
"Frustrated" wrote:

> I'm using .NET 2.0 and SQL Server 2005 Express Edition on WinXP SP2. I'm
> using System.Data.SqlClient to connect to the server which is on the same
> machine. The SQL Server service is set to log on as "Built-in account: Local
> System" and the connection string I'm passing to the constructor is "Data
> Source=(local);Initial Catalog=TestDB;" everything else is set to defaults.
> I get the following error: "System.Data.SqlClient.SqlException: An error has
> occurred while establishing a connection to the server. When connecting to
> SQL Server 2005, this failure may be caused by the fact that under the
> default settings SQL Server does not allow remote connections. (provider:
> Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)"
> Any help would be greatly appreciated.
|||You 'normally' always provide at least three pieces of information for a
connection. The Server, the database, and the security context.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Frustrated" <Frustrated@.discussions.microsoft.com> wrote in message
news:0C3946E2-F417-4345-94E7-57B0BA6F9169@.microsoft.com...[vbcol=seagreen]
>I was fiddling around with different connection strings and this one
>finally
> allowed me to connect: "Data Source=.\\SQLEXPRESS;Initial
> Catalog=TestDB;Integrated Security=SSPI;"
> "Frustrated" wrote:

Problem connection to Express Edition with C#

I'm using .NET 2.0 and SQL Server 2005 Express Edition on WinXP SP2. I'm
using System.Data.SqlClient to connect to the server which is on the same
machine. The SQL Server service is set to log on as "Built-in account: Local
System" and the connection string I'm passing to the constructor is "Data
Source=(local);Initial Catalog=TestDB;" everything else is set to defaults.
I get the following error: "System.Data.SqlClient.SqlException: An error has
occurred while establishing a connection to the server. When connecting to
SQL Server 2005, this failure may be caused by the fact that under the
default settings SQL Server does not allow remote connections. (provider:
Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
"
Any help would be greatly appreciated.I was fiddling around with different connection strings and this one finally
allowed me to connect: "Data Source=.\\SQLEXPRESS;Initial
Catalog=TestDB;Integrated Security=SSPI;"
"Frustrated" wrote:

> I'm using .NET 2.0 and SQL Server 2005 Express Edition on WinXP SP2. I'm
> using System.Data.SqlClient to connect to the server which is on the same
> machine. The SQL Server service is set to log on as "Built-in account: Loc
al
> System" and the connection string I'm passing to the constructor is "Data
> Source=(local);Initial Catalog=TestDB;" everything else is set to defaults
.
> I get the following error: "System.Data.SqlClient.SqlException: An error h
as
> occurred while establishing a connection to the server. When connecting t
o
> SQL Server 2005, this failure may be caused by the fact that under the
> default settings SQL Server does not allow remote connections. (provider:
> Named Pipes Provider, error: 40 - Could not open a connection to SQL Serve
r)"
> Any help would be greatly appreciated.|||You 'normally' always provide at least three pieces of information for a
connection. The Server, the database, and the security context.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Frustrated" <Frustrated@.discussions.microsoft.com> wrote in message
news:0C3946E2-F417-4345-94E7-57B0BA6F9169@.microsoft.com...[vbcol=seagreen]
>I was fiddling around with different connection strings and this one
>finally
> allowed me to connect: "Data Source=.\\SQLEXPRESS;Initial
> Catalog=TestDB;Integrated Security=SSPI;"
> "Frustrated" wrote:
>