connect from ASP app: ive

Showing posts with label ive. Show all posts

Thursday, March 8, 2012

Can't create Primary Key??

Hi Guy's
I've migrated an access DB of ours over to SQL 2000 and when I try to set
the primary key I get the error below. I've checked for and deleted all of
the other indexes so i'm not sure why it says a duplicate was found. I have
some other tables in the Database which I was able to set a primary key on
but this table chokes each time. Help I'm stuck!
'Master' table
- Unable to create index 'PK_Master'.
ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]CREATE UNIQUE
INDEX terminated because a duplicate key was found for index ID 1. Most
significant primary key is 'type 6c, len 9'.
[Microsoft][ODBC SQL Server Driver][SQL Server]Could not create constraint.
See previous errors.
[Microsoft][ODBC SQL Server Driver][SQL Server]The statement has been
terminated.
Rob
IT guy!
Assuming your PK is compreised of columns Col1 and Col2, run the following:
select
Col1
, Col2
, count (*)
from
MyTable
group by
Col1
, Col2
having
count (*) > 1
This will reveal the duplicates.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"Rob" <Rob@.discussions.microsoft.com> wrote in message
news:AA6A9681-B871-4E70-BF9B-6B5A10B74DCE@.microsoft.com...
Hi Guy's
I've migrated an access DB of ours over to SQL 2000 and when I try to set
the primary key I get the error below. I've checked for and deleted all of
the other indexes so i'm not sure why it says a duplicate was found. I have
some other tables in the Database which I was able to set a primary key on
but this table chokes each time. Help I'm stuck!
'Master' table
- Unable to create index 'PK_Master'.
ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]CREATE UNIQUE
INDEX terminated because a duplicate key was found for index ID 1. Most
significant primary key is 'type 6c, len 9'.
[Microsoft][ODBC SQL Server Driver][SQL Server]Could not create constraint.
See previous errors.
[Microsoft][ODBC SQL Server Driver][SQL Server]The statement has been
terminated.
Rob
IT guy!
|||Assuming your PK is comprised of columns Col1 and Col2, run the following:
select
Col1
, Col2
, count (*)
from
MyTable
group by
Col1
, Col2
having
count (*) > 1
This will reveal the duplicates.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"Rob" <Rob@.discussions.microsoft.com> wrote in message
news:AA6A9681-B871-4E70-BF9B-6B5A10B74DCE@.microsoft.com...
Hi Guy's
I've migrated an access DB of ours over to SQL 2000 and when I try to set
the primary key I get the error below. I've checked for and deleted all of
the other indexes so i'm not sure why it says a duplicate was found. I have
some other tables in the Database which I was able to set a primary key on
but this table chokes each time. Help I'm stuck!
'Master' table
- Unable to create index 'PK_Master'.
ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]CREATE UNIQUE
INDEX terminated because a duplicate key was found for index ID 1. Most
significant primary key is 'type 6c, len 9'.
[Microsoft][ODBC SQL Server Driver][SQL Server]Could not create constraint.
See previous errors.
[Microsoft][ODBC SQL Server Driver][SQL Server]The statement has been
terminated.
Rob
IT guy!
|||Tom,
I try running the query but it times out. The table is quite large.
"Tom Moreau" wrote:

> Assuming your PK is comprised of columns Col1 and Col2, run the following:
> select
> Col1
> , Col2
> , count (*)
> from
> MyTable
> group by
> Col1
> , Col2
> having
> count (*) > 1
> This will reveal the duplicates.
> --
> Tom
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Rob" <Rob@.discussions.microsoft.com> wrote in message
> news:AA6A9681-B871-4E70-BF9B-6B5A10B74DCE@.microsoft.com...
> Hi Guy's
> I've migrated an access DB of ours over to SQL 2000 and when I try to set
> the primary key I get the error below. I've checked for and deleted all of
> the other indexes so i'm not sure why it says a duplicate was found. I have
> some other tables in the Database which I was able to set a primary key on
> but this table chokes each time. Help I'm stuck!
> 'Master' table
> - Unable to create index 'PK_Master'.
> ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]CREATE UNIQUE
> INDEX terminated because a duplicate key was found for index ID 1. Most
> significant primary key is 'type 6c, len 9'.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Could not create constraint.
> See previous errors.
> [Microsoft][ODBC SQL Server Driver][SQL Server]The statement has been
> terminated.
> --
> Rob
> IT guy!
>
|||> I try running the query but it times out.
Where did you try running it? I suggest usng Query Analyzer, not Enterprise
Manager. You might also try
...
FROM MyTable WITH (NOLOCK)
...
http://www.aspfaq.com/
(Reverse address to reply.)
|||Rob,
Try
select
Col1
, Col2
, count (*)
from
MyTable
where Col1 = 'type 6c, len 9'
group by
Col1
, Col2
having
count (*) > 1
This assumes that Col1 is the initial column of PK_master, the primary
key you are trying to set, since this value was provided in the error
message.
Steve Kass
Drew University
Rob wrote:
[vbcol=seagreen]
>Tom,
>I try running the query but it times out. The table is quite large.
>"Tom Moreau" wrote:
>
|||You probably have no indexes on the table yet. Run it through QA and let it
finish.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"Rob" <Rob@.discussions.microsoft.com> wrote in message
news:1960D77C-C7C8-40C7-B927-6FC1360C26DC@.microsoft.com...
Tom,
I try running the query but it times out. The table is quite large.
"Tom Moreau" wrote:

> Assuming your PK is comprised of columns Col1 and Col2, run the following:
> select
> Col1
> , Col2
> , count (*)
> from
> MyTable
> group by
> Col1
> , Col2
> having
> count (*) > 1
> This will reveal the duplicates.
> --
> Tom
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "Rob" <Rob@.discussions.microsoft.com> wrote in message
> news:AA6A9681-B871-4E70-BF9B-6B5A10B74DCE@.microsoft.com...
> Hi Guy's
> I've migrated an access DB of ours over to SQL 2000 and when I try to set
> the primary key I get the error below. I've checked for and deleted all of
> the other indexes so i'm not sure why it says a duplicate was found. I
have
> some other tables in the Database which I was able to set a primary key on
> but this table chokes each time. Help I'm stuck!
> 'Master' table
> - Unable to create index 'PK_Master'.
> ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]CREATE UNIQUE
> INDEX terminated because a duplicate key was found for index ID 1. Most
> significant primary key is 'type 6c, len 9'.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Could not create
constraint.
> See previous errors.
> [Microsoft][ODBC SQL Server Driver][SQL Server]The statement has been
> terminated.
> --
> Rob
> IT guy!
>

Sunday, February 19, 2012

Cant connect to SQL Server 2005 in Visual Studio, only SQLExpress works?

Hi all,

I'm having a big problem here. I can't seem to connect to a database of MSSQL Server 2005... Here is what I've did:

1. Under the Server Explorer>Data Connections. Right click and choose "Add Connection..."

2. Data Source was "Microsoft SQL Server Database File". Click OK.

3. I browse to the database in the MSSQL.2/MSSQL/Data folder.

4. Click on the "Advanced" button, and change the default DataSource from .\SQLEXPRESS to .\MSSQLSERVER. Click OK

5. Received this error:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default setting SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 25 - Connection string is not valid)

Only .\SQEXPRESS that I was able to connect to... i've tried the solution from Microsoft, opened SQL Server 2005 Surface Area Configuration and enabled "Local and remote connections", checked the option "Using both TCP/IP and named pipes" but it didn't help. This is frustrating because I can't get the Membership provider, login to work on my host. Please help.

Thank you very much,

Kenny.

Hi Kenny,

xuanvu:
Click on the "Advanced" button, and change the default DataSource from .\SQLEXPRESS to .\MSSQLSERVER. Click OK

is there named instance MSSQLSERVER on your host/machine

xuanvu:
Data Source was "Microsoft SQL Server Database File". Click OK.

wondering what did you chose while creating connection for SQLExpress was it Sql Server Database file or SQL Server. could you try to use SQL Server option for .\MSSQLServer?

thanks,

satish.

|||

Yeap the problem lies in the SQL Server instance name... I was able to connect to the database now, but here is the problem that I've been battled for a whole week without success... Reading countless forum for a solution but none seems to work.

Here is the problem that I've posted: http://forums.asp.net/t/1131239.aspx

Thanks,

Kenny.

Can't connect to sql server 2005 after sysprep

I've installed sql2005 on win2k3, running on virtual pc... I can connect to
the sql server using sql server management studio... Because I'm building
base environment for testing, I seal the machine using sysprep. When I start
a new machine, I get this error...
"A connection was successfully established with the server, but then an
error occurred during the pre-login handshake. (provider: Shraed Memory
Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft
SQL Server, Error: 233)
Any idea how to solve this?
Best Regards,
Kit Kai
MVP (asp.net)
SgDotNet Council Member
Visit us @. http://www.sgdotnet.org
My Blog: http://community.sgdotnet.org/blogs/kitkai
Hi Loke,
Welcome to use MSDN Managed Newsgroup!
From your descriptions, I understood you setup a machine with SQL Server
2005 and after using sysprep (something like GHOST, am I right?), the SQL
Server report the error message 233. If I have misunderstood your concern,
please feel free to point it out.
Since you are using sysprep, does the machine name remains the same? Please
perform the steps below and let me knwo whether it resolved your issue.
1. Open SQL Server Surface Area Configuration
Click 'Surface Area Configuration for Services and Connections'
Extend Database Engine and make sure Remote Connections is enabled for
both TCP/IP and named pipes.
2. Restart the SQL Server
3. Make sure the Firewall is configured correctly.
Sincerely yours,
Michael Cheng
Microsoft Online Partner 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.
|||Yup... You understood my problem perfectly.
In this case, the machine name remains the same, but this would be the only
case where the machine name remains the same... Basically, this setup will
be used as a base for other differentiating disk to build upon.
I've followed your steps, but the problem still remains. Firewall shouldn't
be the cause, since I'm still access sql using the same machine...
Best Regards,
Kit Kai
MVP (asp.net)
SgDotNet Council Member
Visit us @. http://www.sgdotnet.org
My Blog: http://community.sgdotnet.org/blogs/kitkai
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:7nDahdh%23FHA.1236@.TK2MSFTNGXA02.phx.gbl...
> Hi Loke,
> Welcome to use MSDN Managed Newsgroup!
> From your descriptions, I understood you setup a machine with SQL Server
> 2005 and after using sysprep (something like GHOST, am I right?), the SQL
> Server report the error message 233. If I have misunderstood your concern,
> please feel free to point it out.
> Since you are using sysprep, does the machine name remains the same?
> Please
> perform the steps below and let me knwo whether it resolved your issue.
> 1. Open SQL Server Surface Area Configuration
> Click 'Surface Area Configuration for Services and Connections'
> Extend Database Engine and make sure Remote Connections is enabled for
> both TCP/IP and named pipes.
> 2. Restart the SQL Server
> 3. Make sure the Firewall is configured correctly.
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner 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.
>
|||Hi Kit,
This is a very strange issue. Unfortunately, I am afraid it is not
supported to install SQL Server 2005 like this due to license issues. Would
you please completely uninstall SQL Server 2005 and then reinstall it to
see whether you could login SQL Server 2005 this time?
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner 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.
|||Found the solution with Sukhdev's help.
Posted it @.
http://community.sgdotnet.org/blogs/.../13/23344.aspx
Best Regards,
Kit Kai
MVP (asp.net)
SgDotNet Council Member
Visit us @. http://www.sgdotnet.org
My Blog: http://community.sgdotnet.org/blogs/kitkai
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:Tx%23OqCx%23FHA.3764@.TK2MSFTNGXA02.phx.gbl...
> Hi Kit,
> This is a very strange issue. Unfortunately, I am afraid it is not
> supported to install SQL Server 2005 like this due to license issues.
> Would
> you please completely uninstall SQL Server 2005 and then reinstall it to
> see whether you could login SQL Server 2005 this time?
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner 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.
>
|||Hi Kit,
Thanks so much for the update and share this invaluable experience here. I
believe other communities will also benefit much from this.
Sincerely yours,
Michael Cheng
Microsoft Online Partner 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.

