New SQL Server 2005 Installation

I have just purchased SQL Server 2005 and a new Dell 2800 server to run it on. I was told by my Dell rep to configure the server with the following drives. 2 - 36GB drives in a RAID 0 (15,000 RPM), 2 - 73GB drives in a RAID 0 (10,000 RPM) and 3 - 146GB drives in a RAID 5 (10,000 RPM). Dell pre-installed the OS on the 36GB drive. I was told to install SQL on the 73GB drives and the data (primarily TIFF images) on the 146GB. The server is a 64bit machine with Windows 2003 Server and 4GB of RAM. I was told to put the transaction logs on a different physical drive that the database to speed the writes. Is this a correct installation? Is there any information on a best practice installation? I have spent about 6 hours on MS and Google trying to find an answer. Thanks for any help you can give. Recap of Dell recommendation:

2 - 36GB Mirrored Drives = OS

2 - 73BG Mirrored Drives = SQL Server 2005

3 - 146GB RAID 5 Drives = Data (Images)

Is this correct?

Where should the Transaction Logs Be?

Because transaction logging is a mostly write operation the most efficient place for them is on a mirrored drive set. I usually install SQL Server executables on the same drive as the operating system. (The network admins here configure 10GB for the OS and SQL Server, and it's always been plenty.) I place the data files on the RAID array, and the transaction logs on the mirrored set. When you're running setup specify the RAID drive for the data and the 36GB mirror set for the program files, then after installation set your default location for the log files to the 73GB mirror set and you should be all set.

New SQL Server 2000 worm?

Hi all.

My SQL Server 2000 SP4 installation running on Windows 2003 server (SP1, all patches current) has been infected TWICE by something that Sophos can't detect.

The symptoms are that an account called SQLsys is created on the machine and is made an administrator.

A service called "ApptoService spoolsrv" is created. An executable called syss.exe is also created in a few places. After infection the machine immediately starts attacking other computers on the network.

I had Windows Firewall running, with ports open for SQL server and Remote Desktop.

I ran the MBSA, it didn't find anything open.

I even ran the beta MS web tool for scanning, didn't detect any trojans.

I'm going to be restoring the machine (AGAIN), but I wish I knew what security hole is being found! Any ideas?
Please try changing your SA account password. Try a complicated password that has numbers, letters, and symbols in it. Also, do not allow your sql server to have inbound access to the internet. At the very least block port 1433 on your firewall.|||

Have you noticed this issue again after setting a strong SA password?

Thanks
Laurentiu

|||Try using Windows Defender beta which is a good one to catchup such trojans & spyware. Also check any spurious activity on SQL server by referring to data & log file usage with an audit trial.sql

New SQL Express Installation

I just installed SQL Express in my workstation but when I try to create and ODBC connection, the new server does not show in the drop down. Do you have any tips...? Thanks.

If you are using down-level clients through MDAC, you'll need to enable TCP/IP in order to connect to SQL Express, even on the local computer. If you're additionally trying to connect from a remote computer, you'll need to consider turning on SQL Browser and open up your Firewall.

Check out http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx for information about this.

Mike

|||

Why ODBC out of curiousity?

Why not connect with ADO 2.8? or ADO.net using the new sql native client?

Provider=SQLNCLI.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=myDatabaseName;Data Source=.\Sqlexpress

|||If the server is not the default instance (if you installed it as named instance) you may have to type in the instance name manually.

New MSDE Installation

What is the proper way to install a new MSDE Installation?
MSDE Release A then SP4
or
Can SP4 be used for a new installation on a PC?
hi,
topherdel wrote:
> What is the proper way to install a new MSDE Installation?
> MSDE Release A then SP4
> or
> Can SP4 be used for a new installation on a PC?
you can go both way... but directly installing sp4 will result in lower
installation time...
just a caveat... at the moment is not clear to me if it's legal for non
entitled persons (people not owing a legal copy of a product entiteling for
MSDE sp4 new installation use) to use sp4 package to directly install new
instances... but it is legal to use that package to upgrade MSDE Rel. A
instances to sp4...
I've been told a refresh of MSDE Rel.A updated at sp4 level will be
available, but no idea for the time frame...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||The rules seem to change with each release as to who can use it and who cannot.
"Andrea Montanari" wrote:

> hi,
> topherdel wrote:
> you can go both way... but directly installing sp4 will result in lower
> installation time...
> just a caveat... at the moment is not clear to me if it's legal for non
> entitled persons (people not owing a legal copy of a product entiteling for
> MSDE sp4 new installation use) to use sp4 package to directly install new
> instances... but it is legal to use that package to upgrade MSDE Rel. A
> instances to sp4...
> I've been told a refresh of MSDE Rel.A updated at sp4 level will be
> available, but no idea for the time frame...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>

new installation question

I've installed MSDE on a W2000 machine and want to set up an ODBC connection to it from an XP machine using an IP address and specifying a port. How do I determine the login and password I need to use to make the connection
Thanks...Hi,
First , you have to enable TCP/IP protocol from MDE server.
From command prompt of server execute (Server Network Utility) :-
svrnetcn.exe
Here, You can enable the TCPIP protocol
By default MSDE only support Windows authentication. So try creating an ODBC
using a Domain id. Ensure that domain user has got access to SQL Server.
By default users of local administrator group will have access. Have a look
into books online for the below procedures to give preevilages:-
1. sp_grantlogin
2. sp_grantdbaccess
Have a look into below link to identify for connectivity issues:-
http://support.microsoft.com/default.aspx?scid=kb;en-us;827422
Thanks
Hari
MCDBA
"Jeff" <jstemper@.wi.rr.com> wrote in message
news:9DFDAD9E-49E7-4A04-8A0F-56BD4821EC36@.microsoft.com...
> I've installed MSDE on a W2000 machine and want to set up an ODBC
connection to it from an XP machine using an IP address and specifying a
port. How do I determine the login and password I need to use to make the
connection?
> Thanks...|||Jeff,
if you are using trusted security, then there won't be a requirement for a
login and password. If you are using SQL Server security, then you just need
to create a SQL Server login on MSDE and incorporate its details in the
connectionstring. I'm guessing here, but it may be that your question is
wider and you want to know generally about administering the MSDE
installation. SQL Server client tools from any other box could be used to
administer it. Just make sure that the box which is using the client tools
uses trusted security, and the windows login on this box is in the local
administrators group on the MSDE machine. To cheaply set this up, you could
use the Developer Edition to get the client tools. Some people talk about
using the Evaluation client tools although the legality of this is dubious -
you'd have to check this out with MS.
HTH,
Paul Ibison|||If you require SQL authentication, you have to specify
following option for setup.exe while installing MSDE.
Setup.exe SECURITYMODE=SQL SAPWD=<password>
Shrikant Patil
MCDBA
>--Original Message--
>I've installed MSDE on a W2000 machine and want to set
up an ODBC connection to it from an XP machine using an
IP address and specifying a port. How do I determine the
login and password I need to use to make the connection?
>Thanks...
>.
>

new installation question

I've installed MSDE on a W2000 machine and want to set up an ODBC connection to it from an XP machine using an IP address and specifying a port. How do I determine the login and password I need to use to make the connection?
Thanks...
Hi,
First , you have to enable TCP/IP protocol from MDE server.
From command prompt of server execute (Server Network Utility) :-
svrnetcn.exe
Here, You can enable the TCPIP protocol
By default MSDE only support Windows authentication. So try creating an ODBC
using a Domain id. Ensure that domain user has got access to SQL Server.
By default users of local administrator group will have access. Have a look
into books online for the below procedures to give preevilages:-
1. sp_grantlogin
2. sp_grantdbaccess
Have a look into below link to identify for connectivity issues:-
http://support.microsoft.com/default...b;en-us;827422
Thanks
Hari
MCDBA
"Jeff" <jstemper@.wi.rr.com> wrote in message
news:9DFDAD9E-49E7-4A04-8A0F-56BD4821EC36@.microsoft.com...
> I've installed MSDE on a W2000 machine and want to set up an ODBC
connection to it from an XP machine using an IP address and specifying a
port. How do I determine the login and password I need to use to make the
connection?
> Thanks...
|||Jeff,
if you are using trusted security, then there won't be a requirement for a
login and password. If you are using SQL Server security, then you just need
to create a SQL Server login on MSDE and incorporate its details in the
connectionstring. I'm guessing here, but it may be that your question is
wider and you want to know generally about administering the MSDE
installation. SQL Server client tools from any other box could be used to
administer it. Just make sure that the box which is using the client tools
uses trusted security, and the windows login on this box is in the local
administrators group on the MSDE machine. To cheaply set this up, you could
use the Developer Edition to get the client tools. Some people talk about
using the Evaluation client tools although the legality of this is dubious -
you'd have to check this out with MS.
HTH,
Paul Ibison

New Installation question

Do or should the client components be installed on the
Server?
If the client components are installed on the server
briefly describe what their purpose would be on the
server if they are also on the developers workstation.Jim,
This is completely up to you. If you're deploying a production box, then
you probably don't want client tools on it. If you're using it as a
development machine, you might.
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jim Abel" <jim.abel@.lmco.com> wrote in message
news:2b9b301c46921$d2c48bf0$a601280a@.phx.gbl...
> Do or should the client components be installed on the
> Server?
> If the client components are installed on the server
> briefly describe what their purpose would be on the
> server if they are also on the developers workstation.

new installation question

I've installed MSDE on a W2000 machine and want to set up an ODBC connection
to it from an XP machine using an IP address and specifying a port. How do
I determine the login and password I need to use to make the connection?
Thanks...Hi,
First , you have to enable TCP/IP protocol from MDE server.
From command prompt of server execute (Server Network Utility) :-
svrnetcn.exe
Here, You can enable the TCPIP protocol
By default MSDE only support Windows authentication. So try creating an ODBC
using a Domain id. Ensure that domain user has got access to SQL Server.
By default users of local administrator group will have access. Have a look
into books online for the below procedures to give preevilages:-
1. sp_grantlogin
2. sp_grantdbaccess
Have a look into below link to identify for connectivity issues:-
http://support.microsoft.com/defaul...kb;en-us;827422
Thanks
Hari
MCDBA
"Jeff" <jstemper@.wi.rr.com> wrote in message
news:9DFDAD9E-49E7-4A04-8A0F-56BD4821EC36@.microsoft.com...
> I've installed MSDE on a W2000 machine and want to set up an ODBC
connection to it from an XP machine using an IP address and specifying a
port. How do I determine the login and password I need to use to make the
connection?
> Thanks...|||Jeff,
if you are using trusted security, then there won't be a requirement for a
login and password. If you are using SQL Server security, then you just need
to create a SQL Server login on MSDE and incorporate its details in the
connectionstring. I'm guessing here, but it may be that your question is
wider and you want to know generally about administering the MSDE
installation. SQL Server client tools from any other box could be used to
administer it. Just make sure that the box which is using the client tools
uses trusted security, and the windows login on this box is in the local
administrators group on the MSDE machine. To cheaply set this up, you could
use the Developer Edition to get the client tools. Some people talk about
using the Evaluation client tools although the legality of this is dubious -
you'd have to check this out with MS.
HTH,
Paul Ibison

New Installation of SQL Server 2000

Hi,
I installed sql server 2000 sp2 standard edition on Windows 2003, when
installing, it said "This version is not support on this os", but I was told
to continue installing the software and that I could install the latest
security patches to bring it up to date. Will that work? Do I need to do
anything else? SQL Server 2000 is up and running on the box. When running
the statement " select @.@.version" it informed me that I was at 8.00.194
patch level. How can I tell if SQL Server 2000 is 32 or 64 bit? I was
trying to download the lasted patch and it asked for that info. Thanks.--
New SQL Server DBA
Newbie wrote:
> Hi,
> I installed sql server 2000 sp2 standard edition on Windows 2003, when
> installing, it said "This version is not support on this os", but I
> was told to continue installing the software and that I could install
> the latest security patches to bring it up to date. Will that work?
> Do I need to do anything else? SQL Server 2000 is up and running on
> the box. When running the statement " select @.@.version" it informed
> me that I was at 8.00.194 patch level. How can I tell if SQL Server
> 2000 is 32 or 64 bit? I was trying to download the lasted patch and
> it asked for that info. Thanks.-- New SQL Server DBA
You didn't install SQL 2000 SP2. You installed SQL 2000 RTM (v194). The
installation program at the point SQL 2000 RTM was released didn't know
about Win2K3 and is giving you the error.
Install SP3a on the server and you should be ready to go.
David Gugick
Imceda Software
www.imceda.com

New Installation of SQL Server 2000

Hi,
I installed sql server 2000 sp2 standard edition on Windows 2003, when
installing, it said "This version is not support on this os", but I was told
to continue installing the software and that I could install the latest
security patches to bring it up to date. Will that work? Do I need to do
anything else? SQL Server 2000 is up and running on the box. When running
the statement " select @.@.version" it informed me that I was at 8.00.194
patch level. How can I tell if SQL Server 2000 is 32 or 64 bit? I was
trying to download the lasted patch and it asked for that info. Thanks.--
New SQL Server DBANewbie wrote:
> Hi,
> I installed sql server 2000 sp2 standard edition on Windows 2003, when
> installing, it said "This version is not support on this os", but I
> was told to continue installing the software and that I could install
> the latest security patches to bring it up to date. Will that work?
> Do I need to do anything else? SQL Server 2000 is up and running on
> the box. When running the statement " select @.@.version" it informed
> me that I was at 8.00.194 patch level. How can I tell if SQL Server
> 2000 is 32 or 64 bit? I was trying to download the lasted patch and
> it asked for that info. Thanks.-- New SQL Server DBA
You didn't install SQL 2000 SP2. You installed SQL 2000 RTM (v194). The
installation program at the point SQL 2000 RTM was released didn't know
about Win2K3 and is giving you the error.
Install SP3a on the server and you should be ready to go.
David Gugick
Imceda Software
www.imceda.com

New Installation of Sql Server 2000

Hello Guru's, I need your help!

I installed sql server 2000 sp2 standard edition on Windows 2003, when
installing, it said "This version is not supported on this os", but I was told
to continue installing the software and that I could install the latest
security patches to bring it up to date. Will that work? Do I need to do
anything else? SQL Server 2000 is up and running on the box. When running
the statement " select @.@.version" it informed me that I was at 8.00.194
patch level. How can I tell if SQL Server 2000 is 32 or 64 bit? I was
trying to download the lasted patch and it asked for that info. Thanks.--
New to SQL ServerUnless you paid over $20,000 for SQL Server, it is probably 32 bit. I think the 64 bit version of SQL server states in @.@.version that it is 64 bit, so if you do not see anything, you very likely have 32 bit.

You need SQL Server SP3 to run on Windows 2003 with no problems. Just download the patch, run it, and you should be all set.|||Thank You Very Much!!! :)

