Connot create default directory?

I went ahead and installed RS even though it was clear Microsoft install was confused (re: preivous post). Now I get to experience the thrill of configuration hell.

Report Server Virtual Directory had a green check. Unfortunately the Name block says <Not Set>. When I try to create a New... default directory I get the error message: "The virtual directory could not be created. The previously set virtual directory will still be used."

Does anyone know where the <Not Set> virtual directory is stored on the computer?

addl info:

ReportServicesConfigUI.WMIProvider.WMIProviderException: The virtual directory specified already exists. Specify a different name.

at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.CreateVirtualDirectory(String virtualDirectory, String path)

(Vista Ultimate)

AND when I try to browse to the default directory it did let me create (ReportServerDir), of course I get 404.0 error - Not Found

Connectivity with a SQL instance.

Hi,
I installed on a failover cluster, one default virtual sql
server installation named SERVER1 and a other one
installation of virtual server with instance name called
server2\ufa.
When I try to connect true a firewall on SERVER1 with an
UDL file the connection is OK, but When I'm trying the
same test on SERVER2\ufa I've got this error :
[DBNETLIB][ConnectionOpen (Invalid Instance()).]
When I pinging SERVER1 it's OK, When I trying a telnet
command on IP adresse 1433 it's also OK
But on virtual SERVER2 the port 1433 is on the name
SERVER2 so when I try a command telnet SERVER2 1433 it's
OK but SERVER2\UFA is not recognize.
On the firewall the port 1433 is open for Both IP adresses
and we openned also the ports 139 and 445 for the Netbios.
( Name Pipes )
Someone can help me ?You probably need to open up port 1434 or better yet, open the Server
Network Utility on SERVER2 and set the port explicity to something other
than 1433 or 1434, then connect using the port number rather than the
instance name. This is well documented in Books on Line under firewalls.
"Pierre" <anonymous@.discussions.microsoft.com> wrote in message
news:bfde01c4086c$a9472a00$a501280a@.phx.gbl...
> Hi,
> I installed on a failover cluster, one default virtual sql
> server installation named SERVER1 and a other one
> installation of virtual server with instance name called
> server2\ufa.
> When I try to connect true a firewall on SERVER1 with an
> UDL file the connection is OK, but When I'm trying the
> same test on SERVER2\ufa I've got this error :
> [DBNETLIB][ConnectionOpen (Invalid Instance()).]
> When I pinging SERVER1 it's OK, When I trying a telnet
> command on IP adresse 1433 it's also OK
> But on virtual SERVER2 the port 1433 is on the name
> SERVER2 so when I try a command telnet SERVER2 1433 it's
> OK but SERVER2\UFA is not recognize.
> On the firewall the port 1433 is open for Both IP adresses
> and we openned also the ports 139 and 445 for the Netbios.
> ( Name Pipes )
> Someone can help me ?
>|||To be able to connect to a named instance, (both clustered and stand alone)
1) If the client has MDAC 2.5 or lower, then you have to specify the port
number when connecting and make sure this port is open at the firewall.
2)If the client has MDAC 2.6 or higher, then specify the port number when
connecting or make sure UDP port 1434 is open at the firewall (This is true
even if the named instance is listening on port 1433)
The following articles maybe helpful.
286303 INF: Behavior of SQL Server 2000 Network Library During Dynamic Port
http://support.microsoft.com/?id=286303
287932 INF: TCP Ports Needed for Communication to SQL Server Through a
Firewall
http://support.microsoft.com/?id=287932
286303 INF: Behavior of SQL Server 2000 Network Library During Dynamic Port
http://support.microsoft.com/?id=286303
265808 INF: How to Connect to an SQL Server 2000 Named Instance with the
http://support.microsoft.com/?id=265808
Thanks
Deepali
This posting is provided "AS IS" with no warranties, and confers no rights

Connectivity to FoxPro (dbf) from SQL 2005 on x64 Windows 2003

