Cannot determine default collation

when i tried to install the lastest MSDE release A, it has this error. How should I solve it?
See the following KB article for more info on this problem:
http://support.microsoft.com/?id=838302
You can avoid the problem by (temporarily) changing your default system
locale to a locale that isn't in the list in that article, reboot, then
retry the installation. You can also avoid the problem by passing the
COLLATION command line parameter to setup (e.g.
"COLLATION=SQL_Latin1_General_CP1_CI_AS".
Bart
Bart Duncan
Microsoft SQL Server Support
Please reply to the newsgroup only - thanks.
This posting is provided "AS IS" with no warranties, and confers no
rights.
Thread-Topic: Cannot determine default collation
thread-index: AcRS8jxBIFmv0lEuTbeceZiciXUOYg==
X-WBNR-Posting-Host: 61.10.7.203
From: =?Utf-8?B?U2Fu?= <San@.discussions.microsoft.com>
Subject: Cannot determine default collation
Date: Tue, 15 Jun 2004 09:03:01 -0700
Lines: 1
Message-ID: <9101766C-F170-4F20-A300-554889E2A0C2@.microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.sqlserver.msde
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 127.0.0.1
Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFT NGXA01.phx.gbl!TK2MSFTNG
XA03.phx.gbl
Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.msde:15056
X-Tomcat-NG: microsoft.public.sqlserver.msde
when i tried to install the lastest MSDE release A, it has this error.
How should I solve it?

Cannot create a new ODBC connector to my SQL server

I am trying to install a third party application that requires a SQL server.
I am using SQL 2000 in an SBS Premium environment. It appears that my
install of SQL server has some issues. To test I tried creating a new ODBC
connector to my SQL server. Using the ODBC Data Source admin tool, from the
"User DSN" tab I select "Add". From the Create a New Data Source window I
select "SQL Server". I give it a Name, Description and select my SQL server
from the drop down menu. The next window "How should SQL server verify the
authenticity of the login ID?" I choose "With SQL Server authentication
using a login ID and password entered by the user". I enter my ID and
password and get an error.
"Connection Failed:
SQL State: '28000'
SQL Server Error: 18456
[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for sqladmin.
Note: This sqladmin ID is a member of the Domain Admins group and has DBO in
SQL server.
Did you activate Mixed mode authentication on the server ?
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"AllenM" <allen@.majaro.com> schrieb im Newsbeitrag
news:u1jJQCYVFHA.2128@.TK2MSFTNGP14.phx.gbl...
>I am trying to install a third party application that requires a SQL
>server. I am using SQL 2000 in an SBS Premium environment. It appears that
>my install of SQL server has some issues. To test I tried creating a new
>ODBC connector to my SQL server. Using the ODBC Data Source admin tool,
>from the "User DSN" tab I select "Add". From the Create a New Data Source
>window I select "SQL Server". I give it a Name, Description and select my
>SQL server from the drop down menu. The next window "How should SQL server
>verify the authenticity of the login ID?" I choose "With SQL Server
>authentication using a login ID and password entered by the user". I enter
>my ID and password and get an error.
> "Connection Failed:
> SQL State: '28000'
> SQL Server Error: 18456
> [Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for sqladmin.
> Note: This sqladmin ID is a member of the Domain Admins group and has DBO
> in SQL server.
>

Cannot create a new ODBC connector to my SQL server

I am trying to install a third party application that requires a SQL server.
I am using SQL 2000 in an SBS Premium environment. It appears that my
install of SQL server has some issues. To test I tried creating a new ODBC
connector to my SQL server. Using the ODBC Data Source admin tool, from the
"User DSN" tab I select "Add". From the Create a New Data Source window I
select "SQL Server". I give it a Name, Description and select my SQL server
from the drop down menu. The next window "How should SQL server verify the
authenticity of the login ID?" I choose "With SQL Server authentication
using a login ID and password entered by the user". I enter my ID and
password and get an error.
"Connection Failed:
SQL State: '28000'
SQL Server Error: 18456
[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for sqladmin.
Note: This sqladmin ID is a member of the Domain Admins group and has DBO in
SQL server.Did you activate Mixed mode authentication on the server ?
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"AllenM" <allen@.majaro.com> schrieb im Newsbeitrag
news:u1jJQCYVFHA.2128@.TK2MSFTNGP14.phx.gbl...
>I am trying to install a third party application that requires a SQL
>server. I am using SQL 2000 in an SBS Premium environment. It appears that
>my install of SQL server has some issues. To test I tried creating a new
>ODBC connector to my SQL server. Using the ODBC Data Source admin tool,
>from the "User DSN" tab I select "Add". From the Create a New Data Source
>window I select "SQL Server". I give it a Name, Description and select my
>SQL server from the drop down menu. The next window "How should SQL server
>verify the authenticity of the login ID?" I choose "With SQL Server
>authentication using a login ID and password entered by the user". I enter
>my ID and password and get an error.
> "Connection Failed:
> SQL State: '28000'
> SQL Server Error: 18456
> [Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for sqladmin.
> Note: This sqladmin ID is a member of the Domain Admins group and has DBO
> in SQL server.
>

Cannot create a new ODBC connector to my SQL server

I am trying to install a third party application that requires a SQL server.
I am using SQL 2000 in an SBS Premium environment. It appears that my
install of SQL server has some issues. To test I tried creating a new ODBC
connector to my SQL server. Using the ODBC Data Source admin tool, from the
"User DSN" tab I select "Add". From the Create a New Data Source window I
select "SQL Server". I give it a Name, Description and select my SQL server
from the drop down menu. The next window "How should SQL server verify the
authenticity of the login ID?" I choose "With SQL Server authentication
using a login ID and password entered by the user". I enter my ID and
password and get an error.
"Connection Failed:
SQL State: '28000'
SQL Server Error: 18456
[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for
sqladmin.
Note: This sqladmin ID is a member of the Domain Admins group and has DBO in
SQL server.Did you activate Mixed mode authentication on the server ?
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"AllenM" <allen@.majaro.com> schrieb im Newsbeitrag
news:u1jJQCYVFHA.2128@.TK2MSFTNGP14.phx.gbl...
>I am trying to install a third party application that requires a SQL
>server. I am using SQL 2000 in an SBS Premium environment. It appears that
>my install of SQL server has some issues. To test I tried creating a new
>ODBC connector to my SQL server. Using the ODBC Data Source admin tool,
>from the "User DSN" tab I select "Add". From the Create a New Data Source
>window I select "SQL Server". I give it a Name, Description and select my
>SQL server from the drop down menu. The next window "How should SQL server
>verify the authenticity of the login ID?" I choose "With SQL Server
>authentication using a login ID and password entered by the user". I enter
>my ID and password and get an error.
> "Connection Failed:
> SQL State: '28000'
> SQL Server Error: 18456
> [Microsoft][ODBC SQL Server Driver][SQL Server] Login failed f
or sqladmin.
> Note: This sqladmin ID is a member of the Domain Admins group and has DBO
> in SQL server.
>

cannot connect to the server

hello,
i want to install sql server 2000 in my machine which has win xp. now the
problem is that it does not get connected to the server. error message comes
that there is a connection failure.
pls help me
thank u
bituDid you configuire the firewall to let the appropiate ports SQL Server
is configured for let through ?
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
--

cannot connect to the server

hello,
i want to install sql server 2000 in my machine which has win xp. now the
problem is that it does not get connected to the server. error message comes
that there is a connection failure.
pls help me
thank u
bitu
Did you configuire the firewall to let the appropiate ports SQL Server
is configured for let through ?
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de

Cannot connect to SQLServer 2005

After several attempts to install SQL2005 I finally got Microsoft SQL Server Management Studio installed.
But now I get the error below:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)

The sa account username/password are correct and don't work, windows authentication does not work, I have stopped/started all the services, I have all Protocols enabled correctly, I have my Firewall turned off.

Is there anything else I can try? Anything!

After 24 hours of looking at this, I just figured out the answer!!! ServerName\instance is needed for logging on!!

Cannot connect to SQL Server 2005 June CTP

We just install SQL Server 2005 June CTP on a Windows
2003 with SP1 and probably all the additional patches.
We just simply cannot connect to the SQL Server at all.
The SQL Server service is running. When we try to
register and click on Test button, we will just get
Timeout expired. We're using SQL Server Authentication.

We have used the June CTP to do an upgrade from SQL
Server 2000 on a Windows 2003 SP1 but without any additional patch
and we don't have any problem.

By the way, beside this forum, are there any other place in MS website to post questions related SQL Server 2005? So far, I only find this
http://communities.microsoft.com/newsgroups/default.asp?icp=sqlserver2005&slcid=us

Thanks for any help,

Peter

Are you trying to connect from a tool (SQL Server Management Studio, for example) that is local to the same server SQL Server 2005 is running on? Or from a different server/client?

By default, SQL Server 2005 now installs with remote connections turned off (secure by default initiative). So, after installing, you have to enable remote connections before you will be able to connect from a different server/client. To do this, use the SQL Server Surface Area Configuration tool.

Dave Fackler

|||

Hi Dave,

I'm trying to connect from SQL Server Management Studio on the same server SQL Server 2005 June CTP is running on.

I just also tried to use osql and I get the following error:

[SQL Native Client]TCP Provider: No connection could be made because the target machine actively refused it.
[SQL Native Client]Client unable to establish connection.
[SQL Native Client]Login timeout expired.

Thanks,

Peter
Peter

Cannot connect to SQL express database ??

Dear all,
I have setup a database under SQLexpress 2005 which is install on a Vista OS
.
I can manage without any problem my database from the VIsta workstation.
Then on an other PC, I am trying to create a connection to that databse with
.NET 1.1, but no luck
I ma using similar conenction string as for an SQL server databse excpet
that Server="MyWorkStationName\SQLEXPRESS".
I have place the conenctionstring in a config file as follow :
" Database=Line_Config;Server=MyWorkStatio
nName\SQLEXPRESS;uid=rptuser;Pwd=re
porting"
What is wrong that prebvent me from connection to database ?
Is it possible to connect to an SQLExpress database located on an other PC ?
thnaks for help
regards
sergeProbably either the SQL Server Express instance has not enabled remote
connections, or a firewall is blocking the connection.
Run through the short tutorial in Books Online and see if that solves the
problem. The tutorial is also online at
http://msdn2.microsoft.com/en-us/library/ms345318.aspx Note that lesson 2 is
Connecting from Another Computer.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"calderara" <calderara@.discussions.microsoft.com> wrote in message
news:067F10D8-72B1-4858-AE9F-E5EEF213BEF1@.microsoft.com...
> Dear all,
> I have setup a database under SQLexpress 2005 which is install on a Vista
> OS.
> I can manage without any problem my database from the VIsta workstation.
> Then on an other PC, I am trying to create a connection to that databse
> with
> .NET 1.1, but no luck
> I ma using similar conenction string as for an SQL server databse excpet
> that Server="MyWorkStationName\SQLEXPRESS".
> I have place the conenctionstring in a config file as follow :
>
> " Database=Line_Config;Server=MyWorkStatio
nName\SQLEXPRESS;uid=rptuser;Pwd=
reporting"
> What is wrong that prebvent me from connection to database ?
> Is it possible to connect to an SQLExpress database located on an other PC
> ?
> thnaks for help
> regards
> serge|||Thnaks for your reply...
I have check seetings as describe in this link.
What happen is that I have SQL express install on a Vista machine
Then I set use of tcp port from the surface configuration tool and set port
to 1500
From a simple remote machine running w2000, I try to establish an ODBC
connection to my VIsta machine where SQL express is installed.
For that I have install on my 2000 machine the SQL native client for 2005
and try to define a DSN name but when trying to connect...no way...
Any ideas ?
regards
serge
"Rick Byham, (MSFT)" wrote:

> Probably either the SQL Server Express instance has not enabled remote
> connections, or a firewall is blocking the connection.
> Run through the short tutorial in Books Online and see if that solves the
> problem. The tutorial is also online at
> http://msdn2.microsoft.com/en-us/library/ms345318.aspx Note that lesson 2
is
> Connecting from Another Computer.
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> "calderara" <calderara@.discussions.microsoft.com> wrote in message
> news:067F10D8-72B1-4858-AE9F-E5EEF213BEF1@.microsoft.com...
>|||Did you stop and restart SQL Server 2005 Express Edition after setting 1500
as the fixed port?
Are you attempting to connect to the Express Edition by name in the format
computer_name\SQLExpress ?
Is the SQL Server Browser service running?
Can you connect to the Express Edition by the port number using
computer_name,1500 or by IP address in the format 127.025.144.315,1500 ?
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"calderara" <calderara@.discussions.microsoft.com> wrote in message
news:F1AB79D1-899E-40C6-BE14-21D0305C36CA@.microsoft.com...[vbcol=seagreen]
> Thnaks for your reply...
> I have check seetings as describe in this link.
> What happen is that I have SQL express install on a Vista machine
> Then I set use of tcp port from the surface configuration tool and set
> port
> to 1500
> From a simple remote machine running w2000, I try to establish an ODBC
> connection to my VIsta machine where SQL express is installed.
> For that I have install on my 2000 machine the SQL native client for 2005
> and try to define a DSN name but when trying to connect...no way...
> Any ideas ?
> regards
> serge
> "Rick Byham, (MSFT)" wrote:
>|||OK it works now rick...
I have made 2 mistakes...
Frist of all I forgot to open the port 1500 in my windows firewall.
Then I was accessing my server by using <myPCname>\SQLEXPRESS as I use to do
normally with SQL server.
SO in order to work I have to connect using tcp:<myPCname>\SQLEXPRESS,1500
But I like whem I undersatnd things. This connection string using sytax
above is use like that only for this express edition ? I guess not, I mean I
have made many connection like that with SQL server ( On a real server sure)
and I was juist using the instance and Pc name.
Or may be it would work also if I add left the default setting when you use
TCP as port 1443 and let SQL as dynamic mode and then just open the port 144
3
on my firewall. Then use as connection string :<myPCname>\SQLEXPRESS.
But of course dynamic means dynamic.
Does it means that this dynamic TP port seting should never be use with SQL
server ?
regards
serge
"Rick Byham, (MSFT)" wrote:

> Did you stop and restart SQL Server 2005 Express Edition after setting 150
0
> as the fixed port?
> Are you attempting to connect to the Express Edition by name in the format
> computer_name\SQLExpress ?
> Is the SQL Server Browser service running?
> Can you connect to the Express Edition by the port number using
> computer_name,1500 or by IP address in the format 127.025.144.315,1500 ?
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> "calderara" <calderara@.discussions.microsoft.com> wrote in message
> news:F1AB79D1-899E-40C6-BE14-21D0305C36CA@.microsoft.com...
>|||Connecting to the server name (<myPCname>\SQLEXPRESS) should work, if the
SQL Server Browser service is running. However, yes, you are correct that if
SQL Server Express Edition is using dynamic ports, then the port could
change to one that is blocked by the firewall. So you will need to switch
SQL Server Express Edition to a fixed port.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"calderara" <calderara@.discussions.microsoft.com> wrote in message
news:B778178D-FF1E-4827-981E-369B3C5C9AFE@.microsoft.com...[vbcol=seagreen]
> OK it works now rick...
> I have made 2 mistakes...
> Frist of all I forgot to open the port 1500 in my windows firewall.
> Then I was accessing my server by using <myPCname>\SQLEXPRESS as I use to
> do
> normally with SQL server.
> SO in order to work I have to connect using tcp:<myPCname>\SQLEXPRESS,1500
> But I like whem I undersatnd things. This connection string using sytax
> above is use like that only for this express edition ? I guess not, I mean
> I
> have made many connection like that with SQL server ( On a real server
> sure)
> and I was juist using the instance and Pc name.
> Or may be it would work also if I add left the default setting when you
> use
> TCP as port 1443 and let SQL as dynamic mode and then just open the port
> 1443
> on my firewall. Then use as connection string :<myPCname>\SQLEXPRESS.
> But of course dynamic means dynamic.
> Does it means that this dynamic TP port seting should never be use with
> SQL
> server ?
> regards
> serge
> "Rick Byham, (MSFT)" wrote:
>

Cannot connect to SQL express database ??

Dear all,
I have setup a database under SQLexpress 2005 which is install on a Vista OS.
I can manage without any problem my database from the VIsta workstation.
Then on an other PC, I am trying to create a connection to that databse with
..NET 1.1, but no luck
I ma using similar conenction string as for an SQL server databse excpet
that Server="MyWorkStationName\SQLEXPRESS".
I have place the conenctionstring in a config file as follow :
"Database=Line_Config;Server=MyWorkStationName\SQL EXPRESS;uid=rptuser;Pwd=reporting"
What is wrong that prebvent me from connection to database ?
Is it possible to connect to an SQLExpress database located on an other PC ?
thnaks for help
regards
serge
Probably either the SQL Server Express instance has not enabled remote
connections, or a firewall is blocking the connection.
Run through the short tutorial in Books Online and see if that solves the
problem. The tutorial is also online at
http://msdn2.microsoft.com/en-us/library/ms345318.aspx Note that lesson 2 is
Connecting from Another Computer.
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"calderara" <calderara@.discussions.microsoft.com> wrote in message
news:067F10D8-72B1-4858-AE9F-E5EEF213BEF1@.microsoft.com...
> Dear all,
> I have setup a database under SQLexpress 2005 which is install on a Vista
> OS.
> I can manage without any problem my database from the VIsta workstation.
> Then on an other PC, I am trying to create a connection to that databse
> with
> .NET 1.1, but no luck
> I ma using similar conenction string as for an SQL server databse excpet
> that Server="MyWorkStationName\SQLEXPRESS".
> I have place the conenctionstring in a config file as follow :
>
> "Database=Line_Config;Server=MyWorkStationName\SQL EXPRESS;uid=rptuser;Pwd=reporting"
> What is wrong that prebvent me from connection to database ?
> Is it possible to connect to an SQLExpress database located on an other PC
> ?
> thnaks for help
> regards
> serge
|||Thnaks for your reply...
I have check seetings as describe in this link.
What happen is that I have SQL express install on a Vista machine
Then I set use of tcp port from the surface configuration tool and set port
to 1500
From a simple remote machine running w2000, I try to establish an ODBC
connection to my VIsta machine where SQL express is installed.
For that I have install on my 2000 machine the SQL native client for 2005
and try to define a DSN name but when trying to connect...no way...
Any ideas ?
regards
serge
"Rick Byham, (MSFT)" wrote:

> Probably either the SQL Server Express instance has not enabled remote
> connections, or a firewall is blocking the connection.
> Run through the short tutorial in Books Online and see if that solves the
> problem. The tutorial is also online at
> http://msdn2.microsoft.com/en-us/library/ms345318.aspx Note that lesson 2 is
> Connecting from Another Computer.
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "calderara" <calderara@.discussions.microsoft.com> wrote in message
> news:067F10D8-72B1-4858-AE9F-E5EEF213BEF1@.microsoft.com...
>
|||Did you stop and restart SQL Server 2005 Express Edition after setting 1500
as the fixed port?
Are you attempting to connect to the Express Edition by name in the format
computer_name\SQLExpress ?
Is the SQL Server Browser service running?
Can you connect to the Express Edition by the port number using
computer_name,1500 or by IP address in the format 127.025.144.315,1500 ?
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"calderara" <calderara@.discussions.microsoft.com> wrote in message
news:F1AB79D1-899E-40C6-BE14-21D0305C36CA@.microsoft.com...[vbcol=seagreen]
> Thnaks for your reply...
> I have check seetings as describe in this link.
> What happen is that I have SQL express install on a Vista machine
> Then I set use of tcp port from the surface configuration tool and set
> port
> to 1500
> From a simple remote machine running w2000, I try to establish an ODBC
> connection to my VIsta machine where SQL express is installed.
> For that I have install on my 2000 machine the SQL native client for 2005
> and try to define a DSN name but when trying to connect...no way...
> Any ideas ?
> regards
> serge
> "Rick Byham, (MSFT)" wrote:
|||OK it works now rick...
I have made 2 mistakes...
Frist of all I forgot to open the port 1500 in my windows firewall.
Then I was accessing my server by using <myPCname>\SQLEXPRESS as I use to do
normally with SQL server.
SO in order to work I have to connect using tcp:<myPCname>\SQLEXPRESS,1500
But I like whem I undersatnd things. This connection string using sytax
above is use like that only for this express edition ? I guess not, I mean I
have made many connection like that with SQL server ( On a real server sure)
and I was juist using the instance and Pc name.
Or may be it would work also if I add left the default setting when you use
TCP as port 1443 and let SQL as dynamic mode and then just open the port 1443
on my firewall. Then use as connection string :<myPCname>\SQLEXPRESS.
But of course dynamic means dynamic.
Does it means that this dynamic TP port seting should never be use with SQL
server ?
regards
serge
"Rick Byham, (MSFT)" wrote:

> Did you stop and restart SQL Server 2005 Express Edition after setting 1500
> as the fixed port?
> Are you attempting to connect to the Express Edition by name in the format
> computer_name\SQLExpress ?
> Is the SQL Server Browser service running?
> Can you connect to the Express Edition by the port number using
> computer_name,1500 or by IP address in the format 127.025.144.315,1500 ?
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "calderara" <calderara@.discussions.microsoft.com> wrote in message
> news:F1AB79D1-899E-40C6-BE14-21D0305C36CA@.microsoft.com...
>
|||Connecting to the server name (<myPCname>\SQLEXPRESS) should work, if the
SQL Server Browser service is running. However, yes, you are correct that if
SQL Server Express Edition is using dynamic ports, then the port could
change to one that is blocked by the firewall. So you will need to switch
SQL Server Express Edition to a fixed port.
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"calderara" <calderara@.discussions.microsoft.com> wrote in message
news:B778178D-FF1E-4827-981E-369B3C5C9AFE@.microsoft.com...[vbcol=seagreen]
> OK it works now rick...
> I have made 2 mistakes...
> Frist of all I forgot to open the port 1500 in my windows firewall.
> Then I was accessing my server by using <myPCname>\SQLEXPRESS as I use to
> do
> normally with SQL server.
> SO in order to work I have to connect using tcp:<myPCname>\SQLEXPRESS,1500
> But I like whem I undersatnd things. This connection string using sytax
> above is use like that only for this express edition ? I guess not, I mean
> I
> have made many connection like that with SQL server ( On a real server
> sure)
> and I was juist using the instance and Pc name.
> Or may be it would work also if I add left the default setting when you
> use
> TCP as port 1443 and let SQL as dynamic mode and then just open the port
> 1443
> on my firewall. Then use as connection string :<myPCname>\SQLEXPRESS.
> But of course dynamic means dynamic.
> Does it means that this dynamic TP port seting should never be use with
> SQL
> server ?
> regards
> serge
> "Rick Byham, (MSFT)" wrote:

cannot connect to sql 2005 with management studio

Hi ,

I install sql 2005 CTP but cannot connect to the server with management studio

installation was successful and was named instance and under local system account

in event viewer mssql service is running ok, I see even it connects to master db

I can start and stop server with my old sql agent 2000

and I see only 1 error saying in event log:

The SQL Network Interface library was unable to register SPN. Error: 0x54b.

I have for OS 2003 server running on my laptop :-)

any help?

please read following forum thread.
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=20067
hope that solves your problem.
thanks
sql blog
|||thanks just ZoneAlarm firewall was too good - it works fine now

Cannot connect to SQL 2000 remotely

I'm trying to install a bespoke application for a new client, and am
embarassed by not being able to connect to their DB Server.
The server and clients are XP all running on a workgroup called OFFICE
File access is not problem and the DB Server name appears in a dropdown box
of SQL servers on the network - e.g. when trying to create an ODBC DSN.
The SQL Server is now configured to accept Windows and SQL authentication
connection requests - and restarted.
I have switched off or uninstalled everything that looks like a firewall on
both server and clients.
When trying to set up local ODBC DSN to connect as sa, I can connect no
problem, but from one of the client laptops I just get the error:
"Access denied or SQL Server does not exist"
Can anyone tell me where else to look or what else to try?
Is there a step by step procedure which could take me to the cause of the
problem?
The network is a wireless Lan - and IPX/SPX is featuring in the network
stack. Could that be something to do with it?
Any help very very much appreaciated!
Thank you
Clive (London UK)On the server, from the Start menu, point to All Programs, point to
Microsoft SQL Server, and then click Server Network Utility. That utility
should help you understand if SQL Server is using the IPX/SPX or TCP/IP
protocols, which might indicate a problem. On the client there is a similar
program, the Client Network Utility. Obviously the client and server should
be using the same protocols.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Clive" <clive.elsworth@.takeoutonetel.net> wrote in message
news:OxUCSSVyHHA.5856@.TK2MSFTNGP02.phx.gbl...
> I'm trying to install a bespoke application for a new client, and am
> embarassed by not being able to connect to their DB Server.
> The server and clients are XP all running on a workgroup called OFFICE
> File access is not problem and the DB Server name appears in a dropdown
> box of SQL servers on the network - e.g. when trying to create an ODBC
> DSN.
> The SQL Server is now configured to accept Windows and SQL authentication
> connection requests - and restarted.
> I have switched off or uninstalled everything that looks like a firewall
> on both server and clients.
> When trying to set up local ODBC DSN to connect as sa, I can connect no
> problem, but from one of the client laptops I just get the error:
> "Access denied or SQL Server does not exist"
> Can anyone tell me where else to look or what else to try?
> Is there a step by step procedure which could take me to the cause of the
> problem?
> The network is a wireless Lan - and IPX/SPX is featuring in the network
> stack. Could that be something to do with it?
> Any help very very much appreaciated!
> Thank you
> Clive (London UK)
>
>
>
>|||Could it be because the default MSDE 2000 sp3a setup is to Disable network
protocols?
It seems that you can't rely on the setup utility to warn of this kind of
change between sp3 and sp3a. You just have to make sure you read all the
gumf every time - just in case they've decided to quietly cripple your
system this time.
"Rick Byham, (MSFT)" <rickbyh@.REDMOND.CORP.MICROSOFT.COM> wrote in message
news:1CAB65A1-509E-4338-8C33-65D98FDA7300@.microsoft.com...
> On the server, from the Start menu, point to All Programs, point to
> Microsoft SQL Server, and then click Server Network Utility. That utility
> should help you understand if SQL Server is using the IPX/SPX or TCP/IP
> protocols, which might indicate a problem. On the client there is a
> similar program, the Client Network Utility. Obviously the client and
> server should be using the same protocols.
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Clive" <clive.elsworth@.takeoutonetel.net> wrote in message
> news:OxUCSSVyHHA.5856@.TK2MSFTNGP02.phx.gbl...
>|||Apologies for flame throwing. Default of DisableNetworkProtocols WAS the
problem, but in any case
thank for taking the time and trouble to get back to me Rick.
Clive Elsworth
"Rick Byham, (MSFT)" <rickbyh@.REDMOND.CORP.MICROSOFT.COM> wrote in message
news:1CAB65A1-509E-4338-8C33-65D98FDA7300@.microsoft.com...
> On the server, from the Start menu, point to All Programs, point to
> Microsoft SQL Server, and then click Server Network Utility. That utility
> should help you understand if SQL Server is using the IPX/SPX or TCP/IP
> protocols, which might indicate a problem. On the client there is a
> similar program, the Client Network Utility. Obviously the client and
> server should be using the same protocols.
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Clive" <clive.elsworth@.takeoutonetel.net> wrote in message
> news:OxUCSSVyHHA.5856@.TK2MSFTNGP02.phx.gbl...
>|||Glad to help. I recognize customers stress and confusion as a problem that
we (Microsoft) often cause... and have an obligation to resolve.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Clive" <clive.elsworth@.takeoutonetel.net> wrote in message
news:O7J9R4pzHHA.3400@.TK2MSFTNGP03.phx.gbl...
> Apologies for flame throwing. Default of DisableNetworkProtocols WAS the
> problem, but in any case
> thank for taking the time and trouble to get back to me Rick.
> Clive Elsworth
>
>
> "Rick Byham, (MSFT)" <rickbyh@.REDMOND.CORP.MICROSOFT.COM> wrote in message
> news:1CAB65A1-509E-4338-8C33-65D98FDA7300@.microsoft.com...
>

Cannot connect to server

Hi,

I am using sql server 2005 sp1 developer edtion. I have looked at the install logs and all ok, but when connecting to my server (LAPTOP) i get the following error below. I have not changed any of the xml config file, if anyone can help me i would be very grateful.

Thanks in advance

kered

TITLE: Connect to Server

Cannot connect to LAPTOP.

ADDITIONAL INFORMATION:

The type initializer for 'System.Data.SqlClient.SqlConnection' threw an exception. (System.Data)

The type initializer for 'System.Data.SqlClient.SqlConnectionFactory' threw an exception. (System.Data)

The type initializer for 'System.Data.SqlClient.SqlPerformanceCounters' threw an exception. (System.Data)

Configuration system failed to initialize (System.Configuration)

Unrecognized configuration section Runtime. (C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\SqlWb.exe.Config line 2) (System.Configuration)

BUTTONS:

OK

Are you using any application or tool to connect your server?

Check whether SQL Server services are started.

|||

Hi, Satya SKJ

I am not using a tool or application to connect to my server just opening sql server and trying to connect. I have uninstalled and installed a again same problem. I have also stopped and started sql serveices.

kered

|||

can u paste the file

(C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\SqlWb.exe.Config )

content here

there may be problem in that

open this file in IExploere.

copy the XML COntent & paste here

|||

Hi,

Thanks for everones help i have now worked out my problem i had a problem with sp1.

kered

Cannot connect to remote SSRS instance with SSMS

I recent installed a named instance of SSRS 2005 on a remote server. The server has a side by side install of SSRS 2000 and SSRS 2005, with the SSRS 2005 being a named instance. The server also has SSL and MS Sharepoint Portal Server installed.

When I try and connect to the SSRS 2005 instance with my client install of Mangement Studio, I get the error message:

"The underlying connection was closed: Could not establish a trust relationship for the SSL/TLS secure channel. (System.Web.Services)

Additional Information: The remote certificate is invalid according to the validation procedure. (System)."

Obviously, this is a SLL issue, but, not being a security guru, I have no clue on how to fix this. I do know the certificate is valid, not expired and properly working. Both installs of SSRS are set up using the SSL certificate. Also, I am not connecting to SSIS with Management Studio, as I heard there is a bug connecting to both SSRS and SSIS at the same time.

Anyone have any ideas?

Thanks!!

Jeff

Moving to the reporting services forum|||

Can you connect to https://<CN name in cert>/reportserver$instancename locally or remotely? Make sure you have correctly set the report server urls in your report server and manager config files. The urls should be in the same format.

http://blogs.msdn.com/bimusings/archive/2006/03/06/544856.aspx#621163

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

|||

Yes, I have the URLs set correctly in the config files.

I am not sure how your reply has anything to do with connecting to the reporting server with SSMS. I can see where your answer will affect connecting with Internet Explorer, but not SSMS.

Can anyone else help please?

Thanks,

Jeff

Cannot connect to remote SSRS instance with SSMS

I recent installed a named instance of SSRS 2005 on a remote server. The server has a side by side install of SSRS 2000 and SSRS 2005, with the SSRS 2005 being a named instance. The server also has SSL and MS Sharepoint Portal Server installed.

When I try and connect to the SSRS 2005 instance with my client install of Mangement Studio, I get the error message:

"The underlying connection was closed: Could not establish a trust relationship for the SSL/TLS secure channel. (System.Web.Services)

Additional Information: The remote certificate is invalid according to the validation procedure. (System)."

Obviously, this is a SLL issue, but, not being a security guru, I have no clue on how to fix this. I do know the certificate is valid, not expired and properly working. Both installs of SSRS are set up using the SSL certificate. Also, I am not connecting to SSIS with Management Studio, as I heard there is a bug connecting to both SSRS and SSIS at the same time.

Anyone have any ideas?

Thanks!!

Jeff

Moving to the reporting services forum|||

Can you connect to https://<CN name in cert>/reportserver$instancename locally or remotely? Make sure you have correctly set the report server urls in your report server and manager config files. The urls should be in the same format.

http://blogs.msdn.com/bimusings/archive/2006/03/06/544856.aspx#621163

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

|||

Yes, I have the URLs set correctly in the config files.

I am not sure how your reply has anything to do with connecting to the reporting server with SSMS. I can see where your answer will affect connecting with Internet Explorer, but not SSMS.

Can anyone else help please?

Thanks,

Jeff

Cannot connect to MSDE on a W2003 server

I have installed MSDE with SP3a with a instance name on a
Windwos Server 2003 Enterprise edition.
The install works fine.
I installed the client software on a W2k en W98 client
PC, the install work fine.
When i run the program, the program normaly sees the
servernaam and instance name.
This do'nt work on the Windows 2003 server. (2000 server
works fine)
Have enyone a idee?* Did you apply the SP3 version of MSDE? If not TCP will be disabled on
Windows 2003. You must apply SP3 before TCP connections (the default from a
remote client) will work.
* What error do you get when you try to connect?
* Do you get the same error from Query Analyzer, OSQL, and Enterprise
Manager or just from your application?
* If you force TCP, named pipes, or shared memory does it start working or
change the error?
* Do both remote and local connections fail for each protocol? For MSDE
2000 SP3 remote connections are disabled by default, you have to enable TCP
and/or named pipes on the server side before remote connections will work.
To Enable TCP/IP Sockets Server Net-Library
1. On the taskbar, click "Start", and then click "Run".
2. In the "Open" text box, type "svrnetcn.exe" (without the quotation
marks). Note: By default, the svrnetcn.exe is available in the
following folder: <Installation Drive>/Program Files/Microsoft SQL
Server/80/Tools/BINN
3. Click "OK".
4. In the "SQL Server Network Utility" dialog box, click "General" tab.
5. Click the desired instance of Microsoft SQL Server 2000 Desktop Engine
(Windows) or MSDE 2000 SP3a or SQL Server 2000 in the
"Instance(s) on this server" list.
6. In the "Disabled Protocols" list box, click "TCP/IP", and then click
"Enable".
7. In the "Enabled Protocols" list box, click "TCP/IP", and then click
"Properties".
8. In the "<Server Name> - TCP/IP" dialog box, in the "Default Port" text
box, type "0" (without the quotation marks), and then click "OK".
9. In the "SQL Server Network Utility" dialog box, click "OK". Note: You
may receive a message stating that the changes made will be saved, but will
take effect only after restarting the SQL Server service. In the "SQL
Server Network Utility" message box, click "OK".
10. Restart the SQL Server service of the instance of Microsoft SQL Server
2000 Desktop Engine (Windows) or MSDE 2000 SP3a or SQL Server 2000.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.

Cannot connect to Database Engine

Hi! I have a little problem and I need your help.

I have recently installed SQL Server 2005 Developer Edition. I did not install all the features, just the Database engine and Analysis Services. I also updated everything with SQL Server SP2.

So far, so good. But when I tried to connect to the Database Engine, I get a little window with the following message:

"Cannot connect to Valentin-PC (server name)."

"Login failed for user - User Name - ( Microsoft SQL Server, Error: 18456 )".

I have tried just about everything, but to no avail. What is strange is the fact that I can connect to the other server type that I have installed (Analysis Services). No connection problems there.

Can anyone help?

Mucho gracias!

Is the db instance local? If not, then you will need to use the Surface Area Configuration Tool to allow remote connections to the database engine. Remote connections are disabled by default.
Tim|||

I made the switch to allow for remote connections as well but still, the problem persists.

Anyway, and excuse my ignorance, how do I find out if the db instance is local or not?

Thanks!

|||

i think there is something wrong in the credential .... check these links

http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx

http://blogs.msdn.com/sql_protocols/archive/2005/10/22/483684.aspx

Madhu

|||

I also went through a nighmare when trying to connect to my instance of SQL 2005 Server. In a nutshell:

1. I downloaded the SQL 2005 Server Management Tools <- Highly recommended

2. I opened the "Server Configuration Manager" (located in the configuration tools folder in the SQL Server 2005 folder), and I enabled TCP/IP in all my network cards.

3. I specify the port 1433 as the one I want the server to listen to

4. I used the "Server Configuration Manager" to allow me to use both Windows and SQL authentication to log on

5. I told the Firewall to back off and let SQL listen to the port 1433

These five points allowed me to establish a connection from within my LAN. However, I did one last test in a Virtual Machine, and to make connection I had to go to the connection properties of my local area connection for my adapter, I went to the "Authentication Tab", and I unchecked all checkboxes... although I am very well aware that this is a serious security risk... but anyway, it was just a test in a Virtual Machine.

I hope it helps!!!!

Tarh Ik

PS: This posting has been posted "AS IS"

|||

I very much appreciate your help, Madhu. Just one question, if you don't mind.

How do I access the server error log?

I checked and looked around in the SQL Server folder but could not find it.

Thanks, anyway.

|||

Thanks for the input, Tarh lk. What is amazing is the fact that one has to go through the TCP/IP

in order to connect to a database installed on a one's own machine! It's like calling long distance

just to talk to someone in your own house!

Some of the settings you suggested were already there. I made the rest of them as well, but still no luck.

Thanks, anyway.

|||

I found the server error log. The message I'm getting is:

"Error Number: 18456."

"Severity: 14"

"State: 1"

"Line Number: 65536"

What does it mean? Can the connection problem be fixed?

Thank you for your time!

|||

Having a 'dash' in the server name makes it an invalid server name. Try putting square brackets around the server name.

[Valentin-PC]

|||

I followed your advice and now I'm getting a different message:

"An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005,

this error may be caused by the fact that under default settings, SQL Server does not allow remote

connections.(provider: Names Pipes Provider, error: 40 - Could not open a connection to SQL Server)

(Microsoft SQL Server, Error: 53)"

Now, just for the sake of it, I went to Surface Area Configuration and checked the settings for Connections.

Both the Database Engine and Analysis Services are set for local connections only.

Go figure!

Thanks, anyway!

|||

this is a common problem ... you need to enable sql server for remote connection..

Ref : http://support.microsoft.com/kb/914277

Madhu

Cannot connect to database

I have SQL Server 2000 Developers Edition install at work and home
machines., I configure as Windows Authentication.
I am using the CASE Tools DBDesigner to connect to SQL Server.
However, I got probelm in connecting to SQL SErver 2000 at home, the
scenario is below:
1)I create a Windows user in Windows 2000 Professional by Control Panel
2)Go to SQL Server Enterprise Manager
3)Goto Security, create Logins
4)Goto Northwind database
5)Add Database User from Users folder
The problem is it works at work machine, but when I do the same at home
machine, I got different things.
At home machine, I got the new user has domain name prefix, it does not
appear in my work machine.
Now, at home machine, I tried to connect from DBDesigner 4, I got the error
something like the login is not associated with trusted login.
Why it was happened like this ?Alan
Try to switch Authentication to SQL Server and Windows.
Connect to SQL Server as 'sa'
"Alan" <NOSPAMalan_pltse@.yahoo.com.au> wrote in message
news:e%23AlYYoTEHA.1548@.TK2MSFTNGP11.phx.gbl...
> I have SQL Server 2000 Developers Edition install at work and home
> machines., I configure as Windows Authentication.
> I am using the CASE Tools DBDesigner to connect to SQL Server.
> However, I got probelm in connecting to SQL SErver 2000 at home, the
> scenario is below:
> 1)I create a Windows user in Windows 2000 Professional by Control Panel
> 2)Go to SQL Server Enterprise Manager
> 3)Goto Security, create Logins
> 4)Goto Northwind database
> 5)Add Database User from Users folder
> The problem is it works at work machine, but when I do the same at home
> machine, I got different things.
> At home machine, I got the new user has domain name prefix, it does not
> appear in my work machine.
> Now, at home machine, I tried to connect from DBDesigner 4, I got the
error
> something like the login is not associated with trusted login.
> Why it was happened like this ?
>|||What is the exact error you are getting?
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Sorry for late reply.
Now I need to list my details of my work machine SQL Server Developer
editions within Enterprise Manager:
- Use Windows authentication
- I add one login eg. 'bbb', password with 'bbb' from Security|Logins
I have NOT added user in Northwind database yet.
Now leave Enterprise Manager.
Goto DBDesigner 4, select the option reverse engineering, select the
connection to Northwind database, type in 'bbb' with password 'bbb'.
Magic is coming out: DBDesigner can reengineer the logical database
structure for me.
This is so far so good in my working place machine.
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message
news:W4ql$9uTEHA.304@.cpmsftngxa10.phx.gbl...
> What is the exact error you are getting?
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>