New Installation of SQL Server 2000

Hi,
I installed sql server 2000 sp2 standard edition on Windows 2003, when
installing, it said "This version is not support on this os", but I was told
to continue installing the software and that I could install the latest
security patches to bring it up to date. Will that work? Do I need to do
anything else? SQL Server 2000 is up and running on the box. When running
the statement " select @.@.version" it informed me that I was at 8.00.194
patch level. How can I tell if SQL Server 2000 is 32 or 64 bit? I was
trying to download the lasted patch and it asked for that info. Thanks.--
New SQL Server DBANewbie wrote:
> Hi,
> I installed sql server 2000 sp2 standard edition on Windows 2003, when
> installing, it said "This version is not support on this os", but I
> was told to continue installing the software and that I could install
> the latest security patches to bring it up to date. Will that work?
> Do I need to do anything else? SQL Server 2000 is up and running on
> the box. When running the statement " select @.@.version" it informed
> me that I was at 8.00.194 patch level. How can I tell if SQL Server
> 2000 is 32 or 64 bit? I was trying to download the lasted patch and
> it asked for that info. Thanks.-- New SQL Server DBA
You didn't install SQL 2000 SP2. You installed SQL 2000 RTM (v194). The
installation program at the point SQL 2000 RTM was released didn't know
about Win2K3 and is giving you the error.
Install SP3a on the server and you should be ready to go.
David Gugick
Imceda Software
www.imceda.com

