msde and iis

Hi
If I get data from msde remotely
(from another computer)
should I have iis installed on computer
with sql server.?
Does connection should have
static IP?
Thanks
Konrad
"Konrad" <konrad007@.poczta.onet.pl> wrote in message
news:OdFN8F7TEHA.1048@.tk2msftngp13.phx.gbl...
> If I get data from msde remotely
> (from another computer)
> should I have iis installed on computer
> with sql server.?
If you are accessing the data via a web page, then that would work, or
install IIS on another server.

> Does connection should have
> static IP?
I'm not sure what you are asking here... Typically the host server, running
IIS would need a static address, and be registered in DNS. The connection
from the client side, could be the netbios name or the IP addess of the
host.
Steve

MSDE and Enterprise Manager Trouble

I have installed an MSDE instance on my PC. I have used both the setup.exe program and installed MSDE with the merge modules. Everything works fine - I am able to programmatically connect to the database and execute all of my statements. However, when I t
ry to register the database with Enterprise Manager, Enterprise Manager doesn't see the instance. Similarly, my program that uses SQLDMO.DLL to enumerate all servers does not see the MSDE instance. Both the database, my program, and Enterprise Manager are
running locally on the same machine.
This is a development box, and I have had to uninstall MSDE by hand several times by removing registry keys manually. I suspect that my problem is that I have deleted a key that I needed. Does anyone have any clues? Thanks in advance.
Rob Reagan
MSDE with Sp3a or MSDE Release A installs by default without network
connections enabled and will not advertise itself on the network. You can
still register the instance in Enterprise Manager by typing the name in the
textbox during registration.
You can install MSDE with network connections, see the "Customizing Desktop
Engine Setup.exe" topic in Books Online for details. You can also enable
network connections after installation with (I think) svrnetcn.exe in the
Tools\Bin directory, but I have no MSDe instance to check that at the
moment.
Jacco Schalkwijk
SQL Server MVP
"Rob Reagan" <RobReagan@.discussions.microsoft.com> wrote in message
news:AEC24187-ADA9-48D1-ADC3-837FEE031CEB@.microsoft.com...
> I have installed an MSDE instance on my PC. I have used both the setup.exe
program and installed MSDE with the merge modules. Everything works fine - I
am able to programmatically connect to the database and execute all of my
statements. However, when I try to register the database with Enterprise
Manager, Enterprise Manager doesn't see the instance. Similarly, my program
that uses SQLDMO.DLL to enumerate all servers does not see the MSDE
instance. Both the database, my program, and Enterprise Manager are running
locally on the same machine.
> This is a development box, and I have had to uninstall MSDE by hand
several times by removing registry keys manually. I suspect that my problem
is that I have deleted a key that I needed. Does anyone have any clues?
Thanks in advance.
> Rob Reagan

MSDE and Enterprise Manager

I have just installed (new clean install) of MSDE 3a. On another machine I have enterprise manager, and I thought I would be able to access it, but when I try to register it in EM it gives me the following error: SERVERNAME - SQL Server does not exist or access denied, Connection Open(Connect(). I have done this in the past with no problem. Did I forget a parameter on the install of 3a to allow other machines to access or do I have some other security issue?Depends on the configuration of MSDE. If you have enabled (using sapwd flag on setup.exe) SQL authentication, you can authenticate with these credentials. However, I did not try to connect to an MSDE instance running on another box with Enterprise Manager yet. But AFAIK, SQL auth should work fine in this case.|||I did configure it for SQL authentication.sql

MSDE and Access Project Issue

I installed MSDE SP3a on my XP Pro laptop using the following options:
SAPWD=abc456
instancename=MSDE01
DISABLENETWORKPROTOCOLS=0
SECURITYMODE=SQL
DATADIR="C:\MSDE"
TARGETDIR="C:\MSDE"
I went to services and started MSSQL$MSDE01 and SQLAgent$MSDE01.
I opened up MSACCESS 2003 and created a new project with new data. The SQL Server Database Wizard popped up and I entered (local)MSDE01 for the SQL server and clicked the Use Trusted Connection.
After several seconds, I receive an error message:
Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBMSLPCN]ConnectionOpen(Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBMSLPCN]SQL Server does not exist or access denied.
I can connect to this instance of MSDE using ASP.NET and the Server Explorer. So I'm pretty sure that I have a good install of MSDE.
Does anyone have a clue as to what I am doing wrong when I try to connect via Access?
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
Hi,
Try (local)\MSDE01 instead.
HTH,
Greg Low (MVP)
MSDE Manager SQL Tools
www.whitebearconsulting.com
"SqlJunkies User" <User@.-NOSPAM-SqlJunkies.com> wrote in message
news:uv46MJeIEHA.3968@.TK2MSFTNGP12.phx.gbl...
> I installed MSDE SP3a on my XP Pro laptop using the following options:
> SAPWD=abc456
> instancename=MSDE01
> DISABLENETWORKPROTOCOLS=0
> SECURITYMODE=SQL
> DATADIR="C:\MSDE"
> TARGETDIR="C:\MSDE"
> I went to services and started MSSQL$MSDE01 and SQLAgent$MSDE01.
> I opened up MSACCESS 2003 and created a new project with new data. The
SQL Server Database Wizard popped up and I entered (local)MSDE01 for the SQL
server and clicked the Use Trusted Connection.
> After several seconds, I receive an error message:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][DBMSLPCN]ConnectionOpen(Connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsoft][ODBC SQL Server Driver][DBMSLPCN]SQL Server does not exist or
access denied.
> I can connect to this instance of MSDE using ASP.NET and the Server
Explorer. So I'm pretty sure that I have a good install of MSDE.
> Does anyone have a clue as to what I am doing wrong when I try to connect
via Access?
>
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine
supports Post Alerts, Ratings, and Searching.
|||or .\MSDE01
HTH,
Greg Low (MVP)
MSDE Manager SQL Tools
www.whitebearconsulting.com
"SqlJunkies User" <User@.-NOSPAM-SqlJunkies.com> wrote in message
news:uv46MJeIEHA.3968@.TK2MSFTNGP12.phx.gbl...
> I installed MSDE SP3a on my XP Pro laptop using the following options:
> SAPWD=abc456
> instancename=MSDE01
> DISABLENETWORKPROTOCOLS=0
> SECURITYMODE=SQL
> DATADIR="C:\MSDE"
> TARGETDIR="C:\MSDE"
> I went to services and started MSSQL$MSDE01 and SQLAgent$MSDE01.
> I opened up MSACCESS 2003 and created a new project with new data. The
SQL Server Database Wizard popped up and I entered (local)MSDE01 for the SQL
server and clicked the Use Trusted Connection.
> After several seconds, I receive an error message:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][DBMSLPCN]ConnectionOpen(Connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsoft][ODBC SQL Server Driver][DBMSLPCN]SQL Server does not exist or
access denied.
> I can connect to this instance of MSDE using ASP.NET and the Server
Explorer. So I'm pretty sure that I have a good install of MSDE.
> Does anyone have a clue as to what I am doing wrong when I try to connect
via Access?
>
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine
supports Post Alerts, Ratings, and Searching.

