Requirements to set up on a new server?

I wanted to test drive the reporting services against Crystal.
I have a new stage server system where all servers were just promoted to
Win2003, and SQL 2000 on the data server box.
I understand that I need to put the reporting services on my IIS box. That
has .NET 2003 run time and SP applied.
When I attempt to install Reporting Services I get a lame error back about
lacking resources. This is the Reporting 2000 version. What am I missing?
TIA
__StephenWhat is the error? Please copy in the exact error message, and it's easier
to help. :) What resources are missing?
Have you installed Internet Information Services on your RS box? WIthout IIS
you won't get far with RS.
Kaisa M. Lindahl
"__Stephen" <srussell@.transactiongraphics.com> wrote in message
news:OddBAscHGHA.1132@.TK2MSFTNGP10.phx.gbl...
>I wanted to test drive the reporting services against Crystal.
> I have a new stage server system where all servers were just promoted to
> Win2003, and SQL 2000 on the data server box.
> I understand that I need to put the reporting services on my IIS box.
> That has .NET 2003 run time and SP applied.
> When I attempt to install Reporting Services I get a lame error back about
> lacking resources. This is the Reporting 2000 version. What am I
> missing?
> TIA
> __Stephen
>

requirements to connect to a named instance of MSDE 2.0

What is the propery syntax to establish a connection with a named instance
of MSDE on a server from a client workstation using the SQL Query analyzer
(or EM for that matter)?
I have tried "myServer\myInstance" to no positive effect.
Could I do this via TCP from a remote PC? What would be the syntax for
that?
Thanks.
Hi
"myServer\myInstance, portnumber"
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"astro" <astro@.bcmn.com> wrote in message
news:VorVd.24398$Sq5.7292@.twister.rdc-kc.rr.com...
> What is the propery syntax to establish a connection with a named instance
> of MSDE on a server from a client workstation using the SQL Query analyzer
> (or EM for that matter)?
> I have tried "myServer\myInstance" to no positive effect.
> Could I do this via TCP from a remote PC? What would be the syntax for
> that?
> Thanks.
>
>

requirements to connect to a named instance of MSDE 2.0

What is the propery syntax to establish a connection with a named instance
of MSDE on a server from a client workstation using the SQL Query analyzer
(or EM for that matter)?
I have tried "myServer\myInstance" to no positive effect.
Could I do this via TCP from a remote PC? What would be the syntax for
that?
Thanks.Hi
"myServer\myInstance, portnumber"
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"astro" <astro@.bcmn.com> wrote in message
news:VorVd.24398$Sq5.7292@.twister.rdc-kc.rr.com...
> What is the propery syntax to establish a connection with a named instance
> of MSDE on a server from a client workstation using the SQL Query analyzer
> (or EM for that matter)?
> I have tried "myServer\myInstance" to no positive effect.
> Could I do this via TCP from a remote PC? What would be the syntax for
> that?
> Thanks.
>
>

Requirements for Sql Server Mobile and Sql Server 2003 interaction

Folks,

I am trying to use .NET 2005 Beta 2 to write an application targeted to a PPC2003 device. I want to use RDA to Push and Pull data from a Sql Server 2003 database.

This communication fails because I do not have sscesa30.dll in the IIS virtual directory from which the data are pulled.

I would like to know exactly what I need to install on the server so that everything is wired up correctly.

I do not really want to install Sql Server 2005 (CPT) on my server. Is there an SDK that I can install there that makes the sscesa30.dll available? Can it be run without any Sql Server 2005 (CPT) requirements?

Thanks in advance.
-Joel Finkel
finkel@.sd-il.comHi,

I am really not aware of SQL Server 2003. SQL Mobile 3.0 works with both SQL Server 2000 and SQL Server 2005.

I believe that you are working with SQL Server 2000? If so read below!

Given that SQL Mobile 3.0 works with SQL Server 2000. That is you can have SQL Server old version but have the SQL Mobile/CE clients with latest version.

This is what is expected infrastructure:

1) Server Box - SQL Server 2000 SP3a or above
2) IIS Box - Install I1, I2 in order.
3) Device - SQL Mobile 3.0 (Can get from Visual Studio 2005)

I1 - http://www.microsoft.com/downloads/details.aspx?FamilyId=09545A2A-3D2A-4811-AFD5-41AF0F6DF2B3&displaylang=en
I2 - http://www.microsoft.com/downloads/details.aspx?familyid=0A6174A4-C009-4768-8284-698C32EC84E3&displaylang=en

