Please could somebody help with the following problem? I know this may not
quite be the right newgroup to ask this question, but it is related to the
databse.
I have just installed a new install of XP Professional SP2 on my computer,
installed all the latest security updates using Windows Update. Installed XP
Embedded in the order of the splash screen menu, which included the install
on MSDE. Once installed I run a test
build which seemed to go OK, however after restarting the PC I now get the
following message when I try and run Target Designer or Component Database
Manager.
"Target Designer cannot log on to the component database on 'PC001'.
Possible causes: the database is already open by another user in exclusive
mode, or the database does not exist on server, or you do not have permission
to access the databse."
I am not sure how to check for the above or how to rectify this problem,
would appreciate some assistance.
Thanks.
hi,
skylark wrote:
> Please could somebody help with the following problem? I know this
> may not quite be the right newgroup to ask this question, but it is
> related to the databse.
> I have just installed a new install of XP Professional SP2 on my
> computer, installed all the latest security updates using Windows
> Update. Installed XP Embedded in the order of the splash screen menu,
> which included the install on MSDE. Once installed I run a test
> build which seemed to go OK, however after restarting the PC I now
> get the following message when I try and run Target Designer or
> Component Database Manager.
> "Target Designer cannot log on to the component database on 'PC001'.
> Possible causes: the database is already open by another user in
> exclusive mode, or the database does not exist on server, or you do
> not have permission to access the databse."
> I am not sure how to check for the above or how to rectify this
> problem, would appreciate some assistance.
I'm not confortable with this scenario, but IMHO this has nothing to do with
MSDE...
http://msdn.microsoft.com/library/de...ignerGuide.asp
it seems to me more related to Component Database Manager,
http://msdn.microsoft.com/library/de...nagerguide.asp ,
but agian, no idea at all about this package..
perhaps you'll have mor luck asing in microsoft.public.windowsxp.embedded
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
Showing posts with label somebody. Show all posts
Showing posts with label somebody. Show all posts
Friday, March 23, 2012
Monday, February 20, 2012
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
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--
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"
--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
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
Subscribe to:
Posts (Atom)