MSDE along side WMSDE?

I've got a situation where WSUS is already installed on a server and I'm
looking
at moving my anti-virus system on to the same server, however my AV uses
MSDE. The server is running 2003 and therefore WSUS is running in WMSDE.
I take it I can't use WMSDE for my AV solution so I'd like to know, is it
viable to simply install MSDE 2000 along side WMSDE, or will I have to move
WSUS out of WMSDE and into MSDE 2000?
I assume I'll have some conflicts at minimum with the ports clashing if the
two live together, and there are likely to be other major problems.
Does anyone have any ideas or suggestions?
hi,
AC wrote:
> I've got a situation where WSUS is already installed on a server and
> I'm looking
> at moving my anti-virus system on to the same server, however my AV
> uses MSDE. The server is running 2003 and therefore WSUS is running
> in WMSDE.
> I take it I can't use WMSDE for my AV solution so I'd like to know,
> is it viable to simply install MSDE 2000 along side WMSDE, or will I
> have to move WSUS out of WMSDE and into MSDE 2000?
> I assume I'll have some conflicts at minimum with the ports clashing
> if the two live together, and there are likely to be other major
> problems.
> Does anyone have any ideas or suggestions?
WMSDE should not be used for other means then the ones it has been released
for, so just install another instance of MSDE for your AV...
you'll have no "ports clashing" or conflicts, as SQL Server 2000 allows up
to 16 instances to be locally installed...
only one of them can be the "default" instance, litening (by default) on
TCP/IP 1433 where all other instances have to be named instances, where
their full name is composed by the ComputerName\InstanceName...
you can leave for all of them the default "dynamically assigned port"
setting, an additional service, the SQL Server Resolution Service is then
listening on UDP 1434 to resolve and address the correct named instance on
it's appropriate port..
if you manually set the TCP/IP port the named instance(s) will be listen on,
you can close (on your firewall) the UDP 1434 port as it is no longer
needed, but you'll probably need to specify an ALIAS (via Client Network
Utility, cliconfg.exe) on all your remote clients..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thank you very much for your reply Andrea.
Although I've seen installations with several MSDE instances before I never
thought about how they worked untill now, therefore I've never even realised
there is a manager service to resolve the ports for each service!
Thank you for enlightening to this!
"Andrea Montanari" wrote:

> hi,
> AC wrote:
> WMSDE should not be used for other means then the ones it has been released
> for, so just install another instance of MSDE for your AV...
> you'll have no "ports clashing" or conflicts, as SQL Server 2000 allows up
> to 16 instances to be locally installed...
> only one of them can be the "default" instance, litening (by default) on
> TCP/IP 1433 where all other instances have to be named instances, where
> their full name is composed by the ComputerName\InstanceName...
> you can leave for all of them the default "dynamically assigned port"
> setting, an additional service, the SQL Server Resolution Service is then
> listening on UDP 1434 to resolve and address the correct named instance on
> it's appropriate port..
> if you manually set the TCP/IP port the named instance(s) will be listen on,
> you can close (on your firewall) the UDP 1434 port as it is no longer
> needed, but you'll probably need to specify an ALIAS (via Client Network
> Utility, cliconfg.exe) on all your remote clients..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
sql

MSDE Access via the Network