Also, please note that IIS & SQL Server can be on one box. In which case only install I2 on SQL Server Box. You do not need to install I1.

Let me know if you need any more information.

Thanks,
Laxmi NRO, MSFT, SQL Mobile

|||

Thanks for your help, but I have run into issues.

Here is my setup:

IIS 6
Sql Server 2000 (SP4)
Windows 2003 Server

Referring to your note, you write:

"Also, please note that IIS & SQL Server can be on one box.
In which case only install I2 on SQL Server Box. You do not
need to install I1."

Howevever:

When I attempt to install I2, it fails because I have not yet installed I1.

When I attempt to install I1, it fails because I am not running
Sql Server 2000 SP3 or SP3a. I am runnning SP4.

This has now become a critical issue. Any help is greatly appreciated.

|||I2 in the above thread is a beta one by which time SP4 was not shipped.
I2 latest version that works with SP4 is shipped with VS 2005.

The web downloads will be updated with the latest version soon.

Thanks,
Laxmi NRO, MSFT, SQL Mobile, Microsoft Corporation

Requirements for Sql Server Mobile and Sql Server 2003 interaction

Folks,

I am trying to use .NET 2005 Beta 2 to write an application targeted to a PPC2003 device. I want to use RDA to Push and Pull data from a Sql Server 2003 database.

This communication fails because I do not have sscesa30.dll in the IIS virtual directory from which the data are pulled.

I would like to know exactly what I need to install on the server so that everything is wired up correctly.

I do not really want to install Sql Server 2005 (CPT) on my server. Is there an SDK that I can install there that makes the sscesa30.dll available? Can it be run without any Sql Server 2005 (CPT) requirements?

Thanks in advance.
-Joel Finkel
finkel@.sd-il.comHi,

I am really not aware of SQL Server 2003. SQL Mobile 3.0 works with both SQL Server 2000 and SQL Server 2005.

I believe that you are working with SQL Server 2000? If so read below!

Given that SQL Mobile 3.0 works with SQL Server 2000. That is you can have SQL Server old version but have the SQL Mobile/CE clients with latest version.

This is what is expected infrastructure:

1) Server Box - SQL Server 2000 SP3a or above
2) IIS Box - Install I1, I2 in order.
3) Device - SQL Mobile 3.0 (Can get from Visual Studio 2005)

I1 - http://www.microsoft.com/downloads/details.aspx?FamilyId=09545A2A-3D2A-4811-AFD5-41AF0F6DF2B3&displaylang=en
I2 - http://www.microsoft.com/downloads/details.aspx?familyid=0A6174A4-C009-4768-8284-698C32EC84E3&displaylang=en

Also, please note that IIS & SQL Server can be on one box. In which case only install I2 on SQL Server Box. You do not need to install I1.

Let me know if you need any more information.

Thanks,
Laxmi NRO, MSFT, SQL Mobile|||

Thanks for your help, but I have run into issues.

Here is my setup:

IIS 6
Sql Server 2000 (SP4)
Windows 2003 Server

Referring to your note, you write:

"Also, please note that IIS & SQL Server can be on one box.
In which case only install I2 on SQL Server Box. You do not
need to install I1."

Howevever:

When I attempt to install I2, it fails because I have not yet installed I1.

When I attempt to install I1, it fails because I am not running
Sql Server 2000 SP3 or SP3a. I am runnning SP4.

This has now become a critical issue. Any help is greatly appreciated.

|||I2 in the above thread is a beta one by which time SP4 was not shipped.
I2 latest version that works with SP4 is shipped with VS 2005.

The web downloads will be updated with the latest version soon.

Thanks,
Laxmi NRO, MSFT, SQL Mobile, Microsoft Corporation

Requirements for Sql Server Mobile and Sql Server 2003 interaction

Folks,

I am trying to use .NET 2005 Beta 2 to write an application targeted to a PPC2003 device. I want to use RDA to Push and Pull data from a Sql Server 2003 database.

This communication fails because I do not have sscesa30.dll in the IIS virtual directory from which the data are pulled.

I would like to know exactly what I need to install on the server so that everything is wired up correctly.

I do not really want to install Sql Server 2005 (CPT) on my server. Is there an SDK that I can install there that makes the sscesa30.dll available? Can it be run without any Sql Server 2005 (CPT) requirements?