I have installed SQL Sever 2005 on an x64 bit machine running Windows 2003.
When I go to the ODBC Data Source Administrator, and click on the Drivers
tab, it only shows:
SQL Native Client
SQL Server
I would like it to show the "other" drivers that I see in other
installations - to connect to .mdb, .dbf, etc.
I tried installing MDAC 2.8, but it didn't affect the drivers shown in the
list.
Any suggestions? My goal is to write a SSIS package that connects to a
FoxPro (.dbf) file.
Thanks
PaulHi Paul,
There are two methods for connecting to Fox tables - OLE DB and ODBC. The
OLE DB data provider for VFP is only 32-bit compatible. There are no plans
to develop a 64-bit OLE DB data provider for VFP. I assume that the ODBC
drivers for VFP are also only 32-bit compatible (I'm not sure) but I am sure
that there won't be any new ODBC drivers for VFP.
Sorry to be the bearer of bad news.
Cindy Winegarden MCSD, Microsoft Most Valuable Professional
cindy@.cindywinegarden.com
"Paul in Denver" <Paul in Denver@.discussions.microsoft.com> wrote in message
news:F0E93714-1075-446D-AEF9-48D70D0834E1@.microsoft.com...
>I have installed SQL Sever 2005 on an x64 bit machine ...

> Any suggestions? My goal is to write a SSIS package that connects to a
> FoxPro (.dbf) file.

Connectivity issue with SQL 2005 Developer Edition Named Instance

Hi,

I have installed one default and one named instance of SQL Server 2005 Dev. Editition SP2 on my server.

The Named service is configured to use Shared, NamedPipe and TCP (Port 4333).

There is no firewall on the machine. But still i am not able to connect to it form remote computer.

can any one help me with these. this is urgent.

Thanks.

KV

I found it. My SQL Browser service was running under domain account which was not working, i have configured it to run under NetworkService and it has started. sqlsql

Connectivity issue - SQLServer not listening on port 1433/ms-sql-s

Hi. I'm a SQL Server novice, so apologies if any of this sounds simple.

I am running Windows XP SP2, and have just installed SQLServer 2000. I
need another application to connect to SQLServer, and am specifying it
to do so via localhost:1433, but keep getting an error whenever I try
doing so saying it cannot connect to the database. A colleague of mine
has the exact same set up on his machine, and he can connect to SQL
Server fine. Running 'netstat -a' at the command line on his machine
reveals that the system is listening to port 1433/ms-sql-s. Running
netstat on my machine shows that the system is not listening to
1433/ms-sql-ms. I have checked in Network Config in SQLServer
Enterprise Manager, and TCP/IP is set to be using 1433.

To confirm this, my application can connect over the network to my
colleague's SQL Server. but he cannot connect over the network to mine.

So I'm pretty sure the issue is related to this 1433/ms-sql-s problem.
Does anyone know how to resolve this? Many thanks.I just installed SQL Server Service Pack 3, and the problem is now
resolved. Perhaps it was related to the Slammer worm.

connectivity in sql server with two diff public ip address

I 've two machines (Linux Servers) with firewall installed at two
geographical locations. Now I want to make replication of data using
sqlserver2000 from two other machines which are behind the two servers . Both
of them have have private IP address and they can access the internet
through the firewall . Now I have enabled the ports 1433 on both sides and
had given the IP address of the receiving machine at the sending machine
(Public IP at the network client -alias TCP/IP protocal) and vice versa.
Proper mapping of IP (public to private is done ) at the two servers.
But still I 'm getting the message, Failed to register the Sql Server
Pl help
Soumen,
you'll need to register an alias. Have a look at this article:
http://support.microsoft.com/?id=321822
(these may also be of interest
http://www.microsoft.com/resources/d...rt5/sqc07.mspx
http://support.microsoft.com/default...32&Product=sql)
HTH,
Paul Ibison
|||Did you define these two servers using Client Network Utiltity?
If you did, you can then create ODBC DSN's to them and test general
connectivity, or merely register these SQL Server as enabled Subscribers, or
register them in EM.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Soumen ( India)" <SoumenIndia@.discussions.microsoft.com> wrote in message
news:57461CAD-F259-4D49-8710-7217F7AFFE43@.microsoft.com...
> I 've two machines (Linux Servers) with firewall installed at two
> geographical locations. Now I want to make replication of data using
> sqlserver2000 from two other machines which are behind the two servers .
Both
> of them have have private IP address and they can access the internet
> through the firewall . Now I have enabled the ports 1433 on both sides and
> had given the IP address of the receiving machine at the sending machine
> (Public IP at the network client -alias TCP/IP protocal) and vice versa.
> Proper mapping of IP (public to private is done ) at the two servers.
> But still I 'm getting the message, Failed to register the Sql Server
> Pl help

connectivity

dears,
I've installed one sql server instance .
It is connecting through Named pipes only
Through TCP/IP its not connecting.
Only the default instance in the machine is connecting through all
protocols
Why is it like that ?
Please help me...chaluvadi specialists (sanujss@.gmail.com) writes:
> dears,
> I've installed one sql server instance .
> It is connecting through Named pipes only
> Through TCP/IP its not connecting.
> Only the default instance in the machine is connecting through all
> protocols
> Why is it like that ?
> Please help me...
Which versions of SQL Server are the two instances running?
How do you conclude that you cannot connect to the named instance
through TCP/IP?
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've installed one sql server instance .
> It is connecting through Named pipes only
> Through TCP/IP its not connecting.
> Only the default instance in the machine is connecting through all
> protocols
Let's get the obvious out of the way:
What is the possibility that there is a firewall between your client and
your server that is blocking TCP:1433?
--
Peace & happy computing,
Mike Labosh, MCSD MCT
Owner, vbSensei.Com
"Escriba coda ergo sum." -- vbSensei

connections to MSDE with .net installed

Hi,
Does the .net framework take up a connection to MSDE when starting up? We
are experiencing the following scenario:
Start up computer
Start our program that uses MSDE and the .net framework
Runs very slow
Shut down program on all computers
Stop MSDE service and Start again and it runs fine.
The reason I ask about the .net framework is that our program ran fine
before we migrated it to .net.
It seems like the govenor kicks in as soon as the machine is started - maybe
..net checks liscences or something?
..Net does not automatically take up connections or check licenses to MSDE or
any other DBMS. Run SQL Profiler (you have the Developers Edition of SQL
Server, don't you?) and see if any unexpected connections are being made to
the MSDE instance.
Jim
"Andrew" <Andrew@.discussions.microsoft.com> wrote in message
news:BF7838CC-CC14-4953-82A4-280A7B8213F7@.microsoft.com...
> Hi,
> Does the .net framework take up a connection to MSDE when starting up? We
> are experiencing the following scenario:
> Start up computer
> Start our program that uses MSDE and the .net framework
> Runs very slow
> Shut down program on all computers
> Stop MSDE service and Start again and it runs fine.
> The reason I ask about the .net framework is that our program ran fine
> before we migrated it to .net.
> It seems like the govenor kicks in as soon as the machine is started -
maybe
> .net checks liscences or something?

Connectiong to MSDE 2000

I installed MSDE 2000 on my machine running XP home
edition.
I can connect with all client utilities, include, query
analiser, enterprise manager, odbc, etc if i use the
builtin/administrator id, but i cant connect in the SQL
MODE.
If i set up an odbc connection for test, i get the
following error
Attempting connection
[Microsoft][ODBC SQL Server Driver][SQL Server]Login
failed for user 'sa'. Reason: Not associated with a
trusted SQL Server connection.
The ODBC error returns a state 28000 error, with is an
authenticaton error, please how can i correct thisMSDE is installed by default with Windows authentication, not with mixed
authentication, so you can't login with a SQL login, like 'sa'. You can
change this from Enterprise Manager by rightclicking the server, choosing
properties, and change the Authentication on the Security tab. You ahve to
restart SQL Server for the setting to take effect.
Jacco Schalkwijk
SQL Server MVP
"Lanre" <larry548997@.yahoo.com_anonymous> wrote in message
news:1b8701c3fc16$8a0ec650$a401280a@.phx.gbl...
> I installed MSDE 2000 on my machine running XP home
> edition.
> I can connect with all client utilities, include, query
> analiser, enterprise manager, odbc, etc if i use the
> builtin/administrator id, but i cant connect in the SQL
> MODE.
> If i set up an odbc connection for test, i get the
> following error
> Attempting connection
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login
> failed for user 'sa'. Reason: Not associated with a
> trusted SQL Server connection.
> The ODBC error returns a state 28000 error, with is an
> authenticaton error, please how can i correct this|||If you don't have Enterprise Manager, you can change the setting with the
steps from this article:
285097 INF: How to Change the Default Login Authentication Mode to SQL While
http://support.microsoft.com/?id=285097
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.

Connection to the server is lost.

Hi
I have just installed SQL Server 2000 SP3 on 2000 server
.. I am attempting to connect to the Server through the
Analysis Manager, and I am getting an error of:
Cannot connect to the Analysis server on
computer 'computer name'
Connection to the server is lost.
I am able to connect if I use a administrator ID.
Using my ID I can connect using the Enterprise Manager to
the SQL server. On the server itself, I can't get into
Analysis Manager. Can anyone help?
My ID is listed inside the OLAP Administrators local group
on the server.
One more thing is after SP3 instllation, I have installed
and uninstalled EXCEL 2003. To get rid of one
error "version may not be valid" while connecting from
EXCEL To ANalysis Manager. Now this message has gone.
Thanks in advance for any help regarding this
Regards
Sajith
.Have you applied SP3 for SQL and Analysis Services on your client as well as
the server ?
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Sajith S" <sajith_sudhi@.hotmail.com> wrote in message
news:1229a01c3f5e1$94476720$a401280a@.phx
.gbl...
> Hi
> I have just installed SQL Server 2000 SP3 on 2000 server
> .. I am attempting to connect to the Server through the
> Analysis Manager, and I am getting an error of:
> Cannot connect to the Analysis server on
> computer 'computer name'
> Connection to the server is lost.
> I am able to connect if I use a administrator ID.
> Using my ID I can connect using the Enterprise Manager to
> the SQL server. On the server itself, I can't get into
> Analysis Manager. Can anyone help?
> My ID is listed inside the OLAP Administrators local group
> on the server.
> One more thing is after SP3 instllation, I have installed
> and uninstalled EXCEL 2003. To get rid of one
> error "version may not be valid" while connecting from
> EXCEL To ANalysis Manager. Now this message has gone.
> Thanks in advance for any help regarding this
> Regards
> Sajith
> .
>|||I did. But still the same error message.
So I have done the following workarounds
1. Uninstalled Analysis manager, Deleted the Olap
Administrators ID.
2. Installed Analysis Manager,Olap Administrator ID
created again by Analysis Manager. Applied SP3a.
Now everything found to be working...Thanks for the help.

>--Original Message--
>Have you applied SP3 for SQL and Analysis Services on
your client as well as
>the server ?
>--
>HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>
>"Sajith S" <sajith_sudhi@.hotmail.com> wrote in message
> news:1229a01c3f5e1$94476720$a401280a@.phx
.gbl...
to
group
installed
>
>.
>

Connection to the database on MSDE

Hi,

I installed MSDE and the sample databases with it. They work fine.

Well I am using the server explorer of visaula studio standard 2002. I can see all the sample databases there and connect to them as well.

1.
---------------------
Now i created a new database named "testDb" and in a similar fashion i am using windows login thingy.

When i write my connection string in the program now it doesnt work

string connectionStr =@."Server=IMRAN\NetSDK;" + "Integrated Security=SSPI;" + "Connection Timeout=7;" + "Database=testDB;";

If i replace my Database clause to Northwind it works absolutely fine.

The ERROR it gives is:

Cannot open database requested in login 'testDB'. Login fails. Login failed for user 'IMRAN\ASPNET'.

Why is this happenning? :(.

============================================

2.
--------
How can i configure the MSDE to use the SQL Authentication.
It doesnt allow me to do that?

Thanx Heaps,
ImranHi Guys,

I got the solution for the first problem of mine.

We need to Grant Access to the ASPNET user

The ASP.NET process runs under the MACHINENAME\ASPNET account. In order for the data access samples to access the database, this user must be granted rights to the sample databases. To manually grant access to the ASPNET user, replace MACHINENAME with the name of your computer, and run the following commands from the command line. Note: The path to the osql.exe command must be located in your PATH environment variable.

osql -E -S (local)\NetSDK -Q "sp_grantlogin 'MACHINENAME\ASPNET'"

osql -E -S (local)\NetSDK -d DATABASENAME -Q "sp_grantdbaccess 'MACHINENAME\ASPNET'"
osql -E -S (local)\NetSDK -d DATABASENAME -Q "sp_addrolemember 'db_owner', 'MACHINENAME\ASPNET'"

and if you are using the Sql Server Enterprise then just open the Enterprise manager and give the database rights to the [machine_name]\ASPNET user in the database users

Hope that can be useful for someone there.

Thanx.
Imran|||Hi,
Glad you found an answer. BTW, ASPNET is the default user name for Windows 2000 and XP, but it's 'NETWORK SERVICE' on Windows 2003 Server running native mode with IIS 6 (default). I found that out the hard way. After adding 'NT AUTHORITY\NETWORK SERVICE' as a login to SQL Server (MSDE), I was able to have my application access the database using the VS and IE browsers - clearying a major roadblock for me.

Also, you can use the Web Data Administrator to create a new login, if you don't have Enterprise manager, or don't want to use OSQL.

MS sure didn't make ASP.NET appliaction database access clear and simple! Maybe ASP.NET 2.0 will, but at what cost?

Good luck with your projects.

Connection to SQL server Help SOS

I have SQL Server2000 installed on my PC when I am trying to do some programs in ASP.NET application. I have serious problem working with the SQL server 2000.Whenever I use visual tools to connect to the server or manually. Explorer returns error
//////////////////////////////////////////////////////////////////////////////////////////////
Server Error in '/ASP.NetPage530' Application.

Login failed for user 'ZEUS\ASPNET'.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: Login failed for user 'ZEUS\ASPNET'.

Source Error:

Line 88: Private Sub Page_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
Line 89: If Not IsPostBack Then
Line 90: SqlDataAdapter1.Fill(DsCustID1, "Customers")
Line 91: DataBind()
Line 92: End If

Source File: C:\Inetpub\wwwroot\ASP.NetPage530\WebForm1.aspx.vb Line: 90

Stack Trace:

[SqlException: Login failed for user 'ZEUS\ASPNET'.]
System.Data.SqlClient.SqlConnection.Open()
System.Data.Common.DbDataAdapter.QuietOpen(IDbConnection connection, ConnectionState& originalState)
System.Data.Common.DbDataAdapter.Fill(Object data, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, String srcTable)
ASP.NetPage530.WebForm1.Page_Load(Object sender, EventArgs e) in C:\Inetpub\wwwroot\ASP.NetPage530\WebForm1.aspx.vb:90
System.Web.UI.Control.OnLoad(EventArgs e)
System.Web.UI.Control.LoadRecursive()
System.Web.UI.Page.ProcessRequestMain()
////////////////////////////////////////////////////////////////////////////////////////////////////////
No errors exist when I work with windows application both in ACCESS or SQL SERVER Databases and no errors exists when I am using access files in asp.net applicationand in both cases i use Windows NT Integrated Security .Most probably I need to configure my IIS5.0 but how I have no idea
Can anyone help?You may need to grant 'ZEUS\ASPNET' login permissions to your SQL Server. You can do this directly in SQL Server Enterprise Manager if you have it. Otherwise, you will need to use SQL language by running osql.exe from the command line.|||Yes but in command promt it asks for a password I have only one one pasword is system password which is invalid in command promt for osql.exe how i can configure it ?please help|||Type osql /? at the command line.

This gives you a list of parameters you can use to run the program.

I think you can use the-E parameter for a trusted connection.|||Thank you trying help me but I have no idea how to use –E parameters
I have tried the following command in command prompt osql/E the output was the number 1 what it means I don't know pushing the enter gives 2 and etc
what i have to do to enable trusted connections ???|||
If you are seeing this:

1
That means you are logged in succesfully.

Now you can execute any SQL statement. Each statement can consist of multiple lines. When you are finished, typeGO on a new line and hit enter. For Example (type enter at the end of each line):

1>Select name
2>From sysxlogins
3>go

This will display a list of current logins for your database.

What you need to do next is find some documentation on SQL language on how to add logins and grant them access to databases and database objects.

Have a look here for granting an NT user login permissions:http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_sp_ga-gz_8dri.asp

If you like, you can go here for security in general:http://msdn.microsoft.com/library/en-us/adminsql/ad_security_05bt.asp?frame=true

I hope this helps.

connection to SQL Server files (*.mdf) require SQL server express 2005 to function properl

I dont have the SQL EXPRESS installed instead I have SQL Standard Edition.

I have two SQL Server instances installed.

1- UserLT (this is sql 2000)
2- UserLT\SQL2005 (this is SQL 2005 named instance)

But when i try to add a database to my VS website project I get the following error:

Connection to SQL Server files (*.mdf) require SQL server express 2005 to function properly. please verify the installation of the component or download from the URL: go.microsoft.com/fwlink/?linkId=4925

I went in Tools>Opetions>DataBase tools>Data Connection>Sql Server Instance Name (blank for default)

and changed the "SQLEXPRESS" to "USERLT\SQL2005".

But I still get the same error message. Any ideas how i can resolve this issue?

Hello,

Attach the files to your SQL server instance using for example the SQL management Studio and change your connectionstring to connect into this database.

|||

Well the thing is that I dont have a database created yet. I am trying to create a new database. If i create a database in SQL 2005 then my connectionstring will point to the database on sql server. I need the database to reside in the VS project like a stand alone .mdf file so that I can deply the database with my project.

Does that make sense? Thanks for your help.

|||

Hi,

You may open your Machine.Config file (the file is in %SystemRoot%\Microsoft.NET\Framework\ver. number\CONFIG ). Try to find the ConnectionString node, modify the setting and make it look like

<add name="LocalSqlServer" connectionString="data source=UserLT\SQL2005;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|aspnetdb.mdf;User Instance=true" providerName="System.Data.SqlClient" />

Thanks.

Connection to SQL Server 2005

Hi all,
When I installed SPS 2003 , it installed MSDE as part of onstallation.
I also installed WSS SP 2 and SPS SP2 on it. I have SQL Server 2005
also installed on my machine.
How do I connect to this database for my WSS sites? How my sites in WSS
will be communicating to this sequal server?
Someone has suggeted that I should install SPS with SQLServer 2000 and
then upgrade it to SQL Server2005.I don't now why is it important to
install SQLServer 2000 and then upgrade it to 2005?
Is there any way that I can cope with the already made installations on
my machine?
Thanks
KahkashanDownload the WindowsSharePointServicesAdmin BOL from Microsoft, looks
into the section of 'Deployment Scenarios', it has very details how to
set up SPS to connect to a existing SQL Server (rather than use the
default WMSDE)
I followed the instruction and built a test SPS for our department, no
problem.
In the BOL, it only mention you need to have a SQL Server 2000 sp3 or
above to host the SPS databases. So you may need to check if they are
compatible with MSSQL 2005.
Mel

Connection to SQL Server 2005

Hi all,
When I installed SPS 2003 , it installed MSDE as part of onstallation.
I also installed WSS SP 2 and SPS SP2 on it. I have SQL Server 2005
also installed on my machine.
How do I connect to this database for my WSS sites? How my sites in WSS
will be communicating to this sequal server?
Someone has suggeted that I should install SPS with SQLServer 2000 and
then upgrade it to SQL Server2005.I don't now why is it important to
install SQLServer 2000 and then upgrade it to 2005?
Is there any way that I can cope with the already made installations on
my machine?
Thanks
KahkashanDownload the WindowsSharePointServicesAdmin BOL from Microsoft, looks
into the section of 'Deployment Scenarios', it has very details how to
set up SPS to connect to a existing SQL Server (rather than use the
default WMSDE)
I followed the instruction and built a test SPS for our department, no
problem.
In the BOL, it only mention you need to have a SQL Server 2000 sp3 or
above to host the SPS databases. So you may need to check if they are
compatible with MSSQL 2005.
Mel

Connection to SQL Server 2005

Hi all,
When I installed SPS 2003 , it installed MSDE as part of onstallation.
I also installed WSS SP 2 and SPS SP2 on it. I have SQL Server 2005
also installed on my machine.
How do I connect to this database for my WSS sites? How my sites in WSS
will be communicating to this sequal server?
Someone has suggeted that I should install SPS with SQLServer 2000 and
then upgrade it to SQL Server2005.I don't now why is it important to
install SQLServer 2000 and then upgrade it to 2005?
Is there any way that I can cope with the already made installations on
my machine?
Thanks
Kahkashan
Download the WindowsSharePointServicesAdmin BOL from Microsoft, looks
into the section of 'Deployment Scenarios', it has very details how to
set up SPS to connect to a existing SQL Server (rather than use the
default WMSDE)
I followed the instruction and built a test SPS for our department, no
problem.
In the BOL, it only mention you need to have a SQL Server 2000 sp3 or
above to host the SPS databases. So you may need to check if they are
compatible with MSSQL 2005.
Mel

Connection to SQL Server

I have installed MS SQL Server 2005 Express Edition with Advanced Services and MS SQL Server 2005 Express Edition Toolkit SP1. Everything istalled without any errors noted. When starting SQL Server Management Studio Express, accepting the server name MAYNARD-MAIN with authentication as windows authentication. I get the following message:

Cannot connect to MAYNARD-MAIN

Additional information:

An error has occurred while establishing a connection to the server. Wehn connecting to SQL Server 2005, this failure may be caused by the fact that under the default setting SQL Server does not allow remote connections.(provider:Shared Memory Provider, error:36 - The Shared Memory dll used to connect to SQL Server was not found)(Microsoft SQL Server, Error: 126)

I haven found any info on either of these error in the forum.

The Configuration Manager shows the following:

SQL Server FullTextSearch(SQLEXPRESS) - Running

SQL Server(SQLEXPRESS) - Running

SQL Server Reporting Services(SQLEXPRESS) - Running

SQL Server Browser - Running

Protocols for SQLEXPRESS

Shared Memory - Enabled

All others disabled

Client Protocols

Shared Memory - Order 1 - Enabled

TCP/IP - Order 2 - Enabled

Named Pipes - Order 3 - Enabled

VIA - Disabled.

What do I need to be trying to find to corect this.

Either connect to the default server instance..."SQLEXPRESS" or Make sure that the "MAYNARD_MAN" instance is running before trying to connect to it|||Well that was easy enough - I really feel dumb now. Add instance to machine name and it works a lot better. Sorry I took up your time being not to bright.

Connection to Server

I have installed Microsoft SQL Server 2000. I am now
thoroughly confused. :-(
When I click on Start/Continue button (in the SQL Server
Service Manager window), I encounter the following error:
- The service did not start due to logon failure.
- An error 1069 - (The service did not start due to a
logon failure) occurred while performing this service
operation on the SQSQLServer service.
Did I miss a set up step?
I'm also confused as to where I set up new users.
I am running Microsoft XP.
Any help will be most appreciated.
Thanks
Carolinehas the account that runs your SQL Service recently changed it's password?
You can reset the password in ctrl panel/admin tools/services
Ray Higdon MCSE, MCDBA, CCNA
--
"Caroline" <clydec@.comcast.net> wrote in message
news:9b8401c4061f$a88cd050$a001280a@.phx.gbl...
> I have installed Microsoft SQL Server 2000. I am now
> thoroughly confused. :-(
> When I click on Start/Continue button (in the SQL Server
> Service Manager window), I encounter the following error:
> - The service did not start due to logon failure.
> - An error 1069 - (The service did not start due to a
> logon failure) occurred while performing this service
> operation on the SQSQLServer service.
> Did I miss a set up step?
> I'm also confused as to where I set up new users.
> I am running Microsoft XP.
> Any help will be most appreciated.
> Thanks
>
> Caroline
>|||I went to Services, but wasn't sure what I needed to do
there. No passwords have been changed since I bought my
laptop.
SQL Server is installed on my home laptop and it is only a
single instance use.
Any other suggestions?
Thanks
Caroline

>--Original Message--
>has the account that runs your SQL Service recently
changed it's password?
>You can reset the password in ctrl panel/admin
tools/services
>--
>Ray Higdon MCSE, MCDBA, CCNA
>--
>"Caroline" <clydec@.comcast.net> wrote in message
>news:9b8401c4061f$a88cd050$a001280a@.phx.gbl...
error:
>
>.
>|||In services go to MSSQLServer service. If it using a login, change it to use
local system and try to start the service, if it starts then you have an
account or password problem with the other account
Ray Higdon MCSE, MCDBA, CCNA
--
"Caroline" <clydec@.comcast.net> wrote in message
news:a8e501c406bc$0c14bb00$a101280a@.phx.gbl...
> I went to Services, but wasn't sure what I needed to do
> there. No passwords have been changed since I bought my
> laptop.
> SQL Server is installed on my home laptop and it is only a
> single instance use.
> Any other suggestions?
> Thanks
>
> Caroline
>
> changed it's password?
> tools/services
> error:

Connection To Remote Server

I have recently installed SQL Server 2005 onto my development machine and
another developers machine. I am trying to connect to his server via my SQL
Server Management Studio but I am getting the following error.
==================================================
"A connection was successfully established with the server, but then an
error occurred during the pre-login handshake. 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: 0 - No process is on the other end of the pipe.) (.Net
SqlClient Data Provider)"
==================================================
His server is set to allow remote connections. How do I resolve this?
Hello Terry,
I would like to know if you try to add an alias to the remote server, will
it resolve this issue?
1. Open the SQL Server Configuration Manager.
2. Click the SQL Native Client Configuration and right click the Aliases
node. Then Click New Alias...
3. In the Alias - New dialogbox, please type the Alias Name, the Server
name and the TCP/IP port.
4. Click OK and try to connect to the remote server.
Hope this will be helpful!
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Im not sure if I followed instructions correctly but I am still getting the
same problem.
This is what I did:
I did the following on my dev machine - im not sure what port to use so i
tried a range from 100 - 9999

> 1. Open the SQL Server Configuration Manager.
> 2. Click the SQL Native Client Configuration and right click the Aliases
node. Then Click New Alias...
> 3. In the Alias - New dialogbox, please type the Alias Name, the Server
> name and the TCP/IP port.
> 4. Click OK and try to connect to the remote server.
>
|||Hello Terry,
First, I would like to suggest you follow the KB article to check the
connection issue:
827422How to troubleshoot connectivity issues in SQL Server 2000
http://support.microsoft.com/default.aspx?scid=kb;EN-US;827422
Although this article is for the SQL 2000, you could follow the general
troubleshoot steps to narrow down the issue.
Then, please make sure you have typed the correct instance name when you
use my previous approach.
The TCP/IP port is 1433 for the default configuration.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Thank you for your attempts to solve this problem. It is still not resolved
so I am calling microsoft as i need a quick solution.
|||I have solved the problem with the help of microsoft telephone support and I
am posting the solution fyi
=======================================
Enabled “Local and remote connections – Using TCP and Named pipes” in
SQL server surface area configuration tool and the issue is resolved.

Connection To Remote Server

I have recently installed SQL Server 2005 onto my development machine and
another developers machine. I am trying to connect to his server via my SQL
Server Management Studio but I am getting the following error.
========================================
==========
"A connection was successfully established with the server, but then an
error occurred during the pre-login handshake. When connecting to SQL Serve
r
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: 0 - No process is on the other end of the pipe.) (.Net
SqlClient Data Provider)"
========================================
==========
His server is set to allow remote connections. How do I resolve this?Hello Terry,
I would like to know if you try to add an alias to the remote server, will
it resolve this issue?
1. Open the SQL Server Configuration Manager.
2. Click the SQL Native Client Configuration and right click the Aliases
node. Then Click New Alias...
3. In the Alias - New dialogbox, please type the Alias Name, the Server
name and the TCP/IP port.
4. Click OK and try to connect to the remote server.
Hope this will be helpful!
Sincerely,
Wei Lu
Microsoft Online Community Support
========================================
==========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscript...ault.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscript...t/default.aspx.
========================================
==========
(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
========================================
==========
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.|||Im not sure if I followed instructions correctly but I am still getting the
same problem.
This is what I did:
I did the following on my dev machine - im not sure what port to use so i
tried a range from 100 - 9999

> 1. Open the SQL Server Configuration Manager.
> 2. Click the SQL Native Client Configuration and right click the Aliases
node. Then Click New Alias...
> 3. In the Alias - New dialogbox, please type the Alias Name, the Server
> name and the TCP/IP port.
> 4. Click OK and try to connect to the remote server.
>|||Hello Terry,
First, I would like to suggest you follow the KB article to check the
connection issue:
827422 How to troubleshoot connectivity issues in SQL Server 2000
http://support.microsoft.com/defaul...kb;EN-US;827422
Although this article is for the SQL 2000, you could follow the general
troubleshoot steps to narrow down the issue.
Then, please make sure you have typed the correct instance name when you
use my previous approach.
The TCP/IP port is 1433 for the default configuration.
Sincerely,
Wei Lu
Microsoft Online Community Support
========================================
==========
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.|||Thank you for your attempts to solve this problem. It is still not resolved
so I am calling microsoft as i need a quick solution.|||I have solved the problem with the help of microsoft telephone support and I
am posting the solution fyi
=======================================
Enabled “Local and remote connections – Using TCP and Named pipes” in
SQL server surface area configuration tool and the issue is resolved.