I'm having a terrible time accessing an MSDE instance over the network.
sqlDMO's listAvailableSQLServers doesn't see the installed instance. I
installed the MSDE instance using setup.exe with the following command:
setup.exe disablenetworkprotocols=0 sapwd="<pwd>" securityMode=SQL
instanceName="<my instance name>"
No luck. So I thought I'd use the svrnetcn.exe utility to enable network
protocols since MSDE seems to be ignoring the command line. When I try to run
svrnetcn.exe, the screen flickers but the program never opens.
This *was* working several weeks ago. It quit working about the time I
installed Service Pack 2 for Windows XP on the box that was hosting this
server. Does anyone have any idea why this is happening to me? Any help
would be GREATLY appreciated.
Rob Reagan
rob@.digitallabsinc.com
hi Rob,
"Rob Reagan" <RobReagan@.discussions.microsoft.com> ha scritto nel messaggio
news:5B63E3CB-8307-49C8-ABC4-56B114893B1D@.microsoft.com...
> I'm having a terrible time accessing an MSDE instance over the network.
> sqlDMO's listAvailableSQLServers doesn't see the installed instance. I
> installed the MSDE instance using setup.exe with the following command:
> setup.exe disablenetworkprotocols=0 sapwd="<pwd>" securityMode=SQL
> instanceName="<my instance name>"
> No luck. So I thought I'd use the svrnetcn.exe utility to enable network
> protocols since MSDE seems to be ignoring the command line. When I try to
run
> svrnetcn.exe, the screen flickers but the program never opens.
> This *was* working several weeks ago. It quit working about the time I
> installed Service Pack 2 for Windows XP on the box that was hosting this
> server. Does anyone have any idea why this is happening to me? Any help
> would be GREATLY appreciated.
> Rob Reagan
> rob@.digitallabsinc.com
>
SP service pack 2 changed a lot of things regarding SQL Server connections
too..
I've not installed sp2 yet, but it's worth reading
http://support.microsoft.com/default.aspx?kbid=841249 and related links...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thank you so much! That's just the information I needed.
SP2 makes my PC so secure, not even my own applications can get through...
"Andrea Montanari" wrote:

> hi Rob,
> "Rob Reagan" <RobReagan@.discussions.microsoft.com> ha scritto nel messaggio
> news:5B63E3CB-8307-49C8-ABC4-56B114893B1D@.microsoft.com...
> run
> SP service pack 2 changed a lot of things regarding SQL Server connections
> too..
> I've not installed sp2 yet, but it's worth reading
> http://support.microsoft.com/default.aspx?kbid=841249 and related links...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>

MSDE access over network slow for XP workstations, not Win2K

I've installed MSDE SP3a on a Windows 2000 Server, and the VB6 client
application on multiple workstations.
These workstations are either Win2000 Pro or WinXP Pro (both SP1 and SP2).
All workstations can access and ping the server under 1MS.
When the client application opens and reads data from the database server,
it takes a short time for this to be performed on the Win2000 Pro machines,
but all the XP machines take an abnormally long time to connect and to
retrieve the data.
The XP's do connect, but the retrieval is very slow, sometimes it timesout
during a retrieval.
This occurs even when nobody is connected to the database, so I've ruled out
the governer.
I'm using ADO to connect and all PC's have MDAC 2.7 or greater.
The install process only installed MDAC 2.7 if the current version is before
that.
Anybody have an idea what might be the problem?
All responses are welcome.
TIA
Jim K
Hi Jim,
Name resolution problems perhaps? Try connecting to the IP address instead
of the server name to find out.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Jim K" <krusej@.megsinet.net> wrote in message
news:enMo6BQ7EHA.1596@.tk2msftngp13.phx.gbl...
> I've installed MSDE SP3a on a Windows 2000 Server, and the VB6 client
> application on multiple workstations.
> These workstations are either Win2000 Pro or WinXP Pro (both SP1 and SP2).
> All workstations can access and ping the server under 1MS.
> When the client application opens and reads data from the database server,
> it takes a short time for this to be performed on the Win2000 Pro
> machines,
> but all the XP machines take an abnormally long time to connect and to
> retrieve the data.
> The XP's do connect, but the retrieval is very slow, sometimes it timesout
> during a retrieval.
> This occurs even when nobody is connected to the database, so I've ruled
> out
> the governer.
> I'm using ADO to connect and all PC's have MDAC 2.7 or greater.
> The install process only installed MDAC 2.7 if the current version is
> before
> that.
> Anybody have an idea what might be the problem?
> All responses are welcome.
> TIA
> Jim K
>
|||Thanks, I didn't think of that.
I have connected using the IP in other apps, but that was to the default
instance.
Since I have a named instance in this case, how would I format the IP and
instance?
Ex: default instance installed on server SERVER1, I can substitute the IP
for SERVER1
for named instance SERVER1/DB1, how would I format the IP? IP#/DB1 ?
Thanks!
"Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
news:u0zukkl7EHA.3124@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> Hi Jim,
> Name resolution problems perhaps? Try connecting to the IP address instead
> of the server name to find out.
> HTH,
> --
> Greg Low [MVP]
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "Jim K" <krusej@.megsinet.net> wrote in message
> news:enMo6BQ7EHA.1596@.tk2msftngp13.phx.gbl...
SP2).[vbcol=seagreen]
server,[vbcol=seagreen]
timesout
>
|||Hi Jim,
I'd suggest setting a fixed port for the named instance, then just connect
to that port. Even set up an alias on the client boxes that knows about the
port. It would completely avoid the sql browser function that essentially
just maps your instance name to a port anyway. To do that:
1. Open svrnetcn.exe and for the named instance, uncheck the "dynamic port"
box and select your own port (ie 38474 or something).
2. Restart the instance.
3. On the client, run cliconfg.exe and set up an alias pointing to that port
on the server.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Jim K" <krusej@.megsinet.net> wrote in message
news:u6vH8Mo7EHA.2196@.TK2MSFTNGP11.phx.gbl...
> Thanks, I didn't think of that.
> I have connected using the IP in other apps, but that was to the default
> instance.
> Since I have a named instance in this case, how would I format the IP and
> instance?
> Ex: default instance installed on server SERVER1, I can substitute the
> IP
> for SERVER1
> for named instance SERVER1/DB1, how would I format the IP? IP#/DB1 ?
> Thanks!
> "Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
> news:u0zukkl7EHA.3124@.TK2MSFTNGP11.phx.gbl...
> SP2).
> server,
> timesout
>
sql