New installation https issue

Hello,

I had some problems with an upgrade that added in RS to a default upgrade of sql2k to sql2k5. I then went into RS configuration and recreated everything. I am now able to get onto the site with no problems except when I have it checked to require ssl connections. I get the follow message when I have ssl checked using any of the three options "The request failed with HTTP status 401: Unauthorized." The certificate matches the url I am trying to goto: reports.domain.net. If in iis on the default website I force a redirect to https://reports.domain.net /reports it works fine, but it's not enforceing ssl if a user just types in the url http://reports.domain.net.reports. How can I get it to enforce ssl throughout via the RS configuration? Thanks.

John

John,

We are having the exact same issue. Did you ever resolve this?

Tom

New installation https issue

Hello,

I had some problems with an upgrade that added in RS to a default upgrade of sql2k to sql2k5. I then went into RS configuration and recreated everything. I am now able to get onto the site with no problems except when I have it checked to require ssl connections. I get the follow message when I have ssl checked using any of the three options "The request failed with HTTP status 401: Unauthorized." The certificate matches the url I am trying to goto: reports.domain.net. If in iis on the default website I force a redirect to https://reports.domain.net /reports it works fine, but it's not enforceing ssl if a user just types in the url http://reports.domain.net.reports. How can I get it to enforce ssl throughout via the RS configuration? Thanks.