Cannot connect to database

I have SQL Server 2000 Developers Edition install at work and home
machines., I configure as Windows Authentication.
I am using the CASE Tools DBDesigner to connect to SQL Server.
However, I got probelm in connecting to SQL SErver 2000 at home, the
scenario is below:
1)I create a Windows user in Windows 2000 Professional by Control Panel
2)Go to SQL Server Enterprise Manager
3)Goto Security, create Logins
4)Goto Northwind database
5)Add Database User from Users folder
The problem is it works at work machine, but when I do the same at home
machine, I got different things.
At home machine, I got the new user has domain name prefix, it does not
appear in my work machine.
Now, at home machine, I tried to connect from DBDesigner 4, I got the error
something like the login is not associated with trusted login.
Why it was happened like this ?Alan
Try to switch Authentication to SQL Server and Windows.
Connect to SQL Server as 'sa'
"Alan" <NOSPAMalan_pltse@.yahoo.com.au> wrote in message
news:e%23AlYYoTEHA.1548@.TK2MSFTNGP11.phx.gbl...
> I have SQL Server 2000 Developers Edition install at work and home
> machines., I configure as Windows Authentication.
> I am using the CASE Tools DBDesigner to connect to SQL Server.
> However, I got probelm in connecting to SQL SErver 2000 at home, the
> scenario is below:
> 1)I create a Windows user in Windows 2000 Professional by Control Panel
> 2)Go to SQL Server Enterprise Manager
> 3)Goto Security, create Logins
> 4)Goto Northwind database
> 5)Add Database User from Users folder
> The problem is it works at work machine, but when I do the same at home
> machine, I got different things.
> At home machine, I got the new user has domain name prefix, it does not
> appear in my work machine.
> Now, at home machine, I tried to connect from DBDesigner 4, I got the
error
> something like the login is not associated with trusted login.
> Why it was happened like this ?
>|||What is the exact error you are getting?
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Sorry for late reply.
Now I need to list my details of my work machine SQL Server Developer
editions within Enterprise Manager:
- Use Windows authentication
- I add one login eg. 'bbb', password with 'bbb' from Security|Logins
I have NOT added user in Northwind database yet.
Now leave Enterprise Manager.
Goto DBDesigner 4, select the option reverse engineering, select the
connection to Northwind database, type in 'bbb' with password 'bbb'.
Magic is coming out: DBDesigner can reengineer the logical database
structure for me.
This is so far so good in my working place machine.
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message
news:W4ql$9uTEHA.304@.cpmsftngxa10.phx.gbl...
> What is the exact error you are getting?
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>

