MSDE install - problem

hi,
i want to install MSDE (comes with windows embedded designer)
install stops with following event:
ERROR:
event 19011 source MSSQLServer
FillAddress(MSAFD Tcpip [TCP/IPv6]) : Error 0.
WARNING:
event 19011 source MSSQLServer
(SpnRegister) : Error 1355.
any suggestions?
hi,
Zabby wrote:
> hi,
> i want to install MSDE (comes with windows embedded designer)
> install stops with following event:
> ERROR:
> event 19011 source MSSQLServer
> FillAddress(MSAFD Tcpip [TCP/IPv6]) : Error 0.
> WARNING:
> event 19011 source MSSQLServer
> (SpnRegister) : Error 1355.
> any suggestions?
if you can manually install MSDE your self, try adding the
/L*v "c:\msdelog.txt"
parameter to your call to setup.exe bootstrap installer in order to enable
verbose logging of the installation process... you can then ispect the
resulting log text file for
RETURN VALUE 3
entries... about 10 lines before each entry some (sometime cryptic)
description of the found problem will be reported..
please verify File & Printer Sharing is enabled and the Server service up
and running...
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
|||thats my error:
Executing "C:\Programme\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe -V 1
-M 1 -U sa -I "MSSQLSERVER" -Q "Latin1_General_CI_AS""
MSI (c) (A8:A4) [11:05:57:062]: Font created. Charset: Req=0, Ret=0, Font:
Req=MS Shell Dlg, Ret=MS Shell Dlg
Setup failed to configure the server. Refer to the server error logs and
setup error logs for more information.
MSI (s) (CC!CC) [11:06:00:562]: Product: Microsoft SQL Server Desktop Engine
-- Setup failed to configure the server. Refer to the server error logs and
setup error logs for more information.
"Andrea Montanari" wrote:

> hi,
> Zabby wrote:
> if you can manually install MSDE your self, try adding the
> /L*v "c:\msdelog.txt"
> parameter to your call to setup.exe bootstrap installer in order to enable
> verbose logging of the installation process... you can then ispect the
> resulting log text file for
> RETURN VALUE 3
> entries... about 10 lines before each entry some (sometime cryptic)
> description of the found problem will be reported..
> please verify File & Printer Sharing is enabled and the Server service up
> and running...
> --
> 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,
Zabby wrote:
> thats my error:
> Executing "C:\Programme\Microsoft SQL
> Server\80\Tools\Binn\cnfgsvr.exe -V 1 -M 1 -U sa -I "MSSQLSERVER" -Q
> "Latin1_General_CI_AS""
> MSI (c) (A8:A4) [11:05:57:062]: Font created. Charset: Req=0, Ret=0,
> Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
> Setup failed to configure the server. Refer to the server error logs
> and setup error logs for more information.
> MSI (s) (CC!CC) [11:06:00:562]: Product: Microsoft SQL Server Desktop
> Engine -- Setup failed to configure the server. Refer to the server
> error logs and setup error logs for more information.
this problem is usually associated to previously uninstalled instance of
MSDE, as described in
http://support.microsoft.com/default...99&Product=sql
it has been sometime reported to MDAC corruption on WinXP sp2, so I do not
know if it applys to Win2003 too, but Win2003 sp1 include the very same MDAC
stack (2.8 sp2) as WinXP sp2, you can fix as described in
http://www.macropool.com/en/download/mdac_xp_sp2.html
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!
grat job!
"Andrea Montanari" wrote:

> hi,
> Zabby wrote:
> this problem is usually associated to previously uninstalled instance of
> MSDE, as described in
> http://support.microsoft.com/default...99&Product=sql
> it has been sometime reported to MDAC corruption on WinXP sp2, so I do not
> know if it applys to Win2003 too, but Win2003 sp1 include the very same MDAC
> stack (2.8 sp2) as WinXP sp2, you can fix as described in
> http://www.macropool.com/en/download/mdac_xp_sp2.html
> --
> 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 Error 70000

Hello, everyone
Can somebody clarify what type of ther error it is ?
Event Type: Information
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 2/23/2006
Time: 3:01:03 PM
User: N/A
Computer: XXX
Description:
Error: 70000, Severity: 10, State: 1
Input buffer for processes 295: exec sp_XXX 1429, 0, 1475
System error numbers are up to 50000. So 70000 must be a user error
number assigned by the vendor/developer to some event. I don't think
there's anything anyone here can do to help you with that one, you need
to ask the vendor. Note, severity 10 is considered an informational
message only so perhaps it's nothing to be concerned about - once again,
ask the vendor (looks to me kind of like a debug statement - "this
(badly named) proc is being called with these parameters by this SPID").
*mike hodgson*
http://sqlnerd.blogspot.com
Djangar S. wrote:

>Hello, everyone
>Can somebody clarify what type of ther error it is ?
>Event Type: Information
>Event Source: MSSQLSERVER
>Event Category: (2)
>Event ID: 17052
>Date: 2/23/2006
>Time: 3:01:03 PM
>User: N/A
>Computer: XXX
>Description:
>Error: 70000, Severity: 10, State: 1
>Input buffer for processes 295: exec sp_XXX 1429, 0, 1475
>
>
|||Thanks, Mike
"Mike Hodgson" <e1minst3r@.gmail.com> wrote in message news:e%23a99$NOGHA.532@.TK2MSFTNGP15.phx.gbl...
System error numbers are up to 50000. So 70000 must be a user error number assigned by the vendor/developer to some event. I don't think there's anything anyone here can do to help you with that one, you need to ask the vendor. Note, severity 10 is considered an informational message only so perhaps it's nothing to be concerned about - once again, ask the vendor (looks to me kind of like a debug statement - "this (badly named) proc is being called with these parameters by this SPID").
mike hodgson
http://sqlnerd.blogspot.com
Djangar S. wrote:
Hello, everyone
Can somebody clarify what type of ther error it is ?
Event Type: Information
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 2/23/2006
Time: 3:01:03 PM
User: N/A
Computer: XXX
Description:
Error: 70000, Severity: 10, State: 1
Input buffer for processes 295: exec sp_XXX 1429, 0, 1475

MSDE Error 70000

Hello, everyone
Can somebody clarify what type of ther error it is ?
Event Type: Information
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 2/23/2006
Time: 3:01:03 PM
User: N/A
Computer: XXX
Description:
Error: 70000, Severity: 10, State: 1
Input buffer for processes 295: exec sp_XXX 1429, 0, 1475This is a multi-part message in MIME format.
--080606060502060508030601
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
System error numbers are up to 50000. So 70000 must be a user error
number assigned by the vendor/developer to some event. I don't think
there's anything anyone here can do to help you with that one, you need
to ask the vendor. Note, severity 10 is considered an informational
message only so perhaps it's nothing to be concerned about - once again,
ask the vendor (looks to me kind of like a debug statement - "this
(badly named) proc is being called with these parameters by this SPID").
--
*mike hodgson*
http://sqlnerd.blogspot.com
Djangar S. wrote:
>Hello, everyone
>Can somebody clarify what type of ther error it is ?
>Event Type: Information
>Event Source: MSSQLSERVER
>Event Category: (2)
>Event ID: 17052
>Date: 2/23/2006
>Time: 3:01:03 PM
>User: N/A
>Computer: XXX
>Description:
>Error: 70000, Severity: 10, State: 1
>Input buffer for processes 295: exec sp_XXX 1429, 0, 1475
>
>
--080606060502060508030601
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>System error numbers are up to 50000. So 70000 must be a user
error number assigned by the vendor/developer to some event. I don't
think there's anything anyone here can do to help you with that one,
you need to ask the vendor. Note, severity 10 is considered an
informational message only so perhaps it's nothing to be concerned
about - once again, ask the vendor (looks to me kind of like a debug
statement - "this (badly named) proc is being called with these
parameters by this SPID").</tt><br>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span> <b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2"><a href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
Djangar S. wrote:
<blockquote cite="mid%23FuN0yMOGHA.2696@.TK2MSFTNGP14.phx.gbl"
type="cite">
<pre wrap="">Hello, everyone
Can somebody clarify what type of ther error it is ?
Event Type: Information
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 2/23/2006
Time: 3:01:03 PM
User: N/A
Computer: XXX
Description:
Error: 70000, Severity: 10, State: 1
Input buffer for processes 295: exec sp_XXX 1429, 0, 1475
</pre>
</blockquote>
</body>
</html>
--080606060502060508030601--|||This is a multi-part message in MIME format.
--=_NextPart_000_0014_01C63933.5F319C80
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Thanks, Mike
"Mike Hodgson" <e1minst3r@.gmail.com> wrote in message =news:e%23a99$NOGHA.532@.TK2MSFTNGP15.phx.gbl...
System error numbers are up to 50000. So 70000 must be a user error =number assigned by the vendor/developer to some event. I don't think =there's anything anyone here can do to help you with that one, you need =to ask the vendor. Note, severity 10 is considered an informational =message only so perhaps it's nothing to be concerned about - once again, =ask the vendor (looks to me kind of like a debug statement - "this =(badly named) proc is being called with these parameters by this SPID").
--
mike hodgson
http://sqlnerd.blogspot.com=20
Djangar S. wrote: Hello, everyone
Can somebody clarify what type of ther error it is ?
Event Type: Information
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 2/23/2006
Time: 3:01:03 PM
User: N/A
Computer: XXX
Description:
Error: 70000, Severity: 10, State: 1
Input buffer for processes 295: exec sp_XXX 1429, 0, 1475
--=_NextPart_000_0014_01C63933.5F319C80
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

---

Thanks, Mike
"Mike Hodgson" wrote =in message news:e%23a99$NOGHA.5=32@.TK2MSFTNGP15.phx.gbl...System error numbers are up to 50000. So 70000 must be a user error =number assigned by the vendor/developer to some event. I don't think =there's anything anyone here can do to help you with that one, you need to ask =the vendor. Note, severity 10 is considered an informational message =only so perhaps it's nothing to be concerned about - once again, ask the =vendor (looks to me kind of like a debug statement - "this (badly named) proc is =being called with these parameters by this SPID").
--mike =hodgsonhttp://sqlnerd.blogspot.com Djangar S. wrote: Hello, everyone
Can somebody clarify what type of ther error it is ?
Event Type: Information
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 2/23/2006
Time: 3:01:03 PM
User: N/A
Computer: XXX
Description:
Error: 70000, Severity: 10, State: 1
Input buffer for processes 295: exec sp_XXX 1429, 0, 1475

---

--=_NextPart_000_0014_01C63933.5F319C80--

MSDE Error 70000

Hello, everyone
Can somebody clarify what type of ther error it is ?
Event Type: Information
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 2/23/2006
Time: 3:01:03 PM
User: N/A
Computer: XXX
Description:
Error: 70000, Severity: 10, State: 1
Input buffer for processes 295: exec sp_XXX 1429, 0, 1475System error numbers are up to 50000. So 70000 must be a user error
number assigned by the vendor/developer to some event. I don't think
there's anything anyone here can do to help you with that one, you need
to ask the vendor. Note, severity 10 is considered an informational
message only so perhaps it's nothing to be concerned about - once again,
ask the vendor (looks to me kind of like a debug statement - "this
(badly named) proc is being called with these parameters by this SPID").
*mike hodgson*
http://sqlnerd.blogspot.com
Djangar S. wrote:

>Hello, everyone
>Can somebody clarify what type of ther error it is ?
>Event Type: Information
>Event Source: MSSQLSERVER
>Event Category: (2)
>Event ID: 17052
>Date: 2/23/2006
>Time: 3:01:03 PM
>User: N/A
>Computer: XXX
>Description:
>Error: 70000, Severity: 10, State: 1
>Input buffer for processes 295: exec sp_XXX 1429, 0, 1475
>
>|||Thanks, Mike
"Mike Hodgson" <e1minst3r@.gmail.com> wrote in message news:e%23a99$NOGHA.532
@.TK2MSFTNGP15.phx.gbl...
System error numbers are up to 50000. So 70000 must be a user error number
assigned by the vendor/developer to some event. I don't think there's anyth
ing anyone here can do to help you with that one, you need to ask the vendor
. Note, severity 10 is considered an informational message only so perhaps
it's nothing to be concerned about - once again, ask the vendor (looks to me
kind of like a debug statement - "this (badly named) proc is being called w
ith these parameters by this SPID").
mike hodgson
http://sqlnerd.blogspot.com
Djangar S. wrote:
Hello, everyone
Can somebody clarify what type of ther error it is ?
Event Type: Information
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 2/23/2006
Time: 3:01:03 PM
User: N/A
Computer: XXX
Description:
Error: 70000, Severity: 10, State: 1
Input buffer for processes 295: exec sp_XXX 1429, 0, 1475