MSDE 8 and MSDE 2000

Hello,
I have MSDE 8 installed on my Win2k server as it is is required by Veritas
Backup Exec.I would also likw to use this server for WSUS, which requires
MSDE 2000. Can these co-exist on the same server?
Thanks
hi,
mpapier wrote:
> Hello,
> I have MSDE 8 installed on my Win2k server as it is is required by
> Veritas Backup Exec.I would also likw to use this server for WSUS,
> which requires MSDE 2000. Can these co-exist on the same server?
>
actually MSDE 8 should be MSDE 2000, as no MSDE 8 is available, but 8.0 is
the internal version of the current SQL Server product...
MSDE (1.0) is based on SQL Server 7.0, where MSDE 2000 is based on SQL
Server 2000
another MSDE version, WMSDE has been made available for SharePoint, based on
MSDE 2000 with some restrictions on database size left out, as SharePoint
could need a database size beyond the actual 2gb limit of traditional
MSDE...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||So, you are saying I already MSDE 2000?
When I try to install WSUS it stops to tell me I do not have the proper
database software installed.
"Andrea Montanari" wrote:

> hi,
> mpapier wrote:
> actually MSDE 8 should be MSDE 2000, as no MSDE 8 is available, but 8.0 is
> the internal version of the current SQL Server product...
> MSDE (1.0) is based on SQL Server 7.0, where MSDE 2000 is based on SQL
> Server 2000
> another MSDE version, WMSDE has been made available for SharePoint, based on
> MSDE 2000 with some restrictions on database size left out, as SharePoint
> could need a database size beyond the actual 2gb limit of traditional
> MSDE...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||hi,
mpapier wrote:
> So, you are saying I already MSDE 2000?
> When I try to install WSUS it stops to tell me I do not have the
> proper database software installed.
I think you have WMSDE installed... based on MSDE 2000, but "branded" to
allow more then 2gb of data per data file...
AFAIK still there's no sp4 for that piece of software, but you could ask in
SharePoint or Win2003 NG...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE 7.0 and SQL2000

Can you install SQL2000 on a server with an application
that is using MSDE 7.0 which was installed with the
software ?
If you can, what is the best way to do so without it
affecting the previous installation of MSDE 7.0 ?Yes you can. BE aware, though, that MDAC on the machine will be upgraded to 2.6 (if not or higher
already), so make sure you test the app for that MDAC version.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Valencia" <vahorda@.hotmail.com> wrote in message news:a86f01c3ebb2$9d88f350$a401280a@.phx.gbl...
> Can you install SQL2000 on a server with an application
> that is using MSDE 7.0 which was installed with the
> software ?
> If you can, what is the best way to do so without it
> affecting the previous installation of MSDE 7.0 ?
>|||Thank you Tibor. I checked the version of MDAC and it is
2.5.
>--Original Message--
>Yes you can. BE aware, though, that MDAC on the machine
will be upgraded to 2.6 (if not or higher
>already), so make sure you test the app for that MDAC
version.
>--
>Tibor Karaszi, SQL Server MVP
>Archive at: http://groups.google.com/groups?
oi=djq&as_ugroup=microsoft.public.sqlserver
>
>"Valencia" <vahorda@.hotmail.com> wrote in message
news:a86f01c3ebb2$9d88f350$a401280a@.phx.gbl...
>> Can you install SQL2000 on a server with an application
>> that is using MSDE 7.0 which was installed with the
>> software ?
>> If you can, what is the best way to do so without it
>> affecting the previous installation of MSDE 7.0 ?
>
>.
>sql

MSDE 7.0 and SQL2000

Can you install SQL2000 on a server with an application
that is using MSDE 7.0 which was installed with the
software ?
If you can, what is the best way to do so without it
affecting the previous installation of MSDE 7.0 ?Yes you can. BE aware, though, that MDAC on the machine will be upgraded to
2.6 (if not or higher
already), so make sure you test the app for that MDAC version.
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=...ls
erver
"Valencia" <vahorda@.hotmail.com> wrote in message news:a86f01c3ebb2$9d88f350$a401280a@.phx.gbl...[Q
UOTE]
> Can you install SQL2000 on a server with an application
> that is using MSDE 7.0 which was installed with the
> software ?
> If you can, what is the best way to do so without it
> affecting the previous installation of MSDE 7.0 ?
>[/QUOTE]|||Thank you Tibor. I checked the version of MDAC and it is
2.5.
>--Original Message--
>Yes you can. BE aware, though, that MDAC on the machine
will be upgraded to 2.6 (if not or higher
>already), so make sure you test the app for that MDAC
version.
>--
>Tibor Karaszi, SQL Server MVP
>Archive at: http://groups.google.com/groups?
oi=djq&as_ugroup=microsoft.public.sqlserver
>
>"Valencia" <vahorda@.hotmail.com> wrote in message
news:a86f01c3ebb2$9d88f350$a401280a@.phx.gbl...
>
>.
>

MSDE 2ksp3a TO SQL Server 2000, why is upgrade option disabled?