John

John,

We are having the exact same issue. Did you ever resolve this?

Tom

New Installation Error

Hello all.
After suffering a complete RAID failure, I am now tasked with the
responsibility of setting up reporting services again, on a new and
different machine. I had been successful getting it running last time,
so I figured this wouldn't be too much problem. The installation goes
fine, until the end, when it reports that the service wont start for
the first time.
As for information. Server2003-sp1. For the ReportServer Windows
service I'm using account (NT AUTHORITY\NETWORK SERVICE). I've left
virtual directories the same, except that I've disabled SSL
connections. The Database is running locally, and for the runtime
connection credentials, I've chosen to use a Domain User Account (set
up especially for this purpose) "RSExec".
As I said, the install goes fine, but fails. The only thing I can
think of is that maybe my new RSExec user needs more permission than a
standard user. But I've read the books (Lachev, and Blackburn &
Vaughn), as well as the BOL, and I can't find any indication of what I
might be missing.
Opening the //machine/ReportServer page, I get the following error
message:
* The report server cannot open a connection to the report server
database. The logon failed. (rsReportServerDatabaseLogonFailed) Get
Online Help
o Logon failure: the user has not been granted the requested logon
type at this computer.
The error message from the log shows:
w3wp!ui!dc0!9/27/2005-08:25:37:: e ERROR:
System.Web.Services.Protocols.SoapException: The report server cannot
open a connection to the report server database. The logon failed. -->
Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseLogonFailedException:
The report server cannot open a connection to the report server
database. The logon failed. -->
System.Runtime.InteropServices.COMException (0x80070569): Logon
failure: the user has not been granted the requested logon type at this
computer.
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
errorCode, IntPtr errorInfo)
at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pUserName,
String pDomain, String pPassword, Boolean bTryRemote, IntPtr&
pImpToken)
at
Microsoft.ReportingServices.Library.ConnectionManager.GetImpersonationToken(String
userName, String domain, String userPwd)
-- End of inner exception stack trace --
Thanks for all your help. It is sincerely appreciated.
Brian AckermannDid you grant RSExec permissions to logon to SQL server? If so, can you
check to see if the user has permission to the RS database?
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Brian Ackermann" <brian.ackermann@.gmail.com> wrote in message
news:1127830923.220944.153010@.g44g2000cwa.googlegroups.com...
> Hello all.
> After suffering a complete RAID failure, I am now tasked with the
> responsibility of setting up reporting services again, on a new and
> different machine. I had been successful getting it running last time,
> so I figured this wouldn't be too much problem. The installation goes
> fine, until the end, when it reports that the service wont start for
> the first time.
> As for information. Server2003-sp1. For the ReportServer Windows
> service I'm using account (NT AUTHORITY\NETWORK SERVICE). I've left
> virtual directories the same, except that I've disabled SSL
> connections. The Database is running locally, and for the runtime
> connection credentials, I've chosen to use a Domain User Account (set
> up especially for this purpose) "RSExec".
> As I said, the install goes fine, but fails. The only thing I can
> think of is that maybe my new RSExec user needs more permission than a
> standard user. But I've read the books (Lachev, and Blackburn &
> Vaughn), as well as the BOL, and I can't find any indication of what I
> might be missing.
> Opening the //machine/ReportServer page, I get the following error
> message:
> * The report server cannot open a connection to the report server
> database. The logon failed. (rsReportServerDatabaseLogonFailed) Get
> Online Help
> o Logon failure: the user has not been granted the requested logon
> type at this computer.
> The error message from the log shows:
> w3wp!ui!dc0!9/27/2005-08:25:37:: e ERROR:
> System.Web.Services.Protocols.SoapException: The report server cannot
> open a connection to the report server database. The logon failed. -->
> Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseLogonFailedException:
> The report server cannot open a connection to the report server
> database. The logon failed. -->
> System.Runtime.InteropServices.COMException (0x80070569): Logon
> failure: the user has not been granted the requested logon type at this
> computer.
> at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
> errorCode, IntPtr errorInfo)
> at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pUserName,
> String pDomain, String pPassword, Boolean bTryRemote, IntPtr&
> pImpToken)
> at
> Microsoft.ReportingServices.Library.ConnectionManager.GetImpersonationToken(String
> userName, String domain, String userPwd)
> -- End of inner exception stack trace --
> Thanks for all your help. It is sincerely appreciated.
> Brian Ackermann
>|||Daniel,
Thanks for the reply.
As far as I can tell, the installer gives the RSExec user permissions
on the database. I must be missing it if there was something else.
There was a user called RSExec intalled on the database, with what
appeared to be appropriate values.
Can you be more explicit as to what settings exactly need to be set.
I'm sure its quite simple, and that I'm just not seeing it.
Thanks
Brian Ackermann|||From the look of the call stack, it appears that you are using a domain
account to talk to the RS database server. It doesn't appear that user has
permission to logon to the RS box. You should verify if that is the case.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Brian Ackermann" <brian.ackermann@.gmail.com> wrote in message
news:1127939219.565435.135110@.o13g2000cwo.googlegroups.com...
> Daniel,
> Thanks for the reply.
> As far as I can tell, the installer gives the RSExec user permissions
> on the database. I must be missing it if there was something else.
> There was a user called RSExec intalled on the database, with what
> appeared to be appropriate values.
> Can you be more explicit as to what settings exactly need to be set.
> I'm sure its quite simple, and that I'm just not seeing it.
> Thanks
> Brian Ackermann
>