Can't connect to SQL Server 2000 with Visual Studio 2005

I've been using Delphi for years (Win 32) and connecting to my SQL Server
databases with no problem.
I am now trying to learn both VB and C#. (Visual studio 2005)
From the Data menu, I select Add New Data Source
I then choose Database
I select Microsoft SQL Server as the Data Source
The Add Connection Dialog appears
It populates the Server name dropdown with both of my SQL servers.
However, when I try to select a database name, the dropdown is never
populated.
If I manually enter a known database name and try to connect, I get a
TimeOut Expired (or server not responding) error.
This happens whether I use windows authentication or SQL server
authentication.
This drill works fine with Delphi (Win 32) and connects without a hitch.
Any help would be appreciated.
Regards,
Dave
Take a look at my connecting whitepaper on my blog. It lays down the basics.
I expect the rights are not setup correctly or you've chosen a server
instance that's not visible on the network.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Dave Davis" <online@.blindsided.org> wrote in message
news:uvZV0Qt3HHA.4400@.TK2MSFTNGP06.phx.gbl...
> I've been using Delphi for years (Win 32) and connecting to my SQL Server
> databases with no problem.
> I am now trying to learn both VB and C#. (Visual studio 2005)
> From the Data menu, I select Add New Data Source
> I then choose Database
> I select Microsoft SQL Server as the Data Source
> The Add Connection Dialog appears
> It populates the Server name dropdown with both of my SQL servers.
> However, when I try to select a database name, the dropdown is never
> populated.
> If I manually enter a known database name and try to connect, I get a
> TimeOut Expired (or server not responding) error.
> This happens whether I use windows authentication or SQL server
> authentication.
> This drill works fine with Delphi (Win 32) and connects without a hitch.
> Any help would be appreciated.
> Regards,
> Dave
>
|||Bill,
Remember, I connect without any problems using Borland's Delphi. I have for
years.
I also connect with no problems using ASP.
If the rights aren't setup properly or the instance wasn't visible on the
network it seems to me that I couldn't connect with anything.
Or, does .net require different rights or something else different in the
SQL server setup?
Thanks,
Dave
"William Vaughn" <billvaNoSPAM@.betav.com> wrote in message
news:elZYHTv3HHA.1484@.TK2MSFTNGP06.phx.gbl...
> Take a look at my connecting whitepaper on my blog. It lays down the
> basics. I expect the rights are not setup correctly or you've chosen a
> server instance that's not visible on the network.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant, Dad, Grandpa
> Microsoft MVP
> INETA Speaker
> www.betav.com
> www.betav.com/blog/billva
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "Dave Davis" <online@.blindsided.org> wrote in message
> news:uvZV0Qt3HHA.4400@.TK2MSFTNGP06.phx.gbl...
>

Can't connect to SQL Server (developer edition) from another PC?

