MSDE Rel A stops during install

My installation of MSDE Rel A is stopping at the
following point in the log file:
Starting custom action InstallSqlRedis
Executing "C:\Program Files\Microsoft SQL Server\80
\Tools\Binn\sqlredis.exe /q:a"
MSI (c) (B0:E4) [16:21:46:280]: Font created. Charset:
Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
Installation of the Microsoft Data Access Components
package failed.
MSI (s) (30!FC) [16:21:48:908]: Product: Microsoft SQL
Server Desktop Engine -- Installation of the Microsoft
Data Access Components package failed.
Action ended 16:21:48: InstallFinalize. Return value 3.
MSI (s) (30:B0) [16:21:48:978]: User policy
value 'DisableRollback' is 0
MSI (s) (30:B0) [16:21:48:978]: Machine policy
value 'DisableRollback' is 0
In order to get package failed comment, I have to "End
Task" on the sqlredis.exe from the task manager. No disk
activity is occuring. I tried on another box that has XP
Pro SP2 installed and it went on just fine.
Is there something installed that is blocking this.
I have the full line of Office products installed.
hi Paul,
Paul Konen wrote:
> My installation of MSDE Rel A is stopping at the
> following point in the log file:
> Starting custom action InstallSqlRedis
> Executing "C:\Program Files\Microsoft SQL Server\80
> \Tools\Binn\sqlredis.exe /q:a"
> MSI (c) (B0:E4) [16:21:46:280]: Font created. Charset:
> Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
> Installation of the Microsoft Data Access Components
> package failed.
>...
try fixing the MDAC stack, which is currently not available as a refrresh
separated package for Win XP sp 2...
first, locate the mdac.inf file in c:\windows\inf right click and install..
when prompted for a location, point to
c:\windows\servicepackfiles\i386
then when prompted for the XP cd, either load the cd or point to your
\i386...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.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, I tried the fix you described and I stop at the same point.
I have the following in my task manager: (Hope this helps)
setup.exe
setupre.exe
sqlredis.exe
The timer on the Microsoft SqlServer shows 17 seconds. (This may not help)
Is there a install file or something I can modify to not make this install
happen quietly?
Thanks
"Andrea Montanari" wrote:

> hi Paul,
> Paul Konen wrote:
> try fixing the MDAC stack, which is currently not available as a refrresh
> separated package for Win XP sp 2...
> first, locate the mdac.inf file in c:\windows\inf right click and install..
> when prompted for a location, point to
> c:\windows\servicepackfiles\i386
> then when prompted for the XP cd, either load the cd or point to your
> \i386...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||hi Paul,
Paul wrote:
> Hi Andrea, I tried the fix you described and I stop at the same point.
> I have the following in my task manager: (Hope this helps)
> setup.exe
> setupre.exe
> sqlredis.exe
> The timer on the Microsoft SqlServer shows 17 seconds. (This may not
> help)
> Is there a install file or something I can modify to not make this
> install happen quietly?
unfortunately, usually fixing the MDAC stack or manually running the
sqlredis.exe (which actually install/update MDAC) before the re-installation
does the trick....
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I tried to run the sqlredis while the installer was stuck and it didn't yield
any different results. Is there a different place to find the sqlredis that
may work.
Any other information I can provide that may help?
"Andrea Montanari" wrote:

> hi Paul,
> Paul wrote:
> unfortunately, usually fixing the MDAC stack or manually running the
> sqlredis.exe (which actually install/update MDAC) before the re-installation
> does the trick....
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||hi Paul,
Paul wrote:
> I tried to run the sqlredis while the installer was stuck and it
> didn't yield any different results. Is there a different place to
> find the sqlredis that may work.
>
nope, as no refresh distribution is available for MDAC 2.8 WinXP sp2...
just a note... you can eventually try downloading and installing the new sp4
from SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE (full sp4 page at
http://www.microsoft.com/downloads/d...displaylang=en)
which include a modified setup that better checks and installs MDAC only
when and if needed..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||hi Paul,
Paul wrote:
> OK, same results when installing under the SP4. Here is a snippet of
> the Log file during installation
no further idea :-(
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Believe it or not, killing setupre.exe with the task manager once your setup
is frozen will allow the install to complete successfully. Not exactly a
Microsoft recommended solution, but it got me unstuck when I read about it
somewhere else.
John
"Paul Konen" wrote:

> My installation of MSDE Rel A is stopping at the
> following point in the log file:
>
|||That took care of it. I was always killing the sqlredis.exe and not setupre.
Thanks
Paul
"Process Patrol" wrote:
[vbcol=seagreen]
> Believe it or not, killing setupre.exe with the task manager once your setup
> is frozen will allow the install to complete successfully. Not exactly a
> Microsoft recommended solution, but it got me unstuck when I read about it
> somewhere else.
> John
> "Paul Konen" wrote:

MSDE rel A installation error

I got an error "Setup failed to configure the server". I
have tried to delete the directory "C:\program
files\microsoft sql sever before installation. But I still
get this error. What should i do?
Thank you very much. I spent a week to install this MSDE
but still failed. I am very desperate...
San
hi San,
"San" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:1e5f701c4554e$a0454200$a501280a@.phx.gbl...
> I got an error "Setup failed to configure the server". I
> have tried to delete the directory "C:\program
> files\microsoft sql sever before installation. But I still
> get this error. What should i do?
> Thank you very much. I spent a week to install this MSDE
> but still failed. I am very desperate...
in addition to folder delete, try cealning the Windows Registry too, as
reported in
http://support.microsoft.com/default...;EN-US;Q290991
"Remove a Specific Instance of SQL Server" section...
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
|||Thank you. However, I am confused. It is because that KB
is for those who have sql sever installed before. My
computer did not contains any sql sever before (I think).
Could you give me more hints on what I should delete?
Furthermore, I found a strange registry. It
is "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microso ft SQL
Server Setup.{5B5BFFF9-9D55-45AF-9390-AA4DC1C4EEFE}".
Should I delete this?
Thank you for your help.
San

>--Original Message--
>hi San,
>"San" <anonymous@.discussions.microsoft.com> ha scritto
nel messaggio[vbcol=seagreen]
>news:1e5f701c4554e$a0454200$a501280a@.phx.gbl...
still
>in addition to folder delete, try cealning the Windows
Registry too, as
>reported in
>http://support.microsoft.com/default.aspx?scid=kb;EN-
US;Q290991
>"Remove a Specific Instance of SQL Server" section...
>--
>Andrea Montanari (Microsoft MVP - SQL Server)
>http://www.asql.biz/DbaMgr.shtm
http://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
>.
>
|||hi San,
"San" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:1e59401c45553$1386bba0$a101280a@.phx.gbl...
> Thank you. However, I am confused. It is because that KB
> is for those who have sql sever installed before. My
> computer did not contains any sql sever before (I think).
> Could you give me more hints on what I should delete?
> Furthermore, I found a strange registry. It
> is "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microso ft SQL
> Server Setup.{5B5BFFF9-9D55-45AF-9390-AA4DC1C4EEFE}".
> Should I delete this?
personally I always and only cleared the registry keys reported in the KB
article... as you already read, this does not clear the Windows Installer
registry entries, but I was quiet happy with this method when a MSDE
instance I installed refused to uninstall... I still have this entry in the
Add/Remove programs applet, but I'll remove it ...perhaps =;-D
the hive you notice shoul'd only point to a Temp folder used by the setup
process...
you wrote[vbcol=seagreen]
uncomplete installations can make the system dirty, so you are supposed to
clear it before re-proceeding with new installs...
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 over firewall

Succesfully created a MSDE 2000 rel A backend on 2003
server. I can connect a MS Access project frontend to it
from an XP client on the same LAN segment. I can connect
the same frontend over the internet to this server when
set out in the firewall's DMZ.
And now for my next trick! When I tuck the MSDE server
back behind the firewall and open up TCP and UDP ports at
1433 and 1434 for both incoming and outgoing traffic, I
cannot connect. I include a filtered log showing traffic
between the Access client on the Internet and the firewall
for detail. It appears that the Netgear firewall passes
packets to the server but it times out in a little less
than a minute... I am looking forward to any ideas that
may move this project forward!
TimeProtocolSrcDstApplication
Message
13:58:28UDP645521434ms-sql-m
[Service access request successful]
13:58:28TCP645532418cas[Access
Policy not found, dropping packet]
13:58:31TCP645532418cas[Access
Policy not found, dropping packet]
13:58:37TCP645532418cas[Access
Policy not found, dropping packet]
13:58:51TCP645582418cas[Access
Policy not found, dropping packet]
13:58:54TCP645582418cas[Access
Policy not found, dropping packet]
13:59:00TCP645582418cas[Access
Policy not found, dropping packet]
13:59:14TCP64564445ms-ds[Access
Policy not found, dropping packet]
13:59:14TCP64565139netbios-ssn
[Access Policy not found, dropping packet]
13:59:17TCP64565139netbios-ssn
[Access Policy not found, dropping packet]
13:59:17TCP64564445ms-ds[Access
Policy not found, dropping packet]
13:59:20UDP645521434ms-sql-m
[Connection timed out.Bytes transferred : 137]
13:59:23TCP64565139netbios-ssn
[Access Policy not found, dropping packet]
13:59:23TCP64564445ms-ds[Access
Policy not found, dropping packet]
From your trace it appears that many more IP ports (than 1433 & 1434) are
being attempted to be used.
I suspect it's failing because of the attempt to do name resolution.
Steve
"Ed Morra" <ed@.orl-inc.com> wrote in message
news:36f801c4297b$6a642240$a601280a@.phx.gbl...
> Succesfully created a MSDE 2000 rel A backend on 2003
> server. I can connect a MS Access project frontend to it
> from an XP client on the same LAN segment. I can connect
> the same frontend over the internet to this server when
> set out in the firewall's DMZ.
> And now for my next trick! When I tuck the MSDE server
> back behind the firewall and open up TCP and UDP ports at
> 1433 and 1434 for both incoming and outgoing traffic, I
> cannot connect. I include a filtered log showing traffic
> between the Access client on the Internet and the firewall
> for detail. It appears that the Netgear firewall passes
> packets to the server but it times out in a little less
> than a minute... I am looking forward to any ideas that
> may move this project forward!
> Time Protocol Src Dst Application
> Message
> 13:58:28 UDP 64552 1434 ms-sql-m
> [Service access request successful]
> 13:58:28 TCP 64553 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:31 TCP 64553 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:37 TCP 64553 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:51 TCP 64558 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:54 TCP 64558 2418 cas [Access
> Policy not found, dropping packet]
> 13:59:00 TCP 64558 2418 cas [Access
> Policy not found, dropping packet]
> 13:59:14 TCP 64564 445 ms-ds [Access
> Policy not found, dropping packet]
> 13:59:14 TCP 64565 139 netbios-ssn
> [Access Policy not found, dropping packet]
> 13:59:17 TCP 64565 139 netbios-ssn
> [Access Policy not found, dropping packet]
> 13:59:17 TCP 64564 445 ms-ds [Access
> Policy not found, dropping packet]
> 13:59:20 UDP 64552 1434 ms-sql-m
> [Connection timed out.Bytes transferred : 137]
> 13:59:23 TCP 64565 139 netbios-ssn
> [Access Policy not found, dropping packet]
> 13:59:23 TCP 64564 445 ms-ds [Access
> Policy not found, dropping packet]
>

MSDE over firewall

Succesfully created a MSDE 2000 rel A backend on 2003
server. I can connect a MS Access project frontend to it
from an XP client on the same LAN segment. I can connect
the same frontend over the internet to this server when
set out in the firewall's DMZ.
And now for my next trick! When I tuck the MSDE server
back behind the firewall and open up TCP and UDP ports at
1433 and 1434 for both incoming and outgoing traffic, I
cannot connect. I include a filtered log showing traffic
between the Access client on the Internet and the firewall
for detail. It appears that the Netgear firewall passes
packets to the server but it times out in a little less
than a minute... I am looking forward to any ideas that
may move this project forward!
Time Protocol Src Dst Application
Message
13:58:28 UDP 64552 1434 ms-sql-m
[Service access request successful]
13:58:28 TCP 64553 2418 cas [Access
Policy not found, dropping packet]
13:58:31 TCP 64553 2418 cas [Access
Policy not found, dropping packet]
13:58:37 TCP 64553 2418 cas [Access
Policy not found, dropping packet]
13:58:51 TCP 64558 2418 cas [Access
Policy not found, dropping packet]
13:58:54 TCP 64558 2418 cas [Access
Policy not found, dropping packet]
13:59:00 TCP 64558 2418 cas [Access
Policy not found, dropping packet]
13:59:14 TCP 64564 445 ms-ds [Access
Policy not found, dropping packet]
13:59:14 TCP 64565 139 netbios-ssn
[Access Policy not found, dropping packet]
13:59:17 TCP 64565 139 netbios-ssn
[Access Policy not found, dropping packet]
13:59:17 TCP 64564 445 ms-ds [Access
Policy not found, dropping packet]
13:59:20 UDP 64552 1434 ms-sql-m
[Connection timed out.Bytes transferred : 137]
13:59:23 TCP 64565 139 netbios-ssn
[Access Policy not found, dropping packet]
13:59:23 TCP 64564 445 ms-ds [Access
Policy not found, dropping packet]From your trace it appears that many more IP ports (than 1433 & 1434) are
being attempted to be used.
I suspect it's failing because of the attempt to do name resolution.
Steve
"Ed Morra" <ed@.orl-inc.com> wrote in message
news:36f801c4297b$6a642240$a601280a@.phx.gbl...
> Succesfully created a MSDE 2000 rel A backend on 2003
> server. I can connect a MS Access project frontend to it
> from an XP client on the same LAN segment. I can connect
> the same frontend over the internet to this server when
> set out in the firewall's DMZ.
> And now for my next trick! When I tuck the MSDE server
> back behind the firewall and open up TCP and UDP ports at
> 1433 and 1434 for both incoming and outgoing traffic, I
> cannot connect. I include a filtered log showing traffic
> between the Access client on the Internet and the firewall
> for detail. It appears that the Netgear firewall passes
> packets to the server but it times out in a little less
> than a minute... I am looking forward to any ideas that
> may move this project forward!
> Time Protocol Src Dst Application
> Message
> 13:58:28 UDP 64552 1434 ms-sql-m
> [Service access request successful]
> 13:58:28 TCP 64553 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:31 TCP 64553 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:37 TCP 64553 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:51 TCP 64558 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:54 TCP 64558 2418 cas [Access
> Policy not found, dropping packet]
> 13:59:00 TCP 64558 2418 cas [Access
> Policy not found, dropping packet]
> 13:59:14 TCP 64564 445 ms-ds [Access
> Policy not found, dropping packet]
> 13:59:14 TCP 64565 139 netbios-ssn
> [Access Policy not found, dropping packet]
> 13:59:17 TCP 64565 139 netbios-ssn
> [Access Policy not found, dropping packet]
> 13:59:17 TCP 64564 445 ms-ds [Access
> Policy not found, dropping packet]
> 13:59:20 UDP 64552 1434 ms-sql-m
> [Connection timed out.Bytes transferred : 137]
> 13:59:23 TCP 64565 139 netbios-ssn
> [Access Policy not found, dropping packet]
> 13:59:23 TCP 64564 445 ms-ds [Access
> Policy not found, dropping packet]
>

MSDE no show in server explorer

I have installed default instance of SQLServer 2005 DE on Windows Server 2003 host. I also installed a named instance of MSDE rel A. I can connect to the MSDE instance from Management Studio but it does not appear in the list of servers when I try to add the connection in VS2005 server explorer. What am I doing wrong?

- Dick

Anybody?

I can connect to the named MSDE instance (now upgraded to SP4) with management studio and osql, but it does not appear in the server list in VS2005 studio explorer, or in the OS ODBC DataSources utility.

The log shows the MSDE instance is listening on shared memory. I cannot configure it for named pipes because I can only see the default SS2K5 instance in SQL Server Configuration Manager.

All contributions massively appreciated.

|||

MSDE instances listening only on shared memory generally do not show up in the list boxes you mention.

You can configure the MSDE to listen on named pipes (or TCP) through the Server Network Utility.

|||

Thanks Peter

That cracked it. Here's what I did:

- I ran Microsoft SQL Server\80\Tools\binn\SVRNETCN.exe and enabled Named Pipes and TCP/IP

- restarted the server instance but it did not fix it.

- rebooted the machine, got various system errors e.g. reporting services could not connect to db. There was a conflict on port 1433.

- re-ran Server Network Configuration utility, set TCP/IP port to 0. (Bit confused by this, I thought MSDE sp 3 sorted out port sharing issue ...? I havn't tried a remote connection yet)

- Ran SQL Configuration Manager and created np aliases for both the default and named instances.

- rebooted and everything fixed. Able to create a System DSN. MSDE instance did not appear in server list when I tried to add a new a connection in VS2005 server explorer, but I was able to type in the server name and connect ok.

As a general observation I have to say I am not a member of SQL Server 2005 fan club yet. It promises simplicity, but delivers frustration.

MSDE installation failure

I am trying to install MSDE 2000 rel A onto a machine running Win XP Pro SP2,
Keep getting error failed to configure the server and my error logs show this
message "Specified driver could not be loaded due to system error 126 (SQL
Server)." Everything that I have found refers to MDAC issues but SP2
installs the latest MDAC 2.81. I ran component checked and everything matched
when run for 2.8 on XP SP2. The only thing Not Found were odbdbcp.dll
sqlsvr32.dll and sqlsvr32.rll and according to documentation Not Found
just means they were not used in the version selected. Any ideas?
Hi,
I'm not sure, but I heard somewhere that MSDE 2000 relA (or sp3a), cann't be
installed on top of Windows XP SP2.
You must uninstall SP2, install MSDE sp3a and reinstall SP2.
I didn't test it.
HTH
AF
"FirePro2005" <FirePro2005@.discussions.microsoft.com> wrote in message
news:3EC1D631-6F00-4B85-A964-FFE79313533A@.microsoft.com...
> I am trying to install MSDE 2000 rel A onto a machine running Win XP Pro
SP2,
> Keep getting error failed to configure the server and my error logs show
this
> message "Specified driver could not be loaded due to system error 126
(SQL
> Server)." Everything that I have found refers to MDAC issues but SP2
> installs the latest MDAC 2.81. I ran component checked and everything
matched
> when run for 2.8 on XP SP2. The only thing Not Found were odbdbcp.dll
> sqlsvr32.dll and sqlsvr32.rll and according to documentation Not
Found
> just means they were not used in the version selected. Any ideas?
|||I have installed MSDE 2000 Rel A on a quite a few machines with XP and
SP2 without such issues. My issue had always been the same - inability
to connect from a remote system. I have finally figure out that by
default MSDE does not install with Network mode turned on. On top of
that, SP 2 blocks all ports, including 1433 used by MSDE, in the
firewall.
So, I have learned to install with the "Mized Mode Authentication"
turned on and also to open up Port 1433.
- manzoor

MSDE Install

Running MSDE 2000 Rel A install with the following information:
[Setup.ini File]
[Options]
DISABLENETWORKPROTOCOLS=0
SECURITYMODE=SQL
Step 2: Reboot -- Ensure service starts.
Step 3: Extract Service Pack 4
Step 4: Run Service Pack 4 for MSDE
Step 5: Error on install of Service Pack 4 -- Specified 'Instance Name could
not be found'
Any work-arounds for Step 5 ?
Uninstalling MSDE 2000 Rel a does not uninstall all registry entrys, and
rerunning the setup files does not work and gives the following error:
'Specified Instance Name' could not be found.
Seems to work fine by taking a previous system restore point...
Are they bugs ?
I launched the MSDE 2000 Rel A(SP3) install with the following command line:
setup.exe SAPWD="sa" INSTANCENAME="Image_Archive" DISABLENETWORKPROTOCOLS=1
SECURITYMODE=SQL
After reboot the MSDE works fine.
Downloading and extract SP4 for MSDE and try to launch with the following
command line will failed:
setup.exe /upgradesp sqlrun INSTANCENAME="Image_Archive" SECURITYMODE=SQL
UPGRADEUSER=sa UPGRADEPWD=sa /L*v C:\MSDESP4Install.log
The error message that displayed:
"This product is not installed. Check if a appropiate instance of MSDE is
installed."
Ok button.
After this installation failure I try on a clean machine to install MSDE SP3
without instance name:
setup.exe SAPWD="sa" DISABLENETWORKPROTOCOLS=1 SECURITYMODE=SQL
After reboot the MSDE works fine.
Launch the SP4 with the following command line will success:
setup.exe /upgradesp sqlrun SECURITYMODE=SQL UPGRADEUSER=sa UPGRADEPWD=sa
/L*v C:\MSDESP4Install.log
So my question is the same: Is this a bug?
It seems to me that with instance name doesn't work the upgrade or I'm
missed somewhere.
|||hi,
Ketchup wrote:
> setup.exe /upgradesp sqlrun INSTANCENAME="Image_Archive"
> SECURITYMODE=SQL UPGRADEUSER=sa UPGRADEPWD=sa /L*v
> C:\MSDESP4Install.log
try INSTANCENAME=Image_Archive
without quotes..
seem to remember this solved the problem last time I upgraded a named
instance to sp4
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.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 Andrea!That's the solution.
"Andrea Montanari" wrote:

>try INSTANCENAME=Image_Archive
> without quotes..

MSDE Error !

Hi,
When I try to insert 7 to 8 million of rows in MSDE Rel A
version. I get the following error "Unknown token
received from SQL Server". My simulation testing was
running fine untill 4.3 million rows in a single table.
I executed sp_spaceused system stored procedure. I get
the results as follows
DATABASE :LaneDB
DATABASE SIZE: 703.50 MB
UNALLOCATED SPACE: 105.25 MB
Please help if i am missing something.
David
hi David,
"David" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:1b8c01c4e1c3$2e20a460$a401280a@.phx.gbl
> Hi,
> When I try to insert 7 to 8 million of rows in MSDE Rel A
> version. I get the following error "Unknown token
> received from SQL Server". My simulation testing was
> running fine untill 4.3 million rows in a single table.
> I executed sp_spaceused system stored procedure. I get
> the results as follows
> DATABASE :LaneDB
> DATABASE SIZE: 703.50 MB
> UNALLOCATED SPACE: 105.25 MB
> Please help if i am missing something.
> David
unfortunately there are a number of conditions that can cause this. Please
do check if your process matches any of these known bugs
http://support.microsoft.com/search/...false&numDays=
&MaxResults=25&srchstep=2&InCC_hdn=true&querySourc e=gASr_Query
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