Thanks in advance.
-Joel Finkel
finkel@.sd-il.comHi,

I am really not aware of SQL Server 2003. SQL Mobile 3.0 works with both SQL Server 2000 and SQL Server 2005.

I believe that you are working with SQL Server 2000? If so read below!

Given that SQL Mobile 3.0 works with SQL Server 2000. That is you can have SQL Server old version but have the SQL Mobile/CE clients with latest version.

This is what is expected infrastructure:

1) Server Box - SQL Server 2000 SP3a or above
2) IIS Box - Install I1, I2 in order.
3) Device - SQL Mobile 3.0 (Can get from Visual Studio 2005)

I1 - http://www.microsoft.com/downloads/details.aspx?FamilyId=09545A2A-3D2A-4811-AFD5-41AF0F6DF2B3&displaylang=en
I2 - http://www.microsoft.com/downloads/details.aspx?familyid=0A6174A4-C009-4768-8284-698C32EC84E3&displaylang=en

Also, please note that IIS & SQL Server can be on one box. In which case only install I2 on SQL Server Box. You do not need to install I1.

Let me know if you need any more information.

Thanks,
Laxmi NRO, MSFT, SQL Mobile|||

Thanks for your help, but I have run into issues.

Here is my setup:

IIS 6
Sql Server 2000 (SP4)
Windows 2003 Server

Referring to your note, you write:

"Also, please note that IIS & SQL Server can be on one box.
In which case only install I2 on SQL Server Box. You do not
need to install I1."

Howevever:

When I attempt to install I2, it fails because I have not yet installed I1.

When I attempt to install I1, it fails because I am not running
Sql Server 2000 SP3 or SP3a. I am runnning SP4.

This has now become a critical issue. Any help is greatly appreciated.

|||I2 in the above thread is a beta one by which time SP4 was not shipped.
I2 latest version that works with SP4 is shipped with VS 2005.

The web downloads will be updated with the latest version soon.

Thanks,
Laxmi NRO, MSFT, SQL Mobile, Microsoft Corporation

Requirements for non-administrative service account for clustered SQL 2000

I understand from Microsoft that a SQL Server 2000 Cluster on Windows
2003 Enterprise can be run with a non-administrative service account
but I have not been able to get this to work- the SQL installation
fails with "This operation returned because the timeout period expired"
and, while sqlstp.log and sqlstpN.log files look OK, the following
appears in sqlclstr.log:
CreateClusterVirtualSQLSvrGroup2: 1381
[sqlclusterSetup.cpp:2549] : 1460 (0x5b4): This operation returned
because the timeout period expired.
Watching the cluster during the install indicates that it never brings
the SQL Cluster IP address online.
Running the installation in exactly the same way but with the SQL
Server service account in the local administrators group on both nodes
works fine.
My hunch is that this has something to do with registering IP, DNS or
SPN resources in Active Directory but I have found nothing specific in
Technet or in the news groups to back this up.
Has anybody got this to work and can offer me any advice?
Thanks.
I have seen similar error a long time ago. When you get the error, do not press OK. Open SQL Server Errorlog and see the messages in it. That may be helpful.
Also, make sure that you do not have any networking/name resolution issues.
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Thanks for your comments but I eventually cracked it with the help of
this article:
http://www.sqlservercentral.com/colu...intversion.asp
I simply followed the steps in here for assigning file and registry
permissions on both nodes and removed the service account from the
local Adminstrators group when I'd finished. Works a treat.
Note that the service account needs read permissions to the whole of
the drive with the master and TempDB devices not just the folder they
are in and full control on the folders containing the data devices.

Requirements for installing this product on a W2003 server?

I wanted to try a test drive of the product on my new web server, but I get
a warning that it won't install. Warning is worthless because it says that
something isn't present, but fails to mention what that is. No # to cross
reference.
So what do you need to have on a fresh install of W2003 ?
This is a web box only, and my SQL boxes all have no IIS installed.
TIA
__StephenSystem requirements can be found at
http://www.microsoft.com/sql/prodinfo/sysreqs/default.mspx
Hope this helps
--
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
I support the Professional Association for SQL Server ( PASS) and it''s
community of SQL Professionals.
"__Stephen" wrote:
> I wanted to try a test drive of the product on my new web server, but I get
> a warning that it won't install. Warning is worthless because it says that
> something isn't present, but fails to mention what that is. No # to cross
> reference.
> So what do you need to have on a fresh install of W2003 ?
> This is a web box only, and my SQL boxes all have no IIS installed.
> TIA
> __Stephen
>
>