Hi,
I have latest version of MSDE on my win xp machine, I had installed a named version msde using the microsoft bootstrapper along with my application. During installation I had specified the datadir to be something like c:\program files\MyApp\Data
So far so good.
Now I am trying to install SQL Server 2000 dev edition on my computer and was hoping to upgrade this named instance of MSDE, but the upgrade option is disabled. All I can click on is "Create a new instance of SQL Server, or install Client Tools" and "Adv
anced options". Why is that. What am I missing. I read many times that upgrading named instance shouldn't be a problem.
I have to figure this out so that in future my client's can upgrade our MSDE named instance to SQL Server named instance if they need to..
Thanks
dev
correction, I had installed msde using the latest sql2ksp3 exe from microsoft.
thanks
dev
|||You can't upgrade MSDE to Developer Edition, you can only upgrade to SQL
Server 2000 Enterprise Edition or SQL Server 2000 Standard Edition.
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"dev" <anonymous@.discussions.microsoft.com> wrote in message
news:F366A797-A10F-4EAE-8AD7-1BC89ED470C4@.microsoft.com...
> Hi,
> I have latest version of MSDE on my win xp machine, I had installed a
named version msde using the microsoft bootstrapper along with my
application. During installation I had specified the datadir to be
something like c:\program files\MyApp\Data
> So far so good.
> Now I am trying to install SQL Server 2000 dev edition on my computer and
was hoping to upgrade this named instance of MSDE, but the upgrade option is
disabled. All I can click on is "Create a new instance of SQL Server, or
install Client Tools" and "Advanced options". Why is that. What am I
missing. I read many times that upgrading named instance shouldn't be a
problem.
> I have to figure this out so that in future my client's can upgrade our
MSDE named instance to SQL Server named instance if they need to..
> Thanks
> dev
>
|||Jasper thanks for the reply. Where can I find the document which states MSDE can be upgraded to which versions.
Does that mean that my client will have to invest in a server (NT 4.0 Server OR NT 4.0 Enterprise Server OR Windows 2000 server OR Windows 2000 Advanced Server..) if they wish to upgrade from MSDE to SQL Server...
thanks
dev
|||got it, thanks
http://support.microsoft.com/default...b;en-us;823462
|||They'll need a server operating system e.g. Windows 2000 Server or Windows
2003 Standard to install SQL2000 Standard
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"dev" <anonymous@.discussions.microsoft.com> wrote in message
news:3F461785-F5A1-491F-9A4E-8ED5462409AE@.microsoft.com...
> Jasper thanks for the reply. Where can I find the document which states
MSDE can be upgraded to which versions.
> Does that mean that my client will have to invest in a server (NT 4.0
Server OR NT 4.0 Enterprise Server OR Windows 2000 server OR Windows 2000
Advanced Server..) if they wish to upgrade from MSDE to SQL Server...
> thanks
> dev

MSDE 2ksp3a TO SQL Server 2000, why is upgrade option disabled?

Hi
I have latest version of MSDE on my win xp machine, I had installed a named version msde using the microsoft bootstrapper along with my application. During installation I had specified the datadir to be something like c:\program files\MyApp\Dat
So far so good
Now I am trying to install SQL Server 2000 dev edition on my computer and was hoping to upgrade this named instance of MSDE, but the upgrade option is disabled. All I can click on is "Create a new instance of SQL Server, or install Client Tools" and "Advanced options". Why is that. What am I missing. I read many times that upgrading named instance shouldn't be a problem
I have to figure this out so that in future my client's can upgrade our MSDE named instance to SQL Server named instance if they need to.
Thank
deYou can't upgrade MSDE to Developer Edition, you can only upgrade to SQL
Server 2000 Enterprise Edition or SQL Server 2000 Standard Edition.
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"dev" <anonymous@.discussions.microsoft.com> wrote in message
news:F366A797-A10F-4EAE-8AD7-1BC89ED470C4@.microsoft.com...
> Hi,
> I have latest version of MSDE on my win xp machine, I had installed a
named version msde using the microsoft bootstrapper along with my
application. During installation I had specified the datadir to be
something like c:\program files\MyApp\Data
> So far so good.
> Now I am trying to install SQL Server 2000 dev edition on my computer and
was hoping to upgrade this named instance of MSDE, but the upgrade option is
disabled. All I can click on is "Create a new instance of SQL Server, or
install Client Tools" and "Advanced options". Why is that. What am I
missing. I read many times that upgrading named instance shouldn't be a
problem.
> I have to figure this out so that in future my client's can upgrade our
MSDE named instance to SQL Server named instance if they need to..
> Thanks
> dev
>|||Jasper thanks for the reply. Where can I find the document which states MSDE can be upgraded to which versions.
Does that mean that my client will have to invest in a server (NT 4.0 Server OR NT 4.0 Enterprise Server OR Windows 2000 server OR Windows 2000 Advanced Server..) if they wish to upgrade from MSDE to SQL Server...
thank
dev|||got it, thanks
http://support.microsoft.com/default.aspx?scid=kb;en-us;823462|||They'll need a server operating system e.g. Windows 2000 Server or Windows
2003 Standard to install SQL2000 Standard
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"dev" <anonymous@.discussions.microsoft.com> wrote in message
news:3F461785-F5A1-491F-9A4E-8ED5462409AE@.microsoft.com...
> Jasper thanks for the reply. Where can I find the document which states
MSDE can be upgraded to which versions.
> Does that mean that my client will have to invest in a server (NT 4.0
Server OR NT 4.0 Enterprise Server OR Windows 2000 server OR Windows 2000
Advanced Server..) if they wish to upgrade from MSDE to SQL Server...
> thanks
> dev

MSDE 2K Is there a compatibility issue with Backupexe or Sharepoint