New Installation can't connect to default database

I installed SQL Server 2005. Connected to an external dB on a different
server just fine. Now am trying to connect (via SQL Server Management Studio
)
to the default local dB. I get the following error:
Cannot connect to <server name in here>
A connection was successfully established with the server, but then an error
occurred during the login process (provider shared memory provider error 0 -
no process is on the other end of the pipe). Microsoft SQL Server error 23
3.
any ideas what's wrong?Run the SQL Server Configuration Manager and click on the Protocols for that
instance. Check to make sure that you enable Shared Memory.
Andrew J. Kelly SQL MVP
"ChristieD" <ChristieD@.discussions.microsoft.com> wrote in message
news:5298A83E-8980-46E7-BC6F-DB283673B3E0@.microsoft.com...
>I installed SQL Server 2005. Connected to an external dB on a different
> server just fine. Now am trying to connect (via SQL Server Management
> Studio)
> to the default local dB. I get the following error:
> Cannot connect to <server name in here>
> A connection was successfully established with the server, but then an
> error
> occurred during the login process (provider shared memory provider error
> 0 -
> no process is on the other end of the pipe). Microsoft SQL Server error
> 233.
> any ideas what's wrong?|||Shared memory is enabled as is TCP/IP. Shared Pipes was not, and I enabled
that. VIA remains disabled. I can't start the SQL Serveer Agent, either. It
is set to Manual and if I try to start it, I get a message that it started
and stopped again.
"Andrew J. Kelly" wrote:

> Run the SQL Server Configuration Manager and click on the Protocols for th
at
> instance. Check to make sure that you enable Shared Memory.
> --
> Andrew J. Kelly SQL MVP
>
> "ChristieD" <ChristieD@.discussions.microsoft.com> wrote in message
> news:5298A83E-8980-46E7-BC6F-DB283673B3E0@.microsoft.com...
>
>|||What do the error and Agent logs say?
Andrew J. Kelly SQL MVP
"ChristieD" <ChristieD@.discussions.microsoft.com> wrote in message
news:4C86F2E6-A2CF-486B-8967-873B8A2D7F1B@.microsoft.com...[vbcol=seagreen]
> Shared memory is enabled as is TCP/IP. Shared Pipes was not, and I enabled
> that. VIA remains disabled. I can't start the SQL Serveer Agent, either.
> It
> is set to Manual and if I try to start it, I get a message that it started
> and stopped again.
> "Andrew J. Kelly" wrote:
>|||There was an application event (MSSQLSERVER) that said that the max number o
f
2 user connections had been reached and the connection was closed
"Andrew J. Kelly" wrote:

> What do the error and Agent logs say?
> --
> Andrew J. Kelly SQL MVP
>
> "ChristieD" <ChristieD@.discussions.microsoft.com> wrote in message
> news:4C86F2E6-A2CF-486B-8967-873B8A2D7F1B@.microsoft.com...
>
>|||I re-installed SQL and opened the default db first and now it seems to be
working. Very weird.
"Andrew J. Kelly" wrote:

> What do the error and Agent logs say?
> --
> Andrew J. Kelly SQL MVP
>
> "ChristieD" <ChristieD@.discussions.microsoft.com> wrote in message
> news:4C86F2E6-A2CF-486B-8967-873B8A2D7F1B@.microsoft.com...
>
>

New Installation can't connect to default database

I installed SQL Server 2005. Connected to an external dB on a different
server just fine. Now am trying to connect (via SQL Server Management Studio)
to the default local dB. I get the following error:
Cannot connect to <server name in here>
A connection was successfully established with the server, but then an error
occurred during the login process (provider shared memory provider error 0 -
no process is on the other end of the pipe). Microsoft SQL Server error 233.
any ideas what's wrong?
Run the SQL Server Configuration Manager and click on the Protocols for that
instance. Check to make sure that you enable Shared Memory.
Andrew J. Kelly SQL MVP
"ChristieD" <ChristieD@.discussions.microsoft.com> wrote in message
news:5298A83E-8980-46E7-BC6F-DB283673B3E0@.microsoft.com...
>I installed SQL Server 2005. Connected to an external dB on a different
> server just fine. Now am trying to connect (via SQL Server Management
> Studio)
> to the default local dB. I get the following error:
> Cannot connect to <server name in here>
> A connection was successfully established with the server, but then an
> error
> occurred during the login process (provider shared memory provider error
> 0 -
> no process is on the other end of the pipe). Microsoft SQL Server error
> 233.
> any ideas what's wrong?
|||Shared memory is enabled as is TCP/IP. Shared Pipes was not, and I enabled
that. VIA remains disabled. I can't start the SQL Serveer Agent, either. It
is set to Manual and if I try to start it, I get a message that it started
and stopped again.
"Andrew J. Kelly" wrote:

> Run the SQL Server Configuration Manager and click on the Protocols for that
> instance. Check to make sure that you enable Shared Memory.
> --
> Andrew J. Kelly SQL MVP
>
> "ChristieD" <ChristieD@.discussions.microsoft.com> wrote in message
> news:5298A83E-8980-46E7-BC6F-DB283673B3E0@.microsoft.com...
>
>
|||What do the error and Agent logs say?
Andrew J. Kelly SQL MVP
"ChristieD" <ChristieD@.discussions.microsoft.com> wrote in message
news:4C86F2E6-A2CF-486B-8967-873B8A2D7F1B@.microsoft.com...[vbcol=seagreen]
> Shared memory is enabled as is TCP/IP. Shared Pipes was not, and I enabled
> that. VIA remains disabled. I can't start the SQL Serveer Agent, either.
> It
> is set to Manual and if I try to start it, I get a message that it started
> and stopped again.
> "Andrew J. Kelly" wrote:
|||There was an application event (MSSQLSERVER) that said that the max number of
2 user connections had been reached and the connection was closed
"Andrew J. Kelly" wrote:

> What do the error and Agent logs say?
> --
> Andrew J. Kelly SQL MVP
>
> "ChristieD" <ChristieD@.discussions.microsoft.com> wrote in message
> news:4C86F2E6-A2CF-486B-8967-873B8A2D7F1B@.microsoft.com...
>
>
|||I re-installed SQL and opened the default db first and now it seems to be
working. Very weird.
"Andrew J. Kelly" wrote:

> What do the error and Agent logs say?
> --
> Andrew J. Kelly SQL MVP
>
> "ChristieD" <ChristieD@.discussions.microsoft.com> wrote in message
> news:4C86F2E6-A2CF-486B-8967-873B8A2D7F1B@.microsoft.com...
>
>

New installation - Catalog does not get popuated

I am tearing my hair out here!
I have set up a full text catlog on an SQL 2000 Server ( Microsoft SQL
Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05 ), and everything
seemed to go fine until I tried to populate it. It seems to get stuck in
populate mode, and the only errors that I can see are in the event log as
below.
I have looked at various postings on the subject, and the only one that I
can see is relevant is the one about SQL server running under a different
account to the LocalSystem, which it was. I corrected this via Enterprise
manager, re-started SQL Server, then re-started Microsoft Search/Full-text
Search, but still it does not populate!
The event log errors are:
One or more warnings or errors for Gatherer project <SQLServer
SQL0001800005> were logged to file <C:\Program Files\Microsoft SQL
Server\MSSQL\FTData\SQLServer\GatherLogs\SQL000180 0005.1.gthr>. If you are
interested in these messages, please, look at the file using the gatherer log
query object (gthrlog.vbs, log viewer web page).
Followed by:
The crawl seed <MSSQL75://SQLServer/64d0200a> in project <SQLServer
SQL0001800005> cannot be accessed. Error: 800700e9 - No process is on the
other end of the pipe. .
Any ideas?
Cheers, Mike.
SQL FTS uses named pipes to communicate with MSSearch.
The error message you are getting is most often related to security, such as
changing the SQL Server service account through control panel rather than
Enterprise Manager.
Can you confirm, that 1) a stopping and starting of MSSearch, SQL Server,
and even a reboot does not solve this problem. I can be resource related. 2)
secondly verify that the BuiltIn Administrators group is in your security
folder and is a system administrator.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Mike Owen" <MikeOwen@.discussions.microsoft.com> wrote in message
news:F1FF6F58-C7D3-4DC8-913B-9EB244CE6B5F@.microsoft.com...
> I am tearing my hair out here!
> I have set up a full text catlog on an SQL 2000 Server ( Microsoft SQL
> Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05 ), and
everything
> seemed to go fine until I tried to populate it. It seems to get stuck in
> populate mode, and the only errors that I can see are in the event log as
> below.
> I have looked at various postings on the subject, and the only one that I
> can see is relevant is the one about SQL server running under a different
> account to the LocalSystem, which it was. I corrected this via Enterprise
> manager, re-started SQL Server, then re-started Microsoft Search/Full-text
> Search, but still it does not populate!
> The event log errors are:
> One or more warnings or errors for Gatherer project <SQLServer
> SQL0001800005> were logged to file <C:\Program Files\Microsoft SQL
> Server\MSSQL\FTData\SQLServer\GatherLogs\SQL000180 0005.1.gthr>. If you are
> interested in these messages, please, look at the file using the gatherer
log
> query object (gthrlog.vbs, log viewer web page).
> Followed by:
> The crawl seed <MSSQL75://SQLServer/64d0200a> in project <SQLServer
> SQL0001800005> cannot be accessed. Error: 800700e9 - No process is on the
> other end of the pipe. .
> Any ideas?
>
> Cheers, Mike.
|||Mike,
Yes, I have an idea and thank you for providing the version (@.@.select) and
eventlog error as they are both very helpful info in troubleshooting SQL FTS
issues!
The primary error is "800700e9 - No process is on the other end of the
pipe.". This error is often caused by removing or altering the SQL Server
login BUILTIN\Administrators and it most likely is the source of this
problem for you. This most likely is the source of the failure for FT
Populations as the MSSearch service needs this login to log into SQL Server
and you can either add back this login with the original permissions
(default master db, sysadmin privileges or see KB article:
263712 (Q263712) INF: How to Impede Windows NT Administrators from
Administering a Clustered SQL Server at:
http://support.microsoft.com/default...B;EN-US;263712
If you cannot add back the SQL Server login BUILTIN\Administrators login,
you can use the following SQL code as a substitute:
exec sp_grantlogin N'NT Authority\System'
exec sp_defaultdb N'NT Authority\System', N'master'
exec sp_defaultlanguage N'NT Authority\System','us_english'
exec sp_addsrvrolemember N'NT Authority\System', sysadmin
Regards,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Mike Owen" <MikeOwen@.discussions.microsoft.com> wrote in message
news:F1FF6F58-C7D3-4DC8-913B-9EB244CE6B5F@.microsoft.com...
> I am tearing my hair out here!
> I have set up a full text catlog on an SQL 2000 Server ( Microsoft SQL
> Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05 ), and
everything
> seemed to go fine until I tried to populate it. It seems to get stuck in
> populate mode, and the only errors that I can see are in the event log as
> below.
> I have looked at various postings on the subject, and the only one that I
> can see is relevant is the one about SQL server running under a different
> account to the LocalSystem, which it was. I corrected this via Enterprise
> manager, re-started SQL Server, then re-started Microsoft Search/Full-text
> Search, but still it does not populate!
> The event log errors are:
> One or more warnings or errors for Gatherer project <SQLServer
> SQL0001800005> were logged to file <C:\Program Files\Microsoft SQL
> Server\MSSQL\FTData\SQLServer\GatherLogs\SQL000180 0005.1.gthr>. If you are
> interested in these messages, please, look at the file using the gatherer
log
> query object (gthrlog.vbs, log viewer web page).
> Followed by:
> The crawl seed <MSSQL75://SQLServer/64d0200a> in project <SQLServer
> SQL0001800005> cannot be accessed. Error: 800700e9 - No process is on the
> other end of the pipe. .
> Any ideas?
>
> Cheers, Mike.
|||Thanks Hilary, I had previously checked to see what permissions the
BUILTIN\Administrators user(s) had on all the DB's, which was db_owner, but I
didn't check it's 'Server Roles' - It had no server roles, and as soon as I
gave it System Administrators Role eveything started working!
Thanks for your help, Mike.
"Hilary Cotter" wrote:

> SQL FTS uses named pipes to communicate with MSSearch.
> The error message you are getting is most often related to security, such as
> changing the SQL Server service account through control panel rather than
> Enterprise Manager.
> Can you confirm, that 1) a stopping and starting of MSSearch, SQL Server,
> and even a reboot does not solve this problem. I can be resource related. 2)
> secondly verify that the BuiltIn Administrators group is in your security
> folder and is a system administrator.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Mike Owen" <MikeOwen@.discussions.microsoft.com> wrote in message
> news:F1FF6F58-C7D3-4DC8-913B-9EB244CE6B5F@.microsoft.com...
> everything
> log
>
>
|||Thanks for replying John.
I worked through Hilary's answer first (as it was posted first), which I
think was similar to yours, and added BUILTIN\Administrators to the 'System
Administrators' Role, and it all started working.
Cheers, Mike.
"John Kane" wrote:

> Mike,
> Yes, I have an idea and thank you for providing the version (@.@.select) and
> eventlog error as they are both very helpful info in troubleshooting SQL FTS
> issues!
> The primary error is "800700e9 - No process is on the other end of the
> pipe.". This error is often caused by removing or altering the SQL Server
> login BUILTIN\Administrators and it most likely is the source of this
> problem for you. This most likely is the source of the failure for FT
> Populations as the MSSearch service needs this login to log into SQL Server
> and you can either add back this login with the original permissions
> (default master db, sysadmin privileges or see KB article:
> 263712 (Q263712) INF: How to Impede Windows NT Administrators from
> Administering a Clustered SQL Server at:
> http://support.microsoft.com/default...B;EN-US;263712
> If you cannot add back the SQL Server login BUILTIN\Administrators login,
> you can use the following SQL code as a substitute:
> exec sp_grantlogin N'NT Authority\System'
> exec sp_defaultdb N'NT Authority\System', N'master'
> exec sp_defaultlanguage N'NT Authority\System','us_english'
> exec sp_addsrvrolemember N'NT Authority\System', sysadmin
> Regards,
> John
> --
> SQL Full Text Search Blog
> http://spaces.msn.com/members/jtkane/
>
> "Mike Owen" <MikeOwen@.discussions.microsoft.com> wrote in message
> news:F1FF6F58-C7D3-4DC8-913B-9EB244CE6B5F@.microsoft.com...
> everything
> log
>
>

New Installation - Can Not Connet to Server On My PC

I have just installed SQL Express and Server Management Studio on my PC. I also have IIS 5.0 on WinXP. When I open Management Studio and try to connect the sI get the following error message:- Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection. (.Net SqlClient Data Provider) .

This happens if I change the server, change the authentication method or try my user name or the 'sa ' user. To make things even more frustrating I did the same installation on my laptop earlier this year with no problems.

Has anyone any answers to my problem?

Thanks

hi,

having modified the authentication property (and restarted the service), did you enable the sa login?.. verify in the Instance->Security->Logins->sa Properties (Status tab) the login is enabled..

regards

New Installation

Windows 2003 Advanced Server
SQL Server 2K sp3a
There was an existing reporting services database on the SQL Server
Instance. Tried to perform an new install of Reporting Services and point to
this existing database, ReportServer DB. Installation was successful.
However, RS would not activate becuase it thought I was adding to a WEB Farm.
To acivate I needed to run rsactivate from the active RS Server, there was
none. Decided to remove the databases and RS and start clean. Now, everytime
I try to install RS its trying to point to a database that does not exist and
the installation fails. Can anyone help?
ThanksWhat do you mean it tries to point to a DB that doesn't exist? During setup
you can specify a DB that does not exist, it should then create that DB.
What error are you getting?
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"FredG" <FredG@.discussions.microsoft.com> wrote in message
news:4C8C08D6-59AE-4F08-8EF4-B9D64C7B9A58@.microsoft.com...
> Windows 2003 Advanced Server
> SQL Server 2K sp3a
> There was an existing reporting services database on the SQL Server
> Instance. Tried to perform an new install of Reporting Services and point
> to
> this existing database, ReportServer DB. Installation was successful.
> However, RS would not activate becuase it thought I was adding to a WEB
> Farm.
> To acivate I needed to run rsactivate from the active RS Server, there was
> none. Decided to remove the databases and RS and start clean. Now,
> everytime
> I try to install RS its trying to point to a database that does not exist
> and
> the installation fails. Can anyone help?
> Thanks|||I know its suppose to create the database if it does not exist. The error is
"Database ReportServer does not exist".
"Daniel Reib [MSFT]" wrote:
> What do you mean it tries to point to a DB that doesn't exist? During setup
> you can specify a DB that does not exist, it should then create that DB.
> What error are you getting?
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "FredG" <FredG@.discussions.microsoft.com> wrote in message
> news:4C8C08D6-59AE-4F08-8EF4-B9D64C7B9A58@.microsoft.com...
> > Windows 2003 Advanced Server
> > SQL Server 2K sp3a
> >
> > There was an existing reporting services database on the SQL Server
> > Instance. Tried to perform an new install of Reporting Services and point
> > to
> > this existing database, ReportServer DB. Installation was successful.
> > However, RS would not activate becuase it thought I was adding to a WEB
> > Farm.
> > To acivate I needed to run rsactivate from the active RS Server, there was
> > none. Decided to remove the databases and RS and start clean. Now,
> > everytime
> > I try to install RS its trying to point to a database that does not exist
> > and
> > the installation fails. Can anyone help?
> >
> > Thanks
>
>|||At what point in setup do you get this? Have you tried changing the DB
name?
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"FredG" <FredG@.discussions.microsoft.com> wrote in message
news:A8598F84-FDBF-49E5-BB2B-24CFA774A7C7@.microsoft.com...
>I know its suppose to create the database if it does not exist. The error
>is
> "Database ReportServer does not exist".
> "Daniel Reib [MSFT]" wrote:
>> What do you mean it tries to point to a DB that doesn't exist? During
>> setup
>> you can specify a DB that does not exist, it should then create that DB.
>> What error are you getting?
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "FredG" <FredG@.discussions.microsoft.com> wrote in message
>> news:4C8C08D6-59AE-4F08-8EF4-B9D64C7B9A58@.microsoft.com...
>> > Windows 2003 Advanced Server
>> > SQL Server 2K sp3a
>> >
>> > There was an existing reporting services database on the SQL Server
>> > Instance. Tried to perform an new install of Reporting Services and
>> > point
>> > to
>> > this existing database, ReportServer DB. Installation was successful.
>> > However, RS would not activate becuase it thought I was adding to a WEB
>> > Farm.
>> > To acivate I needed to run rsactivate from the active RS Server, there
>> > was
>> > none. Decided to remove the databases and RS and start clean. Now,
>> > everytime
>> > I try to install RS its trying to point to a database that does not
>> > exist
>> > and
>> > the installation fails. Can anyone help?
>> >
>> > Thanks
>>|||Hello Daniel,
After I have completed all the setup questions then selected next. The
installation was running fine then it bombed out with that message. I was
able to track down the log file located in the C:\Progam Files\Microsoft SQL
Server\80\RS Setup Bootstrap\Log directory. I noticed that the account RS
setup was trying to use to create the database was DOMAIN\SERVER_NAME$, (I
believe this occured becuase I was running the Windows service under NT
AUTHORITY\NETWORK SERVICE). Once I added this account to SQL server and
granted CREATE DATABASE it worked fine. I have done other installs of RS and
never ran into this problem.
Thanks
"Daniel Reib [MSFT]" wrote:
> At what point in setup do you get this? Have you tried changing the DB
> name?
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "FredG" <FredG@.discussions.microsoft.com> wrote in message
> news:A8598F84-FDBF-49E5-BB2B-24CFA774A7C7@.microsoft.com...
> >I know its suppose to create the database if it does not exist. The error
> >is
> > "Database ReportServer does not exist".
> >
> > "Daniel Reib [MSFT]" wrote:
> >
> >> What do you mean it tries to point to a DB that doesn't exist? During
> >> setup
> >> you can specify a DB that does not exist, it should then create that DB.
> >> What error are you getting?
> >>
> >> --
> >> -Daniel
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >>
> >> "FredG" <FredG@.discussions.microsoft.com> wrote in message
> >> news:4C8C08D6-59AE-4F08-8EF4-B9D64C7B9A58@.microsoft.com...
> >> > Windows 2003 Advanced Server
> >> > SQL Server 2K sp3a
> >> >
> >> > There was an existing reporting services database on the SQL Server
> >> > Instance. Tried to perform an new install of Reporting Services and
> >> > point
> >> > to
> >> > this existing database, ReportServer DB. Installation was successful.
> >> > However, RS would not activate becuase it thought I was adding to a WEB
> >> > Farm.
> >> > To acivate I needed to run rsactivate from the active RS Server, there
> >> > was
> >> > none. Decided to remove the databases and RS and start clean. Now,
> >> > everytime
> >> > I try to install RS its trying to point to a database that does not
> >> > exist
> >> > and
> >> > the installation fails. Can anyone help?
> >> >
> >> > Thanks
> >>
> >>
> >>
>
>