communicate with SQL Server Manager nor MS Access on peer computer.
Can someone help?
Have set DISABLENETWORKPROTOCOLS=0 at install time.
Install log shows installation successful..
Control Panel> Admin Tools> Services section shows SQL server instance
running.
Disabling firewall has no effect.
SQL Server Manager (icon at bottom right in task tray - this
starts/stops Server instances), on same computer as SQL Server
instance, shows only instance "H" which is the same as the computer
name. (This instance was uninstalled before new instance was
installed.) Typing new instance name ("H\ABC" and variations) into
top combo box produces error messages such as "wrong format for name",
"Network path not found" "RPC service not running". What is the
correct computer/name format?? Key problem is clearly that Service
Manager can't communicate with this local MSDE instance.
All Windows 2000 updates from MS web site have been installed.
Objective is to operate MS Access on computer X (also running Win 2000
Pro) with computer H as a peer that hosts MSDE.
Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system??
--
Mark Ferguson<noname@.noname.com> wrote in message
news:40d53097.2976249@.nntp.flfrd.phub.net.cable.ro gers.com...
> MSDE 2000 Release A installed under windows 2000 pro will not
> communicate with SQL Server Manager nor MS Access on peer computer.
> Can someone help?
> Have set DISABLENETWORKPROTOCOLS=0 at install time.
> Install log shows installation successful..
> Control Panel> Admin Tools> Services section shows SQL server instance
> running.
> Disabling firewall has no effect.
> SQL Server Manager (icon at bottom right in task tray - this
> starts/stops Server instances), on same computer as SQL Server
> instance, shows only instance "H" which is the same as the computer
> name. (This instance was uninstalled before new instance was
> installed.) Typing new instance name ("H\ABC" and variations) into
> top combo box produces error messages such as "wrong format for name",
> "Network path not found" "RPC service not running". What is the
> correct computer/name format?? Key problem is clearly that Service
> Manager can't communicate with this local MSDE instance.
> All Windows 2000 updates from MS web site have been installed.
> Objective is to operate MS Access on computer X (also running Win 2000
> Pro) with computer H as a peer that hosts MSDE.
> Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system??
> --
> Mark Ferguson
I must admit that I don't know the difference between MSDE Release A and
MSDE SP3a. There is no clear information on the MS site (or at least I
couldn't find it), but the download sizes are different, so the obvious
conclusion is that they are different versions. If this assumption is
correct, then you might be seeing this issue:
http://support.microsoft.com/defaul...010&Product=sql
However, I could be wrong, so perhaps you can check some more things. Can
you actually connect to the instance on H using a local osql.exe command
also on H? If you're logged on to Windows as an administrator, then this
should be enough:
osql -S H\ABC -E
If that works, then presumably the problem is the Service Manager itself
(possibly as described in the article above). If you can connect, you can
then check the version with this query:
1> select @.@.version
2> go
If you don't see version 8.00.760, then you don't have SP3a, so I would
completely remove MSDE and then install MSDE SP3a. See "Remove all known
instances of SQL Server" in this article:
http://support.microsoft.com/defaul...991&Product=sql
If you cannot connect with osql.exe, then what error message do you get? In
the final analysis, however, I would suggest that Server Manager is a small,
unimportant component which probably is not worth worrying about. As long as
MSDE is running and you can connect from client applications with no
problems, then I would not spend too much time trying to make it work.
Regarding connecting from a different PC (with Access or any other tool),
there are a number of possible connection issues:
http://support.microsoft.com/defaul...306&Product=sql
I guess when you say "peer" you mean that the PCs are in a workgroup, not a
domain. If this is the case, then trusted connections can be awkward - the
article above has a link to another KB article which describes a possible
workaround. Mixed security using SQL logins should work fine, but is not
generally recommended unless there is no other alternative.
Simon|||Hi
You may get more help in the microsoft.public.sqlserver.msde newsgroup.
John
<noname@.noname.com> wrote in message
news:40d53097.2976249@.nntp.flfrd.phub.net.cable.ro gers.com...
> MSDE 2000 Release A installed under windows 2000 pro will not
> communicate with SQL Server Manager nor MS Access on peer computer.
> Can someone help?
> Have set DISABLENETWORKPROTOCOLS=0 at install time.
> Install log shows installation successful..
> Control Panel> Admin Tools> Services section shows SQL server instance
> running.
> Disabling firewall has no effect.
> SQL Server Manager (icon at bottom right in task tray - this
> starts/stops Server instances), on same computer as SQL Server
> instance, shows only instance "H" which is the same as the computer
> name. (This instance was uninstalled before new instance was
> installed.) Typing new instance name ("H\ABC" and variations) into
> top combo box produces error messages such as "wrong format for name",
> "Network path not found" "RPC service not running". What is the
> correct computer/name format?? Key problem is clearly that Service
> Manager can't communicate with this local MSDE instance.
> All Windows 2000 updates from MS web site have been installed.
> Objective is to operate MS Access on computer X (also running Win 2000
> Pro) with computer H as a peer that hosts MSDE.
> Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system??
> --
> Mark Ferguson|||"Simon Hayes" <sql@.hayes.ch> wrote in message
news:40d5ade5$1_2@.news.bluewin.ch...
|
| <noname@.noname.com> wrote in message
| news:40d53097.2976249@.nntp.flfrd.phub.net.cable.ro gers.com...
| > MSDE 2000 Release A installed under windows 2000 pro will not
| > communicate with SQL Server Manager nor MS Access on peer computer.
| > Can someone help?
| >
| > Have set DISABLENETWORKPROTOCOLS=0 at install time.
| >
| > Install log shows installation successful..
| >
| > Control Panel> Admin Tools> Services section shows SQL server instance
| > running.
| >
| > Disabling firewall has no effect.
| >
| > SQL Server Manager (icon at bottom right in task tray - this
| > starts/stops Server instances), on same computer as SQL Server
| > instance, shows only instance "H" which is the same as the computer
| > name. (This instance was uninstalled before new instance was
| > installed.) Typing new instance name ("H\ABC" and variations) into
| > top combo box produces error messages such as "wrong format for name",
| > "Network path not found" "RPC service not running". What is the
| > correct computer/name format?? Key problem is clearly that Service
| > Manager can't communicate with this local MSDE instance.
| >
| > All Windows 2000 updates from MS web site have been installed.
| >
| > Objective is to operate MS Access on computer X (also running Win 2000
| > Pro) with computer H as a peer that hosts MSDE.
| >
| > Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system??
| > --
| > Mark Ferguson
|
| I must admit that I don't know the difference between MSDE Release A and
| MSDE SP3a. There is no clear information on the MS site (or at least I
| couldn't find it), but the download sizes are different, so the obvious
| conclusion is that they are different versions. If this assumption is
| correct, then you might be seeing this issue:
|
| http://support.microsoft.com/defaul...010&Product=sql
|
| However, I could be wrong, so perhaps you can check some more things. Can
| you actually connect to the instance on H using a local osql.exe command
| also on H? If you're logged on to Windows as an administrator, then this
| should be enough:
|
| osql -S H\ABC -E
|
| If that works, then presumably the problem is the Service Manager itself
| (possibly as described in the article above). If you can connect, you can
| then check the version with this query:
|
| 1> select @.@.version
| 2> go
|
| If you don't see version 8.00.760, then you don't have SP3a, so I would
| completely remove MSDE and then install MSDE SP3a. See "Remove all known
| instances of SQL Server" in this article:
|
| http://support.microsoft.com/defaul...991&Product=sql
|
| If you cannot connect with osql.exe, then what error message do you get? In
| the final analysis, however, I would suggest that Server Manager is a small,
| unimportant component which probably is not worth worrying about. As long as
| MSDE is running and you can connect from client applications with no
| problems, then I would not spend too much time trying to make it work.
|
| Regarding connecting from a different PC (with Access or any other tool),
| there are a number of possible connection issues:
|
| http://support.microsoft.com/defaul...306&Product=sql
|
| I guess when you say "peer" you mean that the PCs are in a workgroup, not a
| domain. If this is the case, then trusted connections can be awkward - the
| article above has a link to another KB article which describes a possible
| workaround. Mixed security using SQL logins should work fine, but is not
| generally recommended unless there is no other alternative.
|
| Simon
|
|
MSDE 2000 Release A is a developer version (SDK) of Microsoft SQL Server 2000
Desktop Engine SP3a. SELECT @.@.VERSION returns the same version info for both.
This brief description of Microsoft SQL Server 2000 Desktop Engine (MSDE 2000)
Release A is quoted from the download page -
<
MSDE 2000 Release A is functionally equivalent to SQL Server 2000 Desktop
Engine SP3a except for the following:
New licensing agreement
Removal of the merge modules that can be used to embed MSDE 2000 Release A
with applications
New ReadMeMSDE2000A.htm that contains information specific to this release.
This new version of MSDE contains all the fixes that are included with SQL
Server 2000 SP3a version of MSDE.
http://www.microsoft.com/downloads/...&DisplayLang=en
Additional information can be found in the Microsoft SQL Server 2000 Desktop
Engine
(MSDE 2000) Release A ReadMe
http://download.microsoft.com/downl...meMSDE2000A.htm
Additions to the SQL Server 2000 Desktop Engine (MSDE) Release A
ReadmeMSDE2000A.htm File
http://support.microsoft.com/?kbid=829925
Dan|||<noname@.noname.com> wrote in message
news:40d53097.2976249@.nntp.flfrd.phub.net.cable.ro gers.com...
| MSDE 2000 Release A installed under windows 2000 pro will not
| communicate with SQL Server Manager nor MS Access on peer computer.
| Can someone help?
|
| Have set DISABLENETWORKPROTOCOLS=0 at install time.
|
| Install log shows installation successful..
|
| Control Panel> Admin Tools> Services section shows SQL server instance
| running.
|
| Disabling firewall has no effect.
|
| SQL Server Manager (icon at bottom right in task tray - this
| starts/stops Server instances), on same computer as SQL Server
| instance, shows only instance "H" which is the same as the computer
| name. (This instance was uninstalled before new instance was
| installed.) Typing new instance name ("H\ABC" and variations) into
| top combo box produces error messages such as "wrong format for name",
| "Network path not found" "RPC service not running". What is the
| correct computer/name format?? Key problem is clearly that Service
| Manager can't communicate with this local MSDE instance.
|
| All Windows 2000 updates from MS web site have been installed.
|
| Objective is to operate MS Access on computer X (also running Win 2000
| Pro) with computer H as a peer that hosts MSDE.
|
| Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system??
| --
| Mark Ferguson
Hi Mark,
There is known bug when reinstalling with same instance name.
Follow the instructions for editing the registry keys given in
the article at:
http://support.microsoft.com/defaul...kb;en-us;823467
If that fails then you will have to uninstall MSDE 2000 Release A
and follow the instructions for editing the registry keys given in
the article at:
http://support.microsoft.com/defaul...kb;en-us;320873
Then reinstall MSDE 2000 Release A
Hope this helps.
Dan|||Thanks John, but I dont see a newsgroup named
microsoft.public.sqlserver.msde. I just checked for new groups and
that one doesn't show up there either. Not sure where i might find
this group.
On Sun, 20 Jun 2004 16:07:34 GMT, "John Bell"
<jbellnewsposts@.hotmail.com> wrote:
>Hi
>You may get more help in the microsoft.public.sqlserver.msde newsgroup.
>John
><noname@.noname.com> wrote in message
>news:40d53097.2976249@.nntp.flfrd.phub.net.cable.ro gers.com...
>> MSDE 2000 Release A installed under windows 2000 pro will not
>> communicate with SQL Server Manager nor MS Access on peer computer.
>> Can someone help?
>>
>> Have set DISABLENETWORKPROTOCOLS=0 at install time.
>>
>> Install log shows installation successful..
>>
>> Control Panel> Admin Tools> Services section shows SQL server instance
>> running.
>>
>> Disabling firewall has no effect.
>>
>> SQL Server Manager (icon at bottom right in task tray - this
>> starts/stops Server instances), on same computer as SQL Server
>> instance, shows only instance "H" which is the same as the computer
>> name. (This instance was uninstalled before new instance was
>> installed.) Typing new instance name ("H\ABC" and variations) into
>> top combo box produces error messages such as "wrong format for name",
>> "Network path not found" "RPC service not running". What is the
>> correct computer/name format?? Key problem is clearly that Service
>> Manager can't communicate with this local MSDE instance.
>>
>> All Windows 2000 updates from MS web site have been installed.
>>
>> Objective is to operate MS Access on computer X (also running Win 2000
>> Pro) with computer H as a peer that hosts MSDE.
>>
>> Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system??
>> --
>> Mark Ferguson|||Hi
Try the news.microsoft.com news server or
http://groups.google.com/groups?hl=...sqlserver.msde
John
<Mark_Ferguson@.noname.com> wrote in message
news:40d736bf.12602391@.nntp.flfrd.phub.net.cable.r ogers.com...
> Thanks John, but I dont see a newsgroup named
> microsoft.public.sqlserver.msde. I just checked for new groups and
> that one doesn't show up there either. Not sure where i might find
> this group.
> On Sun, 20 Jun 2004 16:07:34 GMT, "John Bell"
> <jbellnewsposts@.hotmail.com> wrote:
> >Hi
> >You may get more help in the microsoft.public.sqlserver.msde newsgroup.
> >John
> ><noname@.noname.com> wrote in message
> >news:40d53097.2976249@.nntp.flfrd.phub.net.cable.ro gers.com...
> >> MSDE 2000 Release A installed under windows 2000 pro will not
> >> communicate with SQL Server Manager nor MS Access on peer computer.
> >> Can someone help?
> >>
> >> Have set DISABLENETWORKPROTOCOLS=0 at install time.
> >>
> >> Install log shows installation successful..
> >>
> >> Control Panel> Admin Tools> Services section shows SQL server instance
> >> running.
> >>
> >> Disabling firewall has no effect.
> >>
> >> SQL Server Manager (icon at bottom right in task tray - this
> >> starts/stops Server instances), on same computer as SQL Server
> >> instance, shows only instance "H" which is the same as the computer
> >> name. (This instance was uninstalled before new instance was
> >> installed.) Typing new instance name ("H\ABC" and variations) into
> >> top combo box produces error messages such as "wrong format for name",
> >> "Network path not found" "RPC service not running". What is the
> >> correct computer/name format?? Key problem is clearly that Service
> >> Manager can't communicate with this local MSDE instance.
> >>
> >> All Windows 2000 updates from MS web site have been installed.
> >>
> >> Objective is to operate MS Access on computer X (also running Win 2000
> >> Pro) with computer H as a peer that hosts MSDE.
> >>
> >> Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system??
> >> --
> >> Mark Ferguson|||>I must admit that I don't know the difference between MSDE Release A and
>MSDE SP3a. There is no clear information on the MS site (or at least I
>couldn't find it), but the download sizes are different, so the obvious
>conclusion is that they are different versions. If this assumption is
>correct, then you might be seeing this issue:
>http://support.microsoft.com/defaul...010&Product=sql
This article applies to MSDE Service pack . I have installed MSDE
2000A which includes Service Pack 3. The symptoms don't and conditions
don't apply, nor do the workaround instructions make sense.
>However, I could be wrong, so perhaps you can check some more things. Can
>you actually connect to the instance on H using a local osql.exe command
>also on H? If you're logged on to Windows as an administrator, then this
>should be enough:
>osql -S H\ABC -E
This works. But the SQL Server *is* running - we knew that.
>If that works, then presumably the problem is the Service Manager itself
>(possibly as described in the article above). If you can connect, you can
>then check the version with this query:
>1> select @.@.version
>2> go
Result is:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copy
right (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT
5.0 (Build 2195: Service Pack 4)
>If you don't see version 8.00.760, then you don't have SP3a, so I would
>completely remove MSDE and then install MSDE SP3a. See "Remove all known
>instances of SQL Server" in this article:
>http://support.microsoft.com/defaul...991&Product=sql
Thank you... This may be very useful indeed.
>If you cannot connect with osql.exe, then what error message do you get? In
>the final analysis, however, I would suggest that Server Manager is a small,
>unimportant component which probably is not worth worrying about. As long as
>MSDE is running and you can connect from client applications with no
>problems, then I would not spend too much time trying to make it work.
>Regarding connecting from a different PC (with Access or any other tool),
>there are a number of possible connection issues:
>http://support.microsoft.com/defaul...306&Product=sql
>I guess when you say "peer" you mean that the PCs are in a workgroup, not a
>domain. If this is the case, then trusted connections can be awkward - the
>article above has a link to another KB article which describes a possible
>workaround. Mixed security using SQL logins should work fine, but is not
>generally recommended unless there is no other alternative.
You are correct, the two computers are not in a domain and so there is
no user authentication provided by a domain server. Thanks for the
link I will look it up.
The Server Manager is only important in that its a good first
indication that everything is working at the local computer - an
encouraging first sign, insofar as the client computer cannot connect
to the server.
>Simon
>
I am also working on the problem of fixing ports used by the SQL
Server. The instance now installed is named and so uses dynamic ports
rather than the fixed 1433 and 1434 ports. The question is: what does
the SQL Server Manager use?|||I think you are correct. I need to uninstall MSDE2000A and then fix up
the registry or re-install windows 2000. I have already uninstalled
the old default version that came with MS office. I have also
installed the MSDE2000A version several times.
I have never checked the MDAC version (don't know how), but that may
also be a problem.
I need to try these and then request more help.
Many thanks.
Mark.
On Mon, 21 Jun 2004 05:22:56 -0400, "Daniel A. Thomas"
<dathomas@.--spam--istar.ca> wrote:
>Hi Mark,
>There is known bug when reinstalling with same instance name.
>Follow the instructions for editing the registry keys given in
>the article at:
>http://support.microsoft.com/defaul...kb;en-us;823467
>If that fails then you will have to uninstall MSDE 2000 Release A
>and follow the instructions for editing the registry keys given in
>the article at:
>http://support.microsoft.com/defaul...kb;en-us;320873
>Then reinstall MSDE 2000 Release A
>Hope this helps.
>Dan|||OK, John. The google web page is the same as the MS Discussion forum
for SQL Server. I posted a similar article there, but no help came
there.
Mark.
On Mon, 21 Jun 2004 19:56:20 GMT, "John Bell"
<jbellnewsposts@.hotmail.com> wrote:
>Hi
>Try the news.microsoft.com news server or
>http://groups.google.com/groups?hl=...sqlserver.msde
>John|||I'm grateful for the help from you all, but the one real symptom of
the problem with the Service Manager is its error message:
"The format of the computer name is inavlid."
This is the response to asking it to find the instance ABC on the
computer named "H" - (H\ABC). Recall that running osql.exe against the
name H\ABC works fine.
Mark.
No comments:
Post a Comment