We have installed an application that usese MSDE as the database, no error m
essage during install process. When application is opened and attempts to c
onnect with the database we get the following message:
sql code = -1
sql db code = 10004
"SQL Error: unable to connect: SQL server is unavailable or does not
exist. unable to connect: sql server does not exist or network access
denied"
We can get to the database and view contents using ODBC and OSQL. The syste
m is Windows Server 2003 Small Business Server, and we are using MSDE releas
e A. Other software on the system that might create a problem (hints I've s
een on other forums) are Ba
ckupexe and Sharepoint.
We have checked all issues of access rights and security issues we can think
of but apparently have overlooked something. This is a pretty high priorit
y issue for us so if anyone can help we would certainly appreciate it!I know this may not help much, but if you have no problem connecting from
OSQL and other application, you might want to check with teh vendor of the
application and find out how the connection to SQL Server is made from the
application. This might help lead to you why the error is occurring.
Rand
This posting is provided "as is" with no warranties and confers no rights.sql

MSDE 2000a installation failure on XP Pro

Hi,
Everyone know why MSDE 2000a is refusing to load on a XP Pro wiht Office SBS installed on it. It seems to have MSDE already but the default instance isn't accessible so I tried to install under another instance name. I have set the SA password.
File and print sharing is installed and running (I think). I'm able to share out folders.
Any suggestions?
Jim
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
hi Jim,
"SqlJunkies User" <User@.-NOSPAM-SqlJunkies.com> ha scritto nel messaggio
news:eIKtRH8eEHA.3028@.TK2MSFTNGP12.phx.gbl...
> Hi,
> Everyone know why MSDE 2000a is refusing to load on a XP Pro wiht Office
SBS installed on it. It seems to have MSDE already but the default instance
isn't accessible so I tried to install under another instance name. I have
set the SA password.
> File and print sharing is installed and running (I think). I'm able to
share out folders.
I'm not aware of such limitation... but, anyway, please add the /L*v
"c:\..\Log.txt" command line parameter in order to
inspect the resulting log file..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
sql

MSDE 2000 Wont Install after Uninstall

I installed MSDE 2000, then uninstalled it because of a
problem with a 3rd party program. I then uninstalled that
3rd party program and downloaded sql2kdesksp3.exe, and
unpacked the installer. I ran a command prompt and typed
setup SAPWD=password SecurityType=SQL
and it began to install, but when the installer came down 5
seconds it would just pause and not do anything. There is
no harddrive activity or anything. I have redownloaded the
package, and tried many things to try and get it to
working, but no success.
Help!
hi Mike,
"Mike" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:069c01c4b60c$09261510$a601280a@.phx.gbl
> I installed MSDE 2000, then uninstalled it because of a
> problem with a 3rd party program. I then uninstalled that
> 3rd party program and downloaded sql2kdesksp3.exe, and
> unpacked the installer. I ran a command prompt and typed
> setup SAPWD=password SecurityType=SQL
> and it began to install, but when the installer came down 5
> seconds it would just pause and not do anything. There is
> no harddrive activity or anything. I have redownloaded the
> package, and tried many things to try and get it to
> working, but no success.
first of all, you have to specify SECURITYMODE=SQL and not SecurityType=SQL
the problem you are facing is probably related to "Setup failed to configure
the server", as explained in
http://support.microsoft.com/default...99&Product=sql
due to a incomplete removal of MSDE instance... anyway, try adding the
/L*v "c:\MsdeLog.txt"
parameter to you command line call to setup.exe in order to create a (about
2mb) verbose log of the installation process, where you can search for
RETURN VALUE 3
condition and, about 10 lines before or after the failure cause is (little)
explained
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

msde 2000 sp4 - configuration failed