Cannot connect to database

I have SQL Server 2000 Developers Edition install at work and home
machines., I configure as Windows Authentication.
I am using the CASE Tools DBDesigner to connect to SQL Server.
However, I got probelm in connecting to SQL SErver 2000 at home, the
scenario is below:
1)I create a Windows user in Windows 2000 Professional by Control Panel
2)Go to SQL Server Enterprise Manager
3)Goto Security, create Logins
4)Goto Northwind database
5)Add Database User from Users folder
The problem is it works at work machine, but when I do the same at home
machine, I got different things.
At home machine, I got the new user has domain name prefix, it does not
appear in my work machine.
Now, at home machine, I tried to connect from DBDesigner 4, I got the error
something like the login is not associated with trusted login.
Why it was happened like this ?
Alan
Try to switch Authentication to SQL Server and Windows.
Connect to SQL Server as 'sa'
"Alan" <NOSPAMalan_pltse@.yahoo.com.au> wrote in message
news:e%23AlYYoTEHA.1548@.TK2MSFTNGP11.phx.gbl...
> I have SQL Server 2000 Developers Edition install at work and home
> machines., I configure as Windows Authentication.
> I am using the CASE Tools DBDesigner to connect to SQL Server.
> However, I got probelm in connecting to SQL SErver 2000 at home, the
> scenario is below:
> 1)I create a Windows user in Windows 2000 Professional by Control Panel
> 2)Go to SQL Server Enterprise Manager
> 3)Goto Security, create Logins
> 4)Goto Northwind database
> 5)Add Database User from Users folder
> The problem is it works at work machine, but when I do the same at home
> machine, I got different things.
> At home machine, I got the new user has domain name prefix, it does not
> appear in my work machine.
> Now, at home machine, I tried to connect from DBDesigner 4, I got the
error
> something like the login is not associated with trusted login.
> Why it was happened like this ?
>
|||What is the exact error you are getting?
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Sorry for late reply.
Now I need to list my details of my work machine SQL Server Developer
editions within Enterprise Manager:
- Use Windows authentication
- I add one login eg. 'bbb', password with 'bbb' from Security|Logins
I have NOT added user in Northwind database yet.
Now leave Enterprise Manager.
Goto DBDesigner 4, select the option reverse engineering, select the
connection to Northwind database, type in 'bbb' with password 'bbb'.
Magic is coming out: DBDesigner can reengineer the logical database
structure for me.
This is so far so good in my working place machine.
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message
news:W4ql$9uTEHA.304@.cpmsftngxa10.phx.gbl...
> What is the exact error you are getting?
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>