Requirement to use Management Studio

What are the requirements to use Management Studio/Management Studio Express for local instances? Are the requirements same for both studios and same for all OS?

Based on my own testings:
Remote connection is required for Management Studio in Windows XP SP2.
But it is not required in Management Studio Express in Windows XP SP2.

For Windows 2003 and 2000, remote connection is not required for Management Studio. Have not tried Management Studio Express yet.

Peter

This is additional info to clarify the issues:

I'm testing the following in a Windows XP SP2 with SQL Server 2005 Developer Edition SP1:

Scenario #1
1. Checked Local connections only in SSSAC for a SQL Server 2005 local instance
2. Restarted that instance in SSCM (Note: only Shared Memory enabled for Network Configuration)
3. Tried to connect to that instance in SSMS and get this error:

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: SQL Network Interfaces, error: 28 - Server doesn't support requested protocol) (Microsoft SQL Server, Error: -1)

Scenario #2
1. Checked Local and remote connections and Using named pipes only in SSSAC for a SQL Server 2005 local instance
2. Restarted that instance in SSCM (Note: Shared Memory and Named Pipes enabled for Network Configuration)
3. Tried to connect to that instance in SSMS and get this error:

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: SQL Network Interfaces, error: 28 - Server doesn't support requested protocol) (.Net SqlClient Data Provider)

Scenario #3
1. Checked Local and remote connections and Using TCP/IP only in SSSAC for a SQL Server 2005 local instance
2. Restarted that instance in SSCM (Note: Shared Memory and TCP/IP enabled for Network Configuration)
3. Tried to connect to that instance in SSMS and was able to connect
4. The following is fromt the SQL Server Logs:

Server is listening on [ 127.0.0.1 <ipv4> 4906].
Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SQL2005\sql\query ].
Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQL2005].
Server is listening on [ 'any' <ipv4> 2464].

What do the log mean?

Why I cannot connect to the local instance in Scenario #1 and #2?

Thanks for any help,

Peter

|||

SQL Server supports connections using shared memory (which can only work with applications on the same machine), named pipes (an inter-machine communication technology that is mostly used by older applications running on Windows machines - it lets the client communicate with SQL Server as if it were reading or writing to a file), or TCP/IP connections, which can work for any network client on any machine (including, say, Java clients on Unix machines).

In scenario #1 you've disabled remote connections, so only applications running on your server machine can access the server. In #1, you are only allowing connections via shared memory, and in #2 you are allowing shared memory or named pipes connections. It seems likely that in #1 and #2 SSMS is trying to create a TCP/IP connection to your server, but your server isn't accepting those connection types. You can configure how Management Studio connects to your server in the Connection Dialog by clicking the "Options >>" button. In the "Network protocol" dropdown, just pick one of the connection types your server is allowing. In #1, that would be "Shared Memory."

In scenario #3, the log is saying that SQL Server is accepting

TCP/IP connections from the TCP local loopback adapter (the reserved IP address 127.0.0.1, used by network applications to talk to the local machine) on port 4906. If you type "(local)" or "." as the name of the server, SSMS uses 127.0.0.1 as the address of the server.|||

Hi Steve,

Thanks for your post.

I'm not sure what do you mean by "in #2 you are allowing shared memory or named pipes from local clients". If I understand correctly, the #2 scenario is allowing shared memory from local clients and named pipes from remote clients.

If I don't click the Options button in the Connection Dialog, which protocol will be used by default or how can I find out? If I click the Options button in the Connection Dialog and then select <default>, is it same as not clicking the Options button?

Is there any webcast from technet/msdn/microsoft regarding Connection in SQL Server 2005 and/or SQL Server Browser Service?

Peter

|||

You're right, #2 allows remote connections via named pipes. I wasn't reading your description correctly.

<default> means that the connection dialog doesn't specify a network protocol in the connection string used to connect to the server. Under ADO.net 2.0, I believe this results in a TCP/IP connection. If ADO.net changes this default in a future release, <default> would use it. The Options button just exposes additional connection options and doesn't change anything itself, so clicking <default> shouldn't have an effect if that was the setting initially.

I don't know the answer to your question about upcoming webcasts.

Hope this helps,
Steve