There is a bugfix in sp4 that I need for a customer machine. I have
been unsuccesful in getting service pack 4 installed on a test machine.
configuration:
windows 2000, msde 2000 sp2
setup command line:
setup /upgradesp sqlrun SECURITYMODE=SQL
UPGRADEUSER=myadminacct UPGRADEPWD=mypassword /L*v
C:\MSDELog.log
The setup runs for a couple minutes, then dialog progress bar winds
down. I have a 3.7 MB log, at the end I have:
=== Logging stopped: 7/7/2005 15:30:34 ===
MSI (c) (44:BC): Note: 1: 1729
MSI (c) (44:BC): Product: Microsoft SQL Server Desktop Engine --
Configuration failed.
MSI (c) (44:BC): Grabbed execution mutex.
MSI (c) (44:BC): Cleaning up uninstalled install packages, if
any exist
MSI (c) (44:BC): MainEngineThread is returning 1603
=== Verbose logging stopped: 7/7/2005 15:30:34 ===
After this happens, sqlserver agent will no longer start. I re-imaged
the machine and ran it again with the same result.
Anyone else have similar problems installing sp4? Anyone have a
solution?
Thanks!
hi,
slide@.backpacker.com wrote:
> === Logging stopped: 7/7/2005 15:30:34 ===
> MSI (c) (44:BC): Note: 1: 1729
> MSI (c) (44:BC): Product: Microsoft SQL Server Desktop Engine --
> Configuration failed.
> MSI (c) (44:BC): Grabbed execution mutex.
> MSI (c) (44:BC): Cleaning up uninstalled install packages, if
> any exist
> MSI (c) (44:BC): MainEngineThread is returning 1603
> === Verbose logging stopped: 7/7/2005 15:30:34 ===
please search for
RETURN VALUE 3
entries... about 10/15 lines before each entry you should find some
(sometime cryptic) description...
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
|||Andrea, thanks for the response! I found a 3:
<first>
Starting custom action SetFileAndRegACLs()
Beginning modification of directory Security Descriptor (SD).
SQL Path: C:\Program Files\Microsoft SQL Server\MSSQL\\
SQL Data Path: C:\Program Files\Microsoft SQL Server\MSSQL\\
SQL Service Account: .\dbservice
Agent Service Account: .\dbservice
Error:
No mapping between account names and security IDs was done.
Error Code = 1332
Ending modification of directory Security Descriptor (SD).
Ending custom action SetFileAndRegACLs().
Action ended 15:30:03: InstallFinalize. Return value 3.
</first>
<second>
Start custom action DeferProperties
Defer Properties returns: 0
MSI (s) (14:20): Executing op: End(Checksum=0,ProgressTotal=0)
MSI (s) (14:20): Error in rollback skipped. Return: 5
MSI (s) (14:20): FEATURECACHE: Entering Invalidate
MSI (s) (14:20): Unlocking Server
Action ended 15:30:33: INSTALL. Return value 3.
</second>
This last one was right after a property dump after the second one:
<third>
MSI (s) (14:20): MainEngineThread is returning 1603
MSI (c) (44:BC): Back from server. Return value: 1603
MSI (c) (44:BC): Decrementing counter to disable shutdown. If counter
>= 0, shutdown will be denied. Counter after decrement: -1
Action ended 15:30:34: INSTALL. Return value 3.
</third>
Any ideas?
-Chris
Andrea Montanari wrote:
> hi,
> slide@.backpacker.com wrote:
> please search for
> RETURN VALUE 3
> entries... about 10/15 lines before each entry you should find some
> (sometime cryptic) description...
> --
> 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,
slide@.backpacker.com wrote:
> Andrea, thanks for the response! I found a 3:
> <first>
> Starting custom action SetFileAndRegACLs()
> Beginning modification of directory Security Descriptor (SD).
> SQL Path: C:\Program Files\Microsoft SQL Server\MSSQL\\
> SQL Data Path: C:\Program Files\Microsoft SQL Server\MSSQL\\
> SQL Service Account: .\dbservice
> Agent Service Account: .\dbservice
> Error:
> No mapping between account names and security IDs was done.
> Error Code = 1332
> Ending modification of directory Security Descriptor (SD).
> Ending custom action SetFileAndRegACLs().
> Action ended 15:30:03: InstallFinalize. Return value 3.
> </first>
unfortunately I only found information like http://tinyurl.com/cs39o , and
really do not know if can help... the answers are not very consistent, but
at the very end of the thread there's a note... perhaps...
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
|||> unfortunately I only found information like http://tinyurl.com/cs39o , and
> really do not know if can help... the answers are not very consistent, but
> at the very end of the thread there's a note... perhaps...
Thanks for the "value 3" tip. This was some problem with the account
that sqlserveragent and mssqlserver were running under. Changed to
LocalSystem and installation succeeded.

MSDE 2000 SP3a Workgroup Access

Greetings everyone.

I work in a retail environment and have an MSDE2000 SP3a server installed in 350+ stores. I need to access the server from another computer in the workgroup (not domain) and I can't. I'm getting "SQL Server does not exist or access denied." The server was installed using the default option of Windows Authentication and I have changed it to Mixed mode authentication on one of my in-house lab systems with no luck. Also, when I try to create and OLEDB connection for the database and drop down the list of servers, there is nothing there (not even the local server.) Sorry but I do not have the error message that I get when that happens but I think when I solve the first problem the second will go away too.

Thanks for your inputHi,

Are you saying that when you changed a server to mixed mode you were still unable to connect to it? Even from the local machine?

In my experience with MSDE, when running in mixed mode you should be able to connect remotely with EM or QA with the UID & PWD.

Have you confirmed that you are able to connect over 1433/1434 on the network? I guess this is the equivalent of "have you checked your cables" but it's worth checking to make sure.

Dan|||Hi Dan -- thanks for the reply.

I have always been able to connect to the server, both in Windows Authentication mode and Mixed mode from the local machine on which the server resides. The problem is that I cannot connect in either mode from a different machine in the workgroup. I tried telnet to the local machine using port 1433 and got a connect failed even on the same machine as the server. I did not know about port 1434. I'll try that one when I get back to the office tomorrow.

Thanks Again|||Use the server network utility.|||Not to be dense but what's the "Server Network Utility?"

I know about osql and can connect to the server while on the local machine but not from another machine.|||It's one of the utilities installed with SQL. You'll need to run it from the machine you want to connect from. You'll need to set up the connection. You create an alias where you specify the connection properties for the server.

Dan|||Nevermind -- I found it. I dialed into my office computer and ran the server network utility and all protocols were disabled. I won't be able to check the results until Friday but I'm optimistic that this will resolve my problems. Thanks a lot.|||all protocols were disabled That will do it.|||Once I enabled named pipes and tcp/ip on the server, the workgroup connection works fabulously. Thanks for your help.

One more question. Is there a registry setting for this that I can download a .reg file to the stores to set this or do I have to manually configure this setting in all my stores? Thanks again.

MSDE 2000 Set-up: Invalid instance name

Thanks in advance.

I installed SQL 2000 Client Portion in my local computer: No server functionality. I selected my computer name as an instance name. Installation went OK.

Now, I am trying to install MSDE in my computer. Error comes in early part of installation: It says, "The instance name specified is not valid"

Please, any advise and suggestion.