I've installed SQL Server 2000 Developer Edition on a Windows XP Pro
SP2 machine. It's installed without any problems.
When I try to connect to it from another XP SP2 machine (by creating
an ODBC data source) I get a Login error:
[ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen(Connect()).
Connection failed: SQLState: 08001 SQL Server Error: 17
SQL Server does not exist or access denied
I can ping the server fine from the other machine, and I've tried the
standard "sa" user/pw as welll as my own logins.
The server is configured for mixed authentication (Windows/SQL
Server).
Can anyone suggest what the problem might be?
TIA for any help
Ian
Are you running XP firewall on that machine? If so, turn it off and any
other firewall (Norton Internet Security, etc).
Chris
"ITM" <itm@.nospam.com> wrote in message
news:te7r31d7sh1bof34mmpcegt5p151jc87ac@.4ax.com...
> I've installed SQL Server 2000 Developer Edition on a Windows XP Pro
> SP2 machine. It's installed without any problems.
> When I try to connect to it from another XP SP2 machine (by creating
> an ODBC data source) I get a Login error:
> [ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen(Connect()).
> Connection failed: SQLState: 08001 SQL Server Error: 17
> SQL Server does not exist or access denied
> I can ping the server fine from the other machine, and I've tried the
> standard "sa" user/pw as welll as my own logins.
> The server is configured for mixed authentication (Windows/SQL
> Server).
> Can anyone suggest what the problem might be?
> TIA for any help
> Ian
|||On Sun, 20 Mar 2005 08:59:30 -0800, "Chris Schmidt"
<schmidtc@.KvalleyDotCom> wrote:

>Are you running XP firewall on that machine? If so, turn it off and any
>other firewall (Norton Internet Security, etc).
>Chris
>"ITM" <itm@.nospam.com> wrote in message
>news:te7r31d7sh1bof34mmpcegt5p151jc87ac@.4ax.com.. .
>
I've tried turning off XP firewall but it made no difference. I'm not
running Norton, but am using AVG anti-virus (free edition). No other
firewall/AV software installed.
Ian
|||What happens when you telnet to port 1433 on that machine (or whatever port
you're running it on)?
Chris
"ITM" <itm@.nospam.com> wrote in message
news:0qbr315sngsoq0eh8eook7v1t5k3d5bcsr@.4ax.com...
> On Sun, 20 Mar 2005 08:59:30 -0800, "Chris Schmidt"
> <schmidtc@.KvalleyDotCom> wrote:
> I've tried turning off XP firewall but it made no difference. I'm not
> running Norton, but am using AVG anti-virus (free edition). No other
> firewall/AV software installed.
> Ian
|||On Sun, 20 Mar 2005 09:41:09 -0800, "Chris Schmidt"
<schmidtc@.KvalleyDotCom> wrote:

>What happens when you telnet to port 1433 on that machine (or whatever port
>you're running it on)?
>Chris
>"ITM" <itm@.nospam.com> wrote in message
>news:0qbr315sngsoq0eh8eook7v1t5k3d5bcsr@.4ax.com.. .
>
Have just downloaded and installed SP3 for SQL Server - it seems to
have done the trick. Should've tried that before :-(

Thursday, February 16, 2012

can't connect to SQL 6.5 server in different domain

Is there any trick to setting up a System DSN to connect to a SQL 6.5 Sever that is in a different domain. The domains are trusted. I've tried every type of authentication but my Win XP system just can't get a DSN to connect again the SQL Server that is running Win NT4 SP6. Is there a trick?
Thanks,
Chuck
Hi,
Can you create a alias name using "CLIENT NETWORK UTILITY" from your WIN XP System by providing the
1. Protocol as TCP/IP
2. Provide the SQL 6.5 IP address
3. Define the Port number
Then use the ALIAS server name to connect.
Thanks
Hari
SQL Server MVP
"Charles MacLean" <charlesmaclean@.sbcglobal.net> wrote in message news:ziWkd.18733$Rf1.10698@.newssvr19.news.prodigy. com...
Is there any trick to setting up a System DSN to connect to a SQL 6.5 Sever that is in a different domain. The domains are trusted. I've tried every type of authentication but my Win XP system just can't get a DSN to connect again the SQL Server that is running Win NT4 SP6. Is there a trick?
Thanks,
Chuck
|||If SQL Server 6.5 is set to use Windows only authentication, this will not
work. With SQL Server 6.5 NT authentication only works with named pipes.
Also by default SQL Server 6.5 does not enable TCP/IP. It has to be done
after setup. So use SQL Server setup to see if tcp/ip is enabled. Then set
SQL Server to use mixed security and then configure your DSN to use SQL
authentication. This is just a test to see if you can connect. With this
configuration the alias that Hari suggests should work.
What error are you getting when you try to connect?
Rand
This posting is provided "as is" with no warranties and confers no rights.

Tuesday, February 14, 2012

Cant connect to my SQLExpress Instance

Hello guys,

I've got some troubles , by attempting to connect the SQL Server database to my server.

I've got this error message on the SQL Configuration Manager (when i tried to start SQL Server which was stopped) " The request failed or the service did not respond in a timely fashion.Consult the event log or the other applicable error logs for details "

I found that error log :

2007-12-18 19:36:12.20 Server Server process ID is 5080.
2007-12-18 19:36:12.20 Server Logging SQL Server messages in file'c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2007-12-18 19:36:12.20 Server This instance of SQL Server last reportedusing a process ID of 1180 at 18/12/2007 19:12:20 (local) 18/12/200719:12:20 (UTC). This is an informational message only; no user actionis required.
2007-12-18 19:36:12.20 Server Registry startup parameters:
2007-12-18 19:36:12.20 Server -d c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2007-12-18 19:36:12.20 Server -e c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2007-12-18 19:36:12.20 Server -l c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2007-12-18 19:36:12.20 Server SQL Server is starting at normal prioritybase (=7). This is an informational message only. No user action isrequired.
2007-12-18 19:36:12.20 Server Detected 2 CPUs. This is an informational message; no user action is required.
2007-12-18 19:36:12.40 Server Using dynamic lock allocation. Initialallocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.This is an informational message only. No user action is required.
2007-12-18 19:36:12.42 Server Database Mirroring Transport is disabled in the endpoint configuration.
2007-12-18 19:36:12.43 spid4s Starting up database 'master'.
2007-12-18 19:36:12.50 spid4s Error: 9003, Severity: 20, State: 1.
2007-12-18 19:36:12.50 spid4s The log scan number (228:88:1) passed tolog scan in database 'master' is not valid. This error may indicatedata corruption or that the log file (.ldf) does not match the datafile (.mdf). If this error occurred during replication, re-create thepublication. Otherwise, restore from backup if the problem results in afailure during startup.
2007-12-18 19:36:12.50 spid4s Cannot recover the master database. SQLServer is unable to run. Restore master from a full backup, repair it,or rebuild it. For more information about how to rebuild the masterdatabase, see SQL Server Books Online.

I'm on it since this morning and i haven't been able to fix it , none of the web ressources helped me you're my last chance of sleeping tightly :'(

Thank you so much.

Amokrane CHENTIR

welcome to the forums,

after reading the logfile, i think the Master database is damaged , note that SQL server can't work wothout this database .

you need to re-install the Sqlserver , or repair the installation , go to add/remove programs from control panel ,

and repair the SQl server Express Installation.

|||

Thank you very much , i've just tried it and it worked :)

Sunday, February 12, 2012

Can't connect to MSDE

I've got two machines: 1) SBS 2003 Server, and 2) WinXP Pro.
SQL Server 2000 is installed on the server box, as well as MSDE for the default
SharePoint and SbsMonitoring databases (SBS setup created those). The
workstation is running MSDE.
The problem is that I can only connect to the workstation's MSDE from the
workstation. EM on the server can see the MSDE instance (the worksation's
machine name appears in the Add SQL Server Registration dialog box), but that's
as far as it can get. When I try to add the instance under a new registration, I
get 'access denied or server doesn't exist' (paraphrased).
I also can't connect via EM to the workstation's MSDE from within a Win98
VirtualPC instance running on the workstation, although I can connect to the
server's instances (both SQL Server and MSDE instances) from within that
instance.
I've compared the property sheets of all the instances to which I can connect
from WinXP, and everything seems to be the same. Nothing shows up in my ISA
logs, so I don't think packets are being blocked. Just in case I created a
temporary packet filter allowing all packets from anywhere (risky, I know), but
it still didn't work. Still nothing in the logs.
Does anyone know what this might be?
TIA,
Jeff
By default MSDE doesn't listen to any netlibs. On a regular SQL Server, you configure this using
"Server Network Utility". I'm not sure whether such comes with MSDE, but that would be the place to
start. The name of the exe is svrnetcn.exe
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Jeff Bowman" <write.to.me@.my.addess.com> wrote in message
news:%23Sv%23zABjFHA.3164@.TK2MSFTNGP15.phx.gbl...
> I've got two machines: 1) SBS 2003 Server, and 2) WinXP Pro.
> SQL Server 2000 is installed on the server box, as well as MSDE for the default SharePoint and
> SbsMonitoring databases (SBS setup created those). The workstation is running MSDE.
> The problem is that I can only connect to the workstation's MSDE from the workstation. EM on the
> server can see the MSDE instance (the worksation's machine name appears in the Add SQL Server
> Registration dialog box), but that's as far as it can get. When I try to add the instance under a
> new registration, I get 'access denied or server doesn't exist' (paraphrased).
> I also can't connect via EM to the workstation's MSDE from within a Win98 VirtualPC instance
> running on the workstation, although I can connect to the server's instances (both SQL Server and
> MSDE instances) from within that instance.
> I've compared the property sheets of all the instances to which I can connect from WinXP, and
> everything seems to be the same. Nothing shows up in my ISA logs, so I don't think packets are
> being blocked. Just in case I created a temporary packet filter allowing all packets from anywhere
> (risky, I know), but it still didn't work. Still nothing in the logs.
> Does anyone know what this might be?
> TIA,
> Jeff
>
>
|||That did the trick, thanks for the tip! :-)
(BTW, Server Network Utility appears to be installed with Client Tools.)
Tibor Karaszi wrote:[vbcol=seagreen]
> By default MSDE doesn't listen to any netlibs. On a regular SQL Server, you
> configure this using "Server Network Utility". I'm not sure whether such
> comes with MSDE, but that would be the place to start. The name of the exe is
> svrnetcn.exe
> "Jeff Bowman" <write.to.me@.my.addess.com> wrote in message
> news:%23Sv%23zABjFHA.3164@.TK2MSFTNGP15.phx.gbl...

Cant connect to membership provider db

I've started developing an ASP.net 2.0 app with VWD Express.

The default membership provider db of SQL Server 5005 Express is not installed on my host servers. So my workaround has been to use a Full blown SQL Server 2005 DB as a custom membership provider declared in web.config.

This works fine on the production server. However, when i try to login from my development app I get Exception # 40 can't connect to SQL server membership provider.. Moreover, my app configuration confirms there is problems connecting to this server in my development environment.

How can I solve this and bring my development app up & running again?

many thanks

If you have access to your Production SQL Server from your development environment, the problem is probably due to your connection string.

For my development, I use SQL Express on my local development box and SQL Server for production. There are two things that you have to do. Keeps separate scripts for changes to the database (from development to production). In addition, a separate web.config for production and development to hold your connection strings.

Friday, February 10, 2012

Can't connect to Access project

I've given a copy of Access project to user (win2000prof) but not able to
connect to SQL server on remote server.
SQL driver in use on client is 3.70.09.61 - this gives error DBNMPNTM
specified SQL server not found.
On my PC ( XP and SQL driver 2000.85.1117.00 ) it connects with same login
details.
Can I just download updated version or do I need SQL client software
installed on PC?
Thanks
Try updating the MDAC version on the Windows 2000 client.
You can verify MDAC versions with the component checker. You
can download component checker and MDAC versions from:
http://msdn.microsoft.com/data/mdac/...s/default.aspx
-Sue
On Tue, 9 Aug 2005 07:21:04 -0700, lindab
<lindab@.discussions.microsoft.com> wrote:

>I've given a copy of Access project to user (win2000prof) but not able to
>connect to SQL server on remote server.
>SQL driver in use on client is 3.70.09.61 - this gives error DBNMPNTM
>specified SQL server not found.
>On my PC ( XP and SQL driver 2000.85.1117.00 ) it connects with same login
>details.
>Can I just download updated version or do I need SQL client software
>installed on PC?
>Thanks

Can't connect remotely to MSDE 2000 DB on WinXP Home Machine

Hi All
Having 'Google-ised' I've found that there does appear to be a problem
connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN), but
I haven't found what the concrete solution is.
It definitely appears to be a Windows inflicted problem, as I can connect to
the DB no problem if I create and connect to the ODBC DSN on the same
machine as the MSDE installation and if I use a remote Apple Mac machine to
connect to it via a combo of a router program and the local ODBC DSN then it
works fine.
I have also eliminated the other possibilities by disabling all of the
firewalls (ie Windows' own and Norton) and ultimately when I put the full
blown version of SQL Server on the same machine the remote connection works
perfectly.
Looking through the sites it appears that you have to put
DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
queries are:
Is it a problem with the original MSDE 2000 installer being installed on a
WinXP SP2 machine or just a later version, ie MSDE SP3?
Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
SP1?
Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE 2000
installer or do you have to update it to Service Pack 3 to perform this
task?
Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
Is there anyway of patching/fixing this installation to correct it or have I
got to de-tach the DBs and re-install MSDE with this
DISABLENETWORKPROTOCOLS=0 switch in the ini?
Thanks
Hi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/de...stsql_84xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>
|||Hi John
My version of MSDE is:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
But I still can't get a remote LAN or WAN machine to connect to my MSDE
installation. It still says SQL Server does not exist or access denied,
even though local machine use is fine and I have no firewall security on to
block it.
I've even run the Server Network Utility (svrnetcn.exe) that you suggested
and found that Named Pipes and TCP/IP are already enabled and ready to go.
What am I doing wrong?
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:O6Rcs%237jFHA.2644@.TK2MSFTNGP09.phx.gbl...
Hi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/de...stsql_84xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>
|||I've just checked the log and it still doesn't state that it's using TCP/IP
even though the network util only has TCP/IP in the right-hand box:
2005-07-25 18:42:40.29 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2005-07-25 18:42:40.60 server SQL Server configured for thread mode
processing.
2005-07-25 18:42:40.60 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2005-07-25 18:42:40.62 spid3 Starting up database 'master'.
2005-07-25 18:42:41.04 server Using 'SSNETLIB.DLL' version '8.0.194'.
2005-07-25 18:42:41.07 spid5 Starting up database 'model'.
2005-07-25 18:42:41.12 spid3 Server name is 'FREDPC'.
2005-07-25 18:42:41.12 spid3 Skipping startup of clean database id 4
2005-07-25 18:42:41.12 spid3 Skipping startup of clean database id 5
2005-07-25 18:42:41.35 spid5 Clearing tempdb database.
2005-07-25 18:42:42.54 spid5 Starting up database 'tempdb'.
2005-07-25 18:42:42.65 spid3 Recovery complete.
2005-07-25 18:42:56.09 server SQL server listening on Shared Memory,
Named Pipes. <<<<
2005-07-25 18:42:56.09 server SQL Server is ready for client connections
2005-07-25 18:43:17.17 spid51 Starting up database 'DemoData'.
2005-07-25 19:08:22.85 spid3 SQL Server is terminating due to 'stop'
request from Service Control Manager.
What am I doing wrong?
"Macsicarr" <No3@.Spam67.com> wrote in message
news:ulbflFUkFHA.3164@.TK2MSFTNGP15.phx.gbl...
Hi John
My version of MSDE is:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
But I still can't get a remote LAN or WAN machine to connect to my MSDE
installation. It still says SQL Server does not exist or access denied,
even though local machine use is fine and I have no firewall security on to
block it.
I've even run the Server Network Utility (svrnetcn.exe) that you suggested
and found that Named Pipes and TCP/IP are already enabled and ready to go.
What am I doing wrong?
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:O6Rcs%237jFHA.2644@.TK2MSFTNGP09.phx.gbl...
Hi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/de...stsql_84xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>
|||Hi
You need to make sure that TCP/IP is in the client protocols (using the
client network configuration utitilty on the client) as well as on the
server. You may want to try pinging the server from the client. If it
responds try using telnet to connect to the port you are using (the
default port is 1433).
You @.@.VERSION shows that no patches or service packs have been
installed. http://www.sqlsecurity.com/DesktopDe...aspx?tabid=37.
John

Can't connect remotely to MSDE 2000 DB on WinXP Home Machine

Hi All
Having 'Google-ised' I've found that there does appear to be a problem
connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN), but
I haven't found what the concrete solution is.
It definitely appears to be a Windows inflicted problem, as I can connect to
the DB no problem if I create and connect to the ODBC DSN on the same
machine as the MSDE installation and if I use a remote Apple Mac machine to
connect to it via a combo of a router program and the local ODBC DSN then it
works fine.
I have also eliminated the other possibilities by disabling all of the
firewalls (ie Windows' own and Norton) and ultimately when I put the full
blown version of SQL Server on the same machine the remote connection works
perfectly.
Looking through the sites it appears that you have to put
DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
queries are:
Is it a problem with the original MSDE 2000 installer being installed on a
WinXP SP2 machine or just a later version, ie MSDE SP3?
Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
SP1?
Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE 2000
installer or do you have to update it to Service Pack 3 to perform this
task?
Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
Is there anyway of patching/fixing this installation to correct it or have I
got to de-tach the DBs and re-install MSDE with this
DISABLENETWORKPROTOCOLS=0 switch in the ini?
Thanks
hi,
Macsicarr wrote:
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but
> my queries are:
> Is it a problem with the original MSDE 2000 installer being installed
> on a WinXP SP2 machine or just a later version, ie MSDE SP3?
just up from service pack 3/3a.. before that sp, MSDE installed enabling
network protocols..

> Is it that no MSDE 2000 installer will work on WinXP SP2 when they
> did on SP1?
both sp3 (and MSDE Rel A) and sp4 can be installed on WinXP sp2..

> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original
> MSDE 2000 installer or do you have to update it to Service Pack 3 to
> perform this task?
the very first package did not support that parameter, that is new with sp3
(and MSDE Rel A)

> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
0= enable network protocols

> Is there anyway of patching/fixing this installation to correct it or
> have I got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
>
you can enable the desired network protocol you can use the Server Network
Utility (svrnetcn.exe)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea
My version of MSDE is:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
But I still can't get a remote LAN or WAN machine to connect to my MSDE
installation. It still says SQL Server does not exist or access denied,
even though local machine use is fine and I have no firewall security on to
block it.
I've even run the Server Network Utility (svrnetcn.exe) that you suggested
and found that Named Pipes and TCP/IP are already enabled and ready to go.
What am I doing wrong?
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3kfaa4Ftvsl3U1@.individual.net...
hi,
Macsicarr wrote:
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but
> my queries are:
> Is it a problem with the original MSDE 2000 installer being installed
> on a WinXP SP2 machine or just a later version, ie MSDE SP3?
just up from service pack 3/3a.. before that sp, MSDE installed enabling
network protocols..

> Is it that no MSDE 2000 installer will work on WinXP SP2 when they
> did on SP1?
both sp3 (and MSDE Rel A) and sp4 can be installed on WinXP sp2..

> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original
> MSDE 2000 installer or do you have to update it to Service Pack 3 to
> perform this task?
the very first package did not support that parameter, that is new with sp3
(and MSDE Rel A)

> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
0= enable network protocols

> Is there anyway of patching/fixing this installation to correct it or
> have I got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
>
you can enable the desired network protocol you can use the Server Network
Utility (svrnetcn.exe)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I've just checked the log and it still doesn't state that it's using TCP/IP
even though the network util only has TCP/IP in the right-hand box:
2005-07-25 18:42:40.29 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2005-07-25 18:42:40.60 server SQL Server configured for thread mode
processing.
2005-07-25 18:42:40.60 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2005-07-25 18:42:40.62 spid3 Starting up database 'master'.
2005-07-25 18:42:41.04 server Using 'SSNETLIB.DLL' version '8.0.194'.
2005-07-25 18:42:41.07 spid5 Starting up database 'model'.
2005-07-25 18:42:41.12 spid3 Server name is 'FREDPC'.
2005-07-25 18:42:41.12 spid3 Skipping startup of clean database id 4
2005-07-25 18:42:41.12 spid3 Skipping startup of clean database id 5
2005-07-25 18:42:41.35 spid5 Clearing tempdb database.
2005-07-25 18:42:42.54 spid5 Starting up database 'tempdb'.
2005-07-25 18:42:42.65 spid3 Recovery complete.
2005-07-25 18:42:56.09 server SQL server listening on Shared Memory,
Named Pipes. <<<<
2005-07-25 18:42:56.09 server SQL Server is ready for client connections
2005-07-25 18:43:17.17 spid51 Starting up database 'DemoData'.
2005-07-25 19:08:22.85 spid3 SQL Server is terminating due to 'stop'
request from Service Control Manager.
What am I doing wrong?
"Macsicarr" <No3@.Spam67.com> wrote in message
news:e4aBmFUkFHA.3164@.TK2MSFTNGP15.phx.gbl...
Hi Andrea
My version of MSDE is:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
But I still can't get a remote LAN or WAN machine to connect to my MSDE
installation. It still says SQL Server does not exist or access denied,
even though local machine use is fine and I have no firewall security on to
block it.
I've even run the Server Network Utility (svrnetcn.exe) that you suggested
and found that Named Pipes and TCP/IP are already enabled and ready to go.
What am I doing wrong?
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3kfaa4Ftvsl3U1@.individual.net...
hi,
Macsicarr wrote:
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but
> my queries are:
> Is it a problem with the original MSDE 2000 installer being installed
> on a WinXP SP2 machine or just a later version, ie MSDE SP3?
just up from service pack 3/3a.. before that sp, MSDE installed enabling
network protocols..

> Is it that no MSDE 2000 installer will work on WinXP SP2 when they
> did on SP1?
both sp3 (and MSDE Rel A) and sp4 can be installed on WinXP sp2..

> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original
> MSDE 2000 installer or do you have to update it to Service Pack 3 to
> perform this task?
the very first package did not support that parameter, that is new with sp3
(and MSDE Rel A)

> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
0= enable network protocols

> Is there anyway of patching/fixing this installation to correct it or
> have I got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
>
you can enable the desired network protocol you can use the Server Network
Utility (svrnetcn.exe)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||hi,
Macsicarr wrote:
> Hi Andrea
> My version of MSDE is:
> Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
> Aug 6 2000 00:57:48
> Copyright (c) 1988-2000 Microsoft Corporation
> Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
and this is MSDE retail version (RTM) on WinXP sp2

> But I still can't get a remote LAN or WAN machine to connect to my
> MSDE installation. It still says SQL Server does not exist or access
> denied, even though local machine use is fine and I have no firewall
> security on to block it.
are you sure the Windows Firewall, automatically enabled when installing
WinXP sp2, is not trapping you?

> I've even run the Server Network Utility (svrnetcn.exe) that you
> suggested and found that Named Pipes and TCP/IP are already enabled
> and ready to go.
MSDE retail version default behavior...
try a telnet connection on the MSDE port..
c:\..\>telnet ComputerName port_used_by_MSDE
if the screen becomes black you are connected to MSDE...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||HI Andrea
Thanks for the prompt reply.
In Windows Firewall it is set to Off. Although I would have thought
Microsoft would dim the other tabs (eg Exceptions and Advanced) seeing as
I've turned the firewall off I'm presuming that these have no effect.
The problem I have is that the error log quite clearly states that it is
listening on Shared Memory and Named Pipes - no TCP/IP is mentioned. Why is
this so?
The telnet test confirmed that it couldn't connect.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3kkp0tFull7hU1@.individual.net...
hi,
Macsicarr wrote:
> Hi Andrea
> My version of MSDE is:
> Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
> Aug 6 2000 00:57:48
> Copyright (c) 1988-2000 Microsoft Corporation
> Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
and this is MSDE retail version (RTM) on WinXP sp2

> But I still can't get a remote LAN or WAN machine to connect to my
> MSDE installation. It still says SQL Server does not exist or access
> denied, even though local machine use is fine and I have no firewall
> security on to block it.
are you sure the Windows Firewall, automatically enabled when installing
WinXP sp2, is not trapping you?

> I've even run the Server Network Utility (svrnetcn.exe) that you
> suggested and found that Named Pipes and TCP/IP are already enabled
> and ready to go.
MSDE retail version default behavior...
try a telnet connection on the MSDE port..
c:\..\>telnet ComputerName port_used_by_MSDE
if the screen becomes black you are connected to MSDE...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hello,
You may need to backup you registry file first, then check if you have the
following registry key:
HKLM/Software/Microsoft/Microsoft SQL
Server/mssql$<instancename>/MSSQLServer/SuperSocketNetLib/Tcp/
If not, add above registry key. Restart SQL server. Check the SQL log again
to see if it is listening on the TCP port.
The following articles are for your reference:
841251 How to enable SQL Server connectivity on Windows XP Service Pack 2
http://support.microsoft.com/?id=841251
841252 How to manually enable TCP/IP on Windows XP Service Pack 2 for SQL
http://support.microsoft.com/?id=841252
328306 Potential causes of the "SQL Server does not exist or access denied"
http://support.microsoft.com/?id=328306
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/tec...rview/40010469
Others: https://partner.microsoft.com/US/tec...pportoverview/
If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/common/international.aspx
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

Thursday, March 8, 2012

Can't create Primary Key??

Sunday, February 19, 2012

Cant connect to SQL Server 2005 in Visual Studio, only SQLExpress works?

Can't connect to sql server 2005 after sysprep

Can't connect to SQL Server 2000 with Visual Studio 2005

Can't connect to SQL Server (developer edition) from another PC?

Thursday, February 16, 2012

can't connect to SQL 6.5 server in different domain

Tuesday, February 14, 2012

Cant connect to my SQLExpress Instance

Sunday, February 12, 2012

Can't connect to MSDE

Cant connect to membership provider db

Friday, February 10, 2012

Can't connect to Access project

Can't connect remotely to MSDE 2000 DB on WinXP Home Machine

Can't connect remotely to MSDE 2000 DB on WinXP Home Machine

Can't connect remotely to MSDE 2000 DB on WinXP Home Machine

Can't connect remotely to MSDE 2000 DB on WinXP Home Machine

connect from ASP app

Blog Archive

About Me