Try deinstalling the SQL Client (why did that ask for an instance name when you didn't install the server - are you sure about deselecting the server?)

Install MSDE after the SQL Client was deinstalled. MSDE 2000 comes with a readme which explains the command line options for the setup. Read it carefully.

--
SvenC

|||

Thanks.

By the way, I have SQL 2005 Server in my computer.

Maybe, this is why.

|||

Yes, presumably MSDE tries to use the same instance name already in use by SQL 2005. Why would you want both versions on one machine?

Well, you can do it, but check the MSDE readme how to configure a different instance name. In the connection string you will use servername\instancename to access the named instance.

--
SvenC

MSDE 2000 Revision A installation

Can MSDE 2000 Revision A be installed on Windows Server 2003 Enterprised
Version For 64-Bit?
hi Roy,
"Roy" <Roy@.discussions.microsoft.com> ha scritto nel messaggio
news:805C6FFA-B8EF-4B14-8C00-73FEE032232E@.microsoft.com...
> Can MSDE 2000 Revision A be installed on Windows Server 2003 Enterprised
> Version For 64-Bit?
never tried [still not own a 64bit processor =:-( ], but I think yes, as you
can install SQL Server 2000 too...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Here is something I copied from MSDE document. You can see that the 64-bit
version is not listed. That's why I am wondering if MSDE can be installed on
it, since it fails when I tried. I want to know if this is the reason for
this failure.
Operating System Requirements
To use MSDE 2000, you must have installed one of these operating systems:
Windows Server 2003 Standard Edition, Windows Server 2003 Enterprise
Edition, Windows Server 2003 Datacenter Edition.
Windows 2000 Server, Windows 2000 Advanced Server, Windows 2000 Datacenter
Server.
Windows NT Server 4.0, SP5 or later; Windows NT Server 4.0, Enterprise
Edition, SP5 or later; Windows NT Workstation 4.0, SP5 or later.
Windows XP Professional, Windows XP Home Edition.
Windows 2000 Professional.
Windows Millennium Edition.
Windows 98. Windows 98 Second Edition is required if the computer does not
have a network card.
"Andrea Montanari" wrote:

> hi Roy,
> "Roy" <Roy@.discussions.microsoft.com> ha scritto nel messaggio
> news:805C6FFA-B8EF-4B14-8C00-73FEE032232E@.microsoft.com...
> never tried [still not own a 64bit processor =:-( ], but I think yes, as you
> can install SQL Server 2000 too...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Roy,
"Roy" <Roy@.discussions.microsoft.com> ha scritto nel messaggio
news:2E2CE882-3889-46E9-9751-BB444D9EB9E3@.microsoft.com...
> Here is something I copied from MSDE document. You can see that the 64-bit
> version is not listed. That's why I am wondering if MSDE can be installed
on
> it, since it fails when I tried. I want to know if this is the reason for
> this failure.
>...
actually may be...
what kind of error do you get as installation result in the verbose log
file?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Here is the last section from the log file:
Property(C): DATABASE = C:\DOCUME~1\FOCUS\LOCALS~1\Temp\3cfe77c.msi
Property(C): OriginalDatabase = C:\cmx\MSDERelA\Setup\SqlRun01.msi
Property(C): UILevel = 3
Property(C): ACTION = INSTALL
=== Logging stopped: 9/15/2004 13:18:44 ===
MSI (c) (54:A4): Note: 1: 1708
MSI (c) (54:A4): Product: Microsoft SQL Server Desktop Engine --
Installation operation failed.
MSI (c) (54:A4): Grabbed execution mutex.
MSI (c) (54:A4): Cleaning up uninstalled install packages, if any exist
MSI (c) (54:A4): MainEngineThread is returning 1603
=== Verbose logging stopped: 9/15/2004 13:18:44 ===
What does "MSI (c) (54:A4): Note: 1: 1708 " mean?
Thanks.
Rong
"Andrea Montanari" wrote:

> hi Roy,
> "Roy" <Roy@.discussions.microsoft.com> ha scritto nel messaggio
> news:2E2CE882-3889-46E9-9751-BB444D9EB9E3@.microsoft.com...
> on
> actually may be...
> what kind of error do you get as installation result in the verbose log
> file?
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||BTW, the error msg is "Setup failed to configure the server. Refer to the
server error logs ans setup error logs for more information" when
installation stops.
"Andrea Montanari" wrote:

> hi Roy,
> "Roy" <Roy@.discussions.microsoft.com> ha scritto nel messaggio
> news:2E2CE882-3889-46E9-9751-BB444D9EB9E3@.microsoft.com...
> on
> actually may be...
> what kind of error do you get as installation result in the verbose log
> file?
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Roy,
"Roy" <Roy@.discussions.microsoft.com> ha scritto nel messaggio
news:B1D6F8B1-67F1-48F9-B7D4-80D1E29E54BD@.microsoft.com...
> BTW, the error msg is "Setup failed to configure the server. Refer to the
> server error logs ans setup error logs for more information" when
> installation stops.
>
http://support.microsoft.com/default...99&Product=sql
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Still not working after I remove the data folder.
Instead the log files in the data folder after a failed install shows the
following:
Error 823 Severity 24 State 2
Can not recover the master database. Exiting.
SQL_Latin1_General_CP1_CI_AS
-m -Q -T4022 -T3659
An error occured while attempting to start the service (1460)
Any clue?
Thanks.
"Andrea Montanari" wrote:

> hi Roy,
> "Roy" <Roy@.discussions.microsoft.com> ha scritto nel messaggio
> news:B1D6F8B1-67F1-48F9-B7D4-80D1E29E54BD@.microsoft.com...
> http://support.microsoft.com/default...99&Product=sql
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>

MSDE 2000 Release A won't talk

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?
Have you installed SP3a?
Steve
<noname@.noname.com> wrote in message
news:40d55341.11850570@.nntp.flfrd.phub.net.cable.r ogers.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?
|||Hi Steve,
MSDE 2000A already contains SQL Server SP3a updates.
Mark
Ottawa, Canada
On Tue, 22 Jun 2004 15:25:07 -0400, "Steve Thompson"
<stevethompson@.nomail.please> wrote:

>Have you installed SP3a?
>Steve