I created a install shield package on windows 98 using the
MSDE merge modules with vb .net. It works fine on 2000 and
xp but on windows 98 it give an ambiguous error: "Error
1723. Theres a problem with this windows installer
package. A DLL required for this installation to complete
could not be run."
This happenes as soon as I click on the msi file. Or if I
click the setup file then after a couple checks and when
setup tryes running the msi file.
Anyone have any ideas what it could be? Which dlls? Which
merge modules could be missing?
Any help would greatly appreciated. I've lost some hair
over this one.
You probably don't have any version of MDAC installed on the Win98 system.
Make MDAC a dependency of your install and install it first if needed before
going forward.
J
"MSDE" <Sebastian@.ilogic.com> wrote in message
news:1ebc01c49a69$81a56400$a301280a@.phx.gbl...
> I created a install shield package on windows 98 using the
> MSDE merge modules with vb .net. It works fine on 2000 and
> xp but on windows 98 it give an ambiguous error: "Error
> 1723. Theres a problem with this windows installer
> package. A DLL required for this installation to complete
> could not be run."
> This happenes as soon as I click on the msi file. Or if I
> click the setup file then after a couple checks and when
> setup tryes running the msi file.
> Anyone have any ideas what it could be? Which dlls? Which
> merge modules could be missing?
> Any help would greatly appreciated. I've lost some hair
> over this one.
|||The other problems we've found with Win98 are if file sharing isn't enabled
or if the Windows Family Logon is enabled.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Jim Young" <thorium48@.hotmail.com> wrote in message
news:O3HnrMrnEHA.132@.TK2MSFTNGP09.phx.gbl...
> You probably don't have any version of MDAC installed on the Win98 system.
> Make MDAC a dependency of your install and install it first if needed
before
> going forward.
> J
> "MSDE" <Sebastian@.ilogic.com> wrote in message
> news:1ebc01c49a69$81a56400$a301280a@.phx.gbl...
>
Showing posts with label win. Show all posts
Showing posts with label win. Show all posts
Friday, March 23, 2012
MSDE over SQL 2005 accidentaly - how to restore SQL 2005?
Hello all!
I write this post on behalf of my colleagues so I don't know a full picture
but this is the situation:
On a Win 2k3 machine with a SQL Server 2005 installed, a colleague
mistakenly installed a software (MBS Navision) with an option for MSDE
installation checked. The result turned out to be non-functional SQL Server
2005 that cannot be reinstalled, removed or repared.
Is there a way to remove the MSDE components and repair or reinstall SQL
Server 2005 without formatting?
Thank youin advance,
HrvojeGu
"Hrvoje Vrbanc" wrote:
> Hello all!
> I write this post on behalf of my colleagues so I don't know a full pictur
e
> but this is the situation:
> On a Win 2k3 machine with a SQL Server 2005 installed, a colleague
> mistakenly installed a software (MBS Navision) with an option for MSDE
> installation checked. The result turned out to be non-functional SQL Serve
r
> 2005 that cannot be reinstalled, removed or repared.
> Is there a way to remove the MSDE components and repair or reinstall SQL
> Server 2005 without formatting?
> Thank youin advance,
> Hrvoje
>
Have you checked out http://support.microsoft.com/kb/290991 on how to remove
SQL 2000 manually.
To remove SQL 2005 manually see http://support.microsoft.com/kb/909967
although there is a command line option to reinstall (REINSTALLMODE) the
instance see http://msdn2.microsoft.com/en-us/library/ms144259.aspx
Johnsql
I write this post on behalf of my colleagues so I don't know a full picture
but this is the situation:
On a Win 2k3 machine with a SQL Server 2005 installed, a colleague
mistakenly installed a software (MBS Navision) with an option for MSDE
installation checked. The result turned out to be non-functional SQL Server
2005 that cannot be reinstalled, removed or repared.
Is there a way to remove the MSDE components and repair or reinstall SQL
Server 2005 without formatting?
Thank youin advance,
HrvojeGu
"Hrvoje Vrbanc" wrote:
> Hello all!
> I write this post on behalf of my colleagues so I don't know a full pictur
e
> but this is the situation:
> On a Win 2k3 machine with a SQL Server 2005 installed, a colleague
> mistakenly installed a software (MBS Navision) with an option for MSDE
> installation checked. The result turned out to be non-functional SQL Serve
r
> 2005 that cannot be reinstalled, removed or repared.
> Is there a way to remove the MSDE components and repair or reinstall SQL
> Server 2005 without formatting?
> Thank youin advance,
> Hrvoje
>
Have you checked out http://support.microsoft.com/kb/290991 on how to remove
SQL 2000 manually.
To remove SQL 2005 manually see http://support.microsoft.com/kb/909967
although there is a command line option to reinstall (REINSTALLMODE) the
instance see http://msdn2.microsoft.com/en-us/library/ms144259.aspx
Johnsql
Monday, March 19, 2012
MSDE login problem - Windows
I'm confused.
OS = Win XP Pro
I installed MSDE2000A on a new laptop using mixed security - Windows and
SQL. Everything went fine. At the time my everyday Windows user account wa
s
set up as a Windows (not SQL) administrator, so that I could get some other
software installed, too.
I subsequently changed my Windows user account to be a power user and NOT a
Windows administrator and now I cannot connect to MSDE with that Windows
account. If I switch the account back to Windows adminstrator all is well
with MSDE.
How can I coax MSDE to recognize this user account when it is no longer a
Windows administrator?Add your windows account to the Logins for MSDE. You are
getting in due to the default behavior of SQL Server adding
BUILTIN\Administrators as a login. That would include all
logins that are members of the local admins group.
You can add your login using sp_grantlogin. You can find
more information in books online.
-Sue
On Mon, 9 Jan 2006 08:07:04 -0800, "Duke Carey"
<DukeCarey@.discussions.microsoft.com> wrote:
>I'm confused.
>OS = Win XP Pro
>I installed MSDE2000A on a new laptop using mixed security - Windows and
>SQL. Everything went fine. At the time my everyday Windows user account w
as
>set up as a Windows (not SQL) administrator, so that I could get some other
>software installed, too.
>I subsequently changed my Windows user account to be a power user and NOT a
>Windows administrator and now I cannot connect to MSDE with that Windows
>account. If I switch the account back to Windows adminstrator all is well
>with MSDE.
>How can I coax MSDE to recognize this user account when it is no longer a
>Windows administrator?
>|||Sue -
Thanks for the guidance, but it looks like sp_grantlogin requires me to use
a domain name. The laptop is not part of a domain. Is there a workaround
for that?
"Sue Hoegemeier" wrote:
> Add your windows account to the Logins for MSDE. You are
> getting in due to the default behavior of SQL Server adding
> BUILTIN\Administrators as a login. That would include all
> logins that are members of the local admins group.
> You can add your login using sp_grantlogin. You can find
> more information in books online.
> -Sue
> On Mon, 9 Jan 2006 08:07:04 -0800, "Duke Carey"
> <DukeCarey@.discussions.microsoft.com> wrote:
>
>|||If you are logging into the laptop using a local account,
you would use:
MachineName\LoginName
-Sue
On Mon, 9 Jan 2006 16:29:02 -0800, "Duke Carey"
<DukeCarey@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Sue -
>Thanks for the guidance, but it looks like sp_grantlogin requires me to use
>a domain name. The laptop is not part of a domain. Is there a workaround
>for that?
>"Sue Hoegemeier" wrote:
>|||Sue -
I logged in to the laptop as Administrator and was automatically logged in
to MSDE. Within MSDE I then ran EXEC sp_grantlogin 'pc_name\duke' and it ra
n
successfully.
However, after logging in as Duke *without Windows administrator rights* I
was still unable to login to MSDE.
I have to be so dense, but what am I missing?
Duke
"Sue Hoegemeier" wrote:
> If you are logging into the laptop using a local account,
> you would use:
> MachineName\LoginName
> -Sue
> On Mon, 9 Jan 2006 16:29:02 -0800, "Duke Carey"
> <DukeCarey@.discussions.microsoft.com> wrote:
>
>|||If the login is there, you should be able to at least
connect.
So when you log in as Duke and try to log in to MSDE, what
is the exact error message - all the details?
-Sue
On Thu, 19 Jan 2006 08:24:04 -0800, "Duke Carey"
<DukeCarey@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Sue -
>I logged in to the laptop as Administrator and was automatically logged in
>to MSDE. Within MSDE I then ran EXEC sp_grantlogin 'pc_name\duke' and it r
an
>successfully.
>However, after logging in as Duke *without Windows administrator rights* I
>was still unable to login to MSDE.
>I have to be so dense, but what am I missing?
>Duke
>"Sue Hoegemeier" wrote:
>|||Sue -
There are no error messages as such
What is happening is that the SQL Service Mgr in the systray shows an empty
circle. When I open it I have to type in the pc name and select SQL Server
as the service. It then shows that it is already running. When I go into
MSDE Manager (Vale Software's management tool), it shows me logged in as
guest. It also shows the database owner (there's only one user database so
far) as hp_notebook\duke and says that I do not have permisssion to access
that database
If I grant my Windows login Windows Administrator status, MSDE starts fine
and I log in to the MSDE as myself
I don't know enough to provide you more helpful information
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:1q00t11aka3drrkih9ev7rofpbidk5c6dr@.
4ax.com...
> If the login is there, you should be able to at least
> connect.
> So when you log in as Duke and try to log in to MSDE, what
> is the exact error message - all the details?
> -Sue
>|||Okay...so you get on the server but can't do anything in
that database or can't access the database.
Add your Duke login as a user in the database using
sp_grantdbaccess.
If you need that login to be able to do anything and
everything on the MSDE instance, you can add that login to
the sysadmins server role using:
EXEC sp_addsrvrolemember 'pc_name\duke', 'sysadmin'
-Sue
On Thu, 19 Jan 2006 19:02:51 -0500, "Duke Carey"
<dukecarey@.hotmail.com> wrote:
> When I go into
>MSDE Manager (Vale Software's management tool), it shows me logged in as
>guest. It also shows the database owner (there's only one user database so
>far) as hp_notebook\duke and says that I do not have permisssion to access
>that database|||Sue -
Thanks for sticking with me. It appears that things are working correctly
now.
EXEC sp_addsrvrolemember 'pc_name\duke', 'sysadmin' seems to have done the
trick.
"Sue Hoegemeier" wrote:
> Okay...so you get on the server but can't do anything in
> that database or can't access the database.
> Add your Duke login as a user in the database using
> sp_grantdbaccess.
> If you need that login to be able to do anything and
> everything on the MSDE instance, you can add that login to
> the sysadmins server role using:
> EXEC sp_addsrvrolemember 'pc_name\duke', 'sysadmin'
> -Sue
> On Thu, 19 Jan 2006 19:02:51 -0500, "Duke Carey"
> <dukecarey@.hotmail.com> wrote:
>
>|||Good to hear it's all working now - thanks for posting back!
-Sue
On Mon, 23 Jan 2006 06:31:04 -0800, "Duke Carey"
<DukeCarey@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Sue -
>Thanks for sticking with me. It appears that things are working correctly
>now.
>EXEC sp_addsrvrolemember 'pc_name\duke', 'sysadmin' seems to have done the
>trick.
>
>"Sue Hoegemeier" wrote:
>
OS = Win XP Pro
I installed MSDE2000A on a new laptop using mixed security - Windows and
SQL. Everything went fine. At the time my everyday Windows user account wa
s
set up as a Windows (not SQL) administrator, so that I could get some other
software installed, too.
I subsequently changed my Windows user account to be a power user and NOT a
Windows administrator and now I cannot connect to MSDE with that Windows
account. If I switch the account back to Windows adminstrator all is well
with MSDE.
How can I coax MSDE to recognize this user account when it is no longer a
Windows administrator?Add your windows account to the Logins for MSDE. You are
getting in due to the default behavior of SQL Server adding
BUILTIN\Administrators as a login. That would include all
logins that are members of the local admins group.
You can add your login using sp_grantlogin. You can find
more information in books online.
-Sue
On Mon, 9 Jan 2006 08:07:04 -0800, "Duke Carey"
<DukeCarey@.discussions.microsoft.com> wrote:
>I'm confused.
>OS = Win XP Pro
>I installed MSDE2000A on a new laptop using mixed security - Windows and
>SQL. Everything went fine. At the time my everyday Windows user account w
as
>set up as a Windows (not SQL) administrator, so that I could get some other
>software installed, too.
>I subsequently changed my Windows user account to be a power user and NOT a
>Windows administrator and now I cannot connect to MSDE with that Windows
>account. If I switch the account back to Windows adminstrator all is well
>with MSDE.
>How can I coax MSDE to recognize this user account when it is no longer a
>Windows administrator?
>|||Sue -
Thanks for the guidance, but it looks like sp_grantlogin requires me to use
a domain name. The laptop is not part of a domain. Is there a workaround
for that?
"Sue Hoegemeier" wrote:
> Add your windows account to the Logins for MSDE. You are
> getting in due to the default behavior of SQL Server adding
> BUILTIN\Administrators as a login. That would include all
> logins that are members of the local admins group.
> You can add your login using sp_grantlogin. You can find
> more information in books online.
> -Sue
> On Mon, 9 Jan 2006 08:07:04 -0800, "Duke Carey"
> <DukeCarey@.discussions.microsoft.com> wrote:
>
>|||If you are logging into the laptop using a local account,
you would use:
MachineName\LoginName
-Sue
On Mon, 9 Jan 2006 16:29:02 -0800, "Duke Carey"
<DukeCarey@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Sue -
>Thanks for the guidance, but it looks like sp_grantlogin requires me to use
>a domain name. The laptop is not part of a domain. Is there a workaround
>for that?
>"Sue Hoegemeier" wrote:
>|||Sue -
I logged in to the laptop as Administrator and was automatically logged in
to MSDE. Within MSDE I then ran EXEC sp_grantlogin 'pc_name\duke' and it ra
n
successfully.
However, after logging in as Duke *without Windows administrator rights* I
was still unable to login to MSDE.
I have to be so dense, but what am I missing?
Duke
"Sue Hoegemeier" wrote:
> If you are logging into the laptop using a local account,
> you would use:
> MachineName\LoginName
> -Sue
> On Mon, 9 Jan 2006 16:29:02 -0800, "Duke Carey"
> <DukeCarey@.discussions.microsoft.com> wrote:
>
>|||If the login is there, you should be able to at least
connect.
So when you log in as Duke and try to log in to MSDE, what
is the exact error message - all the details?
-Sue
On Thu, 19 Jan 2006 08:24:04 -0800, "Duke Carey"
<DukeCarey@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Sue -
>I logged in to the laptop as Administrator and was automatically logged in
>to MSDE. Within MSDE I then ran EXEC sp_grantlogin 'pc_name\duke' and it r
an
>successfully.
>However, after logging in as Duke *without Windows administrator rights* I
>was still unable to login to MSDE.
>I have to be so dense, but what am I missing?
>Duke
>"Sue Hoegemeier" wrote:
>|||Sue -
There are no error messages as such
What is happening is that the SQL Service Mgr in the systray shows an empty
circle. When I open it I have to type in the pc name and select SQL Server
as the service. It then shows that it is already running. When I go into
MSDE Manager (Vale Software's management tool), it shows me logged in as
guest. It also shows the database owner (there's only one user database so
far) as hp_notebook\duke and says that I do not have permisssion to access
that database
If I grant my Windows login Windows Administrator status, MSDE starts fine
and I log in to the MSDE as myself
I don't know enough to provide you more helpful information
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:1q00t11aka3drrkih9ev7rofpbidk5c6dr@.
4ax.com...
> If the login is there, you should be able to at least
> connect.
> So when you log in as Duke and try to log in to MSDE, what
> is the exact error message - all the details?
> -Sue
>|||Okay...so you get on the server but can't do anything in
that database or can't access the database.
Add your Duke login as a user in the database using
sp_grantdbaccess.
If you need that login to be able to do anything and
everything on the MSDE instance, you can add that login to
the sysadmins server role using:
EXEC sp_addsrvrolemember 'pc_name\duke', 'sysadmin'
-Sue
On Thu, 19 Jan 2006 19:02:51 -0500, "Duke Carey"
<dukecarey@.hotmail.com> wrote:
> When I go into
>MSDE Manager (Vale Software's management tool), it shows me logged in as
>guest. It also shows the database owner (there's only one user database so
>far) as hp_notebook\duke and says that I do not have permisssion to access
>that database|||Sue -
Thanks for sticking with me. It appears that things are working correctly
now.
EXEC sp_addsrvrolemember 'pc_name\duke', 'sysadmin' seems to have done the
trick.
"Sue Hoegemeier" wrote:
> Okay...so you get on the server but can't do anything in
> that database or can't access the database.
> Add your Duke login as a user in the database using
> sp_grantdbaccess.
> If you need that login to be able to do anything and
> everything on the MSDE instance, you can add that login to
> the sysadmins server role using:
> EXEC sp_addsrvrolemember 'pc_name\duke', 'sysadmin'
> -Sue
> On Thu, 19 Jan 2006 19:02:51 -0500, "Duke Carey"
> <dukecarey@.hotmail.com> wrote:
>
>|||Good to hear it's all working now - thanks for posting back!
-Sue
On Mon, 23 Jan 2006 06:31:04 -0800, "Duke Carey"
<DukeCarey@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Sue -
>Thanks for sticking with me. It appears that things are working correctly
>now.
>EXEC sp_addsrvrolemember 'pc_name\duke', 'sysadmin' seems to have done the
>trick.
>
>"Sue Hoegemeier" wrote:
>
Monday, March 12, 2012
msde licence
we get from a company installed at our customer sides an application using
msde in a win 2000 server (terminal) or higher network enwironment. We have a
lot of troubles because this application is going to let our application fail
often , and we get a lot of instability.
Hi rudolph,
Sorry, but dont' see a question here. Why do you think that the MSDE is
causing instability for your app?
Regards,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"rudolph" <rudolph@.discussions.microsoft.com> wrote in message
news:121817FD-B051-4D59-9690-BDD6DA952ADA@.microsoft.com...
> we get from a company installed at our customer sides an application using
> msde in a win 2000 server (terminal) or higher network enwironment. We
> have a
> lot of troubles because this application is going to let our application
> fail
> often , and we get a lot of instability.
|||Hi Greg!
My question is, that we have done out of a pervasive sql based application
an Interface to a small application. This small application is using msde in
a enviroment, we are using, win 2003 or winn200 Server with terminal clients.
The company, who has done the small aplication we are interfacing has
installed at our clients side either msde or MSSQL Server products, depending
on their stability.We have not been asked by them what they are going to
install I thought, that msde is a client product and not a server product. IS
msde a product which can run simitaniosly in our environment?
"Greg Low [MVP]" wrote:
> Hi rudolph,
> Sorry, but dont' see a question here. Why do you think that the MSDE is
> causing instability for your app?
> Regards,
> --
> Greg Low [MVP]
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "rudolph" <rudolph@.discussions.microsoft.com> wrote in message
> news:121817FD-B051-4D59-9690-BDD6DA952ADA@.microsoft.com...
>
>
|||hi Rudolph,
rudolph wrote:
> Hi Greg!
> My question is, that we have done out of a pervasive sql based
> application an Interface to a small application. This small
> application is using msde in a enviroment, we are using, win 2003 or
> winn200 Server with terminal clients. The company, who has done the
> small aplication we are interfacing has installed at our clients side
> either msde or MSSQL Server products, depending on their stability. We
> have not been asked by them what they are going to install I thought,
> that msde is a client product and not a server product. IS msde a
> product which can run simitaniosly in our environment?
I'm not Greg (hi Greg :D) but, again, I do not understand the "stability"
problems...
MSDE is one of the editions of SQL Server, limited some way, but shares the
same core functionnalities and features...
MSDE is not a client product as Access, it's a "scaled down" version of a
full blown "enterprise" DBMS, with built-in limitation for database size,
concurrent workloads, and so on...
as regard as your last question,
>IS msde a
> product which can run simitaniosly in our environment?
I should say yes, but your environment is not public
, and of course it
all depends on your requirements..
regards
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Rudolph,
And to add to what Andrea said, we've used it in that sort of environment
many, many times without issue.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:35pbuqF4pmdlaU1@.individual.net...
> hi Rudolph,
> rudolph wrote:
> I'm not Greg (hi Greg :D) but, again, I do not understand the "stability"
> problems...
> MSDE is one of the editions of SQL Server, limited some way, but shares
> the
> same core functionnalities and features...
> MSDE is not a client product as Access, it's a "scaled down" version of a
> full blown "enterprise" DBMS, with built-in limitation for database size,
> concurrent workloads, and so on...
> as regard as your last question,
> I should say yes, but your environment is not public , and of course it
> all depends on your requirements..
> regards
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
msde in a win 2000 server (terminal) or higher network enwironment. We have a
lot of troubles because this application is going to let our application fail
often , and we get a lot of instability.
Hi rudolph,
Sorry, but dont' see a question here. Why do you think that the MSDE is
causing instability for your app?
Regards,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"rudolph" <rudolph@.discussions.microsoft.com> wrote in message
news:121817FD-B051-4D59-9690-BDD6DA952ADA@.microsoft.com...
> we get from a company installed at our customer sides an application using
> msde in a win 2000 server (terminal) or higher network enwironment. We
> have a
> lot of troubles because this application is going to let our application
> fail
> often , and we get a lot of instability.
|||Hi Greg!
My question is, that we have done out of a pervasive sql based application
an Interface to a small application. This small application is using msde in
a enviroment, we are using, win 2003 or winn200 Server with terminal clients.
The company, who has done the small aplication we are interfacing has
installed at our clients side either msde or MSSQL Server products, depending
on their stability.We have not been asked by them what they are going to
install I thought, that msde is a client product and not a server product. IS
msde a product which can run simitaniosly in our environment?
"Greg Low [MVP]" wrote:
> Hi rudolph,
> Sorry, but dont' see a question here. Why do you think that the MSDE is
> causing instability for your app?
> Regards,
> --
> Greg Low [MVP]
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "rudolph" <rudolph@.discussions.microsoft.com> wrote in message
> news:121817FD-B051-4D59-9690-BDD6DA952ADA@.microsoft.com...
>
>
|||hi Rudolph,
rudolph wrote:
> Hi Greg!
> My question is, that we have done out of a pervasive sql based
> application an Interface to a small application. This small
> application is using msde in a enviroment, we are using, win 2003 or
> winn200 Server with terminal clients. The company, who has done the
> small aplication we are interfacing has installed at our clients side
> either msde or MSSQL Server products, depending on their stability. We
> have not been asked by them what they are going to install I thought,
> that msde is a client product and not a server product. IS msde a
> product which can run simitaniosly in our environment?
I'm not Greg (hi Greg :D) but, again, I do not understand the "stability"
problems...
MSDE is one of the editions of SQL Server, limited some way, but shares the
same core functionnalities and features...
MSDE is not a client product as Access, it's a "scaled down" version of a
full blown "enterprise" DBMS, with built-in limitation for database size,
concurrent workloads, and so on...
as regard as your last question,
>IS msde a
> product which can run simitaniosly in our environment?
I should say yes, but your environment is not public
, and of course itall depends on your requirements..
regards
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Rudolph,
And to add to what Andrea said, we've used it in that sort of environment
many, many times without issue.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:35pbuqF4pmdlaU1@.individual.net...
> hi Rudolph,
> rudolph wrote:
> I'm not Greg (hi Greg :D) but, again, I do not understand the "stability"
> problems...
> MSDE is one of the editions of SQL Server, limited some way, but shares
> the
> same core functionnalities and features...
> MSDE is not a client product as Access, it's a "scaled down" version of a
> full blown "enterprise" DBMS, with built-in limitation for database size,
> concurrent workloads, and so on...
> as regard as your last question,
> I should say yes, but your environment is not public
, and of course it> all depends on your requirements..
> regards
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
Friday, March 9, 2012
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
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
Wednesday, March 7, 2012
MSDE Installation Error on Win9x
I am installing MSDE on win 9x machines and am having a problem. The installation aborts and the installshield unattend.iss script rolls back the installation. It seems the failure is in the cnfgsvr.exe program (based on the sqlstp.log file).
the command line that I use is:
msdex86 -s -a -f1 "c:\unattend.iss"
The log files sqlstp.log and cnfgsvr.out are included below.
I have seen some postings similar to this, but never a resolution. Any help would be appreciated...
Here are the log files...
Sqlstp.log file
~~~~~~~~~~~~~~~~~~~sqlstp.log~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~
13:53:56 Begin Setup
13:53:56 7.00.623
13:53:56 Mode=Silent
13:53:56 ModeType=NORMAL
13:53:57 ValueFTS returned: 0
13:53:57 ValuePID returned: 0
13:53:57 ValueLic returned: 0
13:53:57 GetDefinitionEx returned: 0, Extended: 0x0
13:53:57 System: Windows 95
13:53:57 SQL Server ProductType: MSDE [0x4]
13:53:57 Begin Action: SetupInitialize
13:53:57 End Action SetupInitialize
13:53:57 Fixed install: 0
13:53:57 Begin Action: CheckRequirements
13:53:57 Platform ID: 0xf0000
13:53:57 Version: 4.0.67109975
13:53:57 DCOM95 has been detected.
13:53:57 File Version - C:\WINDOWS\SYSTEM\shdocvw.dll: 5.50.4134.600
13:53:57 ComputerName: JMCGUIRE1
13:53:57 User Name: cbauerle
13:53:57 Domain: JMCGUIRE1
13:53:57 OS Language: 0x409
13:53:57 End Action CheckRequirements
13:53:57 Begin Action: Detection
13:53:57 End Action Detection
13:53:57 Begin Action: ODBCLocked
13:53:57 C:\WINDOWS\TEMP\_ISTMP0.DIR\odbcinst.exe -IsLocked -Silent 1 -SourceDir C:\WINDOWS\TEMP\PFT234~1\X86\ODBC -LogFile C:\WINDOWS\sqlodbci.log
13:53:58 Process Exit Code: (-1)
13:53:58 End Action ODBCLocked
13:53:58 This combination of Package and Operating System allows a full product install.
13:53:58 Reading Software\Microsoft\Windows\CurrentVersion\CommonFi lesDir ...
13:53:58 CommonFilesDir=C:\Program Files\Common Files
13:53:58 Windows Directory=C:\WINDOWS\
13:53:58 Begin Action: ShowDialogs
13:53:58 Begin Action: DialogShowSdWelcome
13:53:58 End Action DialogShowSdWelcome
13:53:58 Begin Action: DialogShowSdLicense
13:53:58 End Action DialogShowSdLicense
13:53:58 Begin Action: DialogShowSdRegisterUserEx
13:53:58 End Action DialogShowSdRegisterUserEx
13:53:58 Begin Action: DialogShowSdSetupType
13:53:58 [SetupTypeSQL]
13:53:58 Result=302
13:53:58 szDir=C:\MSSQL7
13:53:58 final szDir=C:\MSSQL7
13:53:58 szDataDir=C:\MSSQL7
13:53:58 final szDataDir=C:\MSSQL7
13:53:58 End Action DialogShowSdSetupType
13:53:58 Begin Action: DialogShowSdComponentMult
13:53:58 End Action DialogShowSdComponentMult
13:53:58 Begin Action: DlgCpSortUnicode
13:53:58 Result=1
13:53:58 [DlgCpSortUnicode]
13:53:58 SortId=52
13:53:58 LCID=1033
13:53:58 CompStyle=196609
13:53:58 End Action DlgCpSortUnicode
13:53:58 Begin Action: DlgNetwork
13:53:58 Result=1
13:53:58 [DlgServerNetwork]
13:53:58 NetworkLibs=4095
13:53:58 TCPPort=1433
13:53:58 TCPPrxy=
13:53:58 NMPPipeName=\\.\pipe\sql\query
13:53:58 End Action DlgNetwork
13:53:58 Begin Action: DlgServices
13:53:58 [DlgServices]
13:53:58 Result=1
13:53:58 Local-Domain=3855
13:53:58 AutoStart=61455
13:53:58 End Action DlgServices
13:53:58 Begin Action: DialogShowSdStartCopy
13:53:58 End Action DialogShowSdStartCopy
13:53:58 Begin Action: DlgCPLLicense
13:53:58 End Action DlgCPLLicense
13:53:58 End Action ShowDialogs
13:53:58 Begin Action ProcessBeforeDataMove:
13:53:58 DeinstallStart returned (C:\MSSQL7): 0
13:53:58 End Action ProcessBeforeDataMove:
13:53:58 Begin Action ProcessComponentSelection:
13:53:58 End Action ProcessComponentSelection
13:53:58 Begin Action LogSelectedComponents:
13:53:58 SQLProg
13:53:58 SQLProg\SQLServr
13:53:58 SQLProg\SQLServr\Help
13:53:58 SQLProg\SQLServr\SCMDev
13:53:58 SQLProg\SQLServr\SCMDev\SCMh
13:53:58 SQLProg\SQLServr\SCMDev\SCMX86Lb
13:53:58 SQLProg\SQLServr\SCMDev\SCMALb
13:53:59 SQLProg\ReplSupp
13:53:59 SQLProg\ReplSupp\ReplSys
13:53:59 SQLProg\ReplSupp\ReplSys1
13:53:59 SQLProg\ReplSupp\RepComm
13:53:59 SQLProg\Dat
13:53:59 SQLProg\BaseSys
13:53:59 SQLProg\BaseBinn
13:53:59 Core
13:53:59 CoreSys
13:53:59 ODBC
13:53:59 OLEDB
13:53:59 CoreMisc
13:53:59 Jet
13:53:59 NetCore
13:53:59 CoreInst
13:53:59 Core1033
13:53:59 CoreIntl
13:53:59 CrMi1033
13:53:59 CrMiIntl
13:53:59 SysCore
13:53:59 VOLEDB
13:53:59 VODBC
13:53:59 CrRepCom
13:53:59 {E07FDDBE-5A21-11d2-9DAD-00C04F79D434}
13:53:59 {E07FDDC0-5A21-11d2-9DAD-00C04F79D434}
13:53:59 End Action LogSelectedComponents
13:54:00 SQL program folder: C:\MSSQL7
13:54:00 SQL data folder: C:\MSSQL7
13:54:00 Windows system folder: C:\WINDOWS\SYSTEM\
13:54:00 Prog req: 15751, Data req: 20447, Sys req: 4433
13:54:00 Prog avail: 792068, Data avail: 792068, Sys avail: 792068
13:54:00 Prog req vs. avail, 40631, 792068
13:54:00 Data req vs. avail, 20447, 792068
13:54:00 Sys req vs. avail, 24880, 792068
13:54:00 DisplaySystemPreReq
13:54:00 Begin Action MoveFileData:
13:54:32 End Action MoveFileData
13:54:32 Begin Action ProcessAfterDataMove:
13:54:32 DeinstallSetReference (C:\MSSQL7\sqlservr.exe) returned: 0
13:54:32 End Action ProcessAfterDataMove
13:54:32 Begin Action InstallPkgs:
13:54:32 Setup is installing Microsoft Data Access Components (MDAC) ...
13:54:32 C:\WINDOWS\TEMP\pft2344~TMP\x86\Other\mdac_typ.exe /q:a /c:"setup.exe /qtn"
13:55:44 Process Exit Code: (3010)
13:55:44 Setup is installing Microsoft Distributed Transaction Coordinator (MSDTC) ...
13:55:44 C:\WINDOWS\TEMP\pft2344~TMP\x86\Other\dtcsetup.exe /q:a /r:n
13:56:04 Process Exit Code: (0)
13:56:04 End Action InstallPkgs
13:56:04 Begin Action BuildServer:
13:56:04 SetNewPath returned: 3010
13:56:04 Path successfully updated.
13:56:04 C:\MSSQL7\binn\cnfgsvr.exe -Silent 1 -NoSampleDB 1 -SQLPath "C:\MSSQL7\" -SQLDataPath "C:\MSSQL7\" -SortID 52 -LCIDCompStyle "1033-196609" -HWND 732 -User sa -Pwd
13:58:14 Process Exit Code: (-1)
13:58:14 Setup failed to configure the server. Refer to the server error logs and cnfgsvr.out for more information.
13:58:14 Action CleanUpInstall:
13:58:14 C:\WINDOWS\TEMP\_ISTMP0.DIR\scm.exe -Silent 1 -Action 4 -Service SQLServerAgent
13:58:14 Process Exit Code: (0)
13:58:14 Installation Failed.
~~~~~~~~~~~~~~~end sqlstp.log~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cnfgsvr.out file
~~~~~~~~~~~~~~~~~~~cnfgsvr.out~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~
Starting Service ...
Connecting to Server ...
driver={sql server};server=JMCGUIRE1;UID=sa;PWD=;database=mast er
[Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access denied.
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen (Connect()).
driver={sql server};server=JMCGUIRE1;UID=sa;PWD=;database=mast er
[Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access denied.
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen (Connect()).
driver={sql server};server=.;UID=sa;PWD=;database=master
[Microsoft][ODBC SQL Server Driver][Named Pipes]SQL Server does not exist or access denied.
[Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionOpen (Connect()).
SQL Server configuration failed.
~~~~~~~~~~~~~~~end cnfgsvr.out~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~I am able to easily reproduce the error with the following steps:
1. Install WIN95b
2. Install IE5.5
3. Install MDAC 2.6SP1
4. Install MSDE
MSDE does not install on a win95 machine that has MDAC installed.
If I install MSDE, then MDAC it is OK.
Any thoughts??
the command line that I use is:
msdex86 -s -a -f1 "c:\unattend.iss"
The log files sqlstp.log and cnfgsvr.out are included below.
I have seen some postings similar to this, but never a resolution. Any help would be appreciated...
Here are the log files...
Sqlstp.log file
~~~~~~~~~~~~~~~~~~~sqlstp.log~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~
13:53:56 Begin Setup
13:53:56 7.00.623
13:53:56 Mode=Silent
13:53:56 ModeType=NORMAL
13:53:57 ValueFTS returned: 0
13:53:57 ValuePID returned: 0
13:53:57 ValueLic returned: 0
13:53:57 GetDefinitionEx returned: 0, Extended: 0x0
13:53:57 System: Windows 95
13:53:57 SQL Server ProductType: MSDE [0x4]
13:53:57 Begin Action: SetupInitialize
13:53:57 End Action SetupInitialize
13:53:57 Fixed install: 0
13:53:57 Begin Action: CheckRequirements
13:53:57 Platform ID: 0xf0000
13:53:57 Version: 4.0.67109975
13:53:57 DCOM95 has been detected.
13:53:57 File Version - C:\WINDOWS\SYSTEM\shdocvw.dll: 5.50.4134.600
13:53:57 ComputerName: JMCGUIRE1
13:53:57 User Name: cbauerle
13:53:57 Domain: JMCGUIRE1
13:53:57 OS Language: 0x409
13:53:57 End Action CheckRequirements
13:53:57 Begin Action: Detection
13:53:57 End Action Detection
13:53:57 Begin Action: ODBCLocked
13:53:57 C:\WINDOWS\TEMP\_ISTMP0.DIR\odbcinst.exe -IsLocked -Silent 1 -SourceDir C:\WINDOWS\TEMP\PFT234~1\X86\ODBC -LogFile C:\WINDOWS\sqlodbci.log
13:53:58 Process Exit Code: (-1)
13:53:58 End Action ODBCLocked
13:53:58 This combination of Package and Operating System allows a full product install.
13:53:58 Reading Software\Microsoft\Windows\CurrentVersion\CommonFi lesDir ...
13:53:58 CommonFilesDir=C:\Program Files\Common Files
13:53:58 Windows Directory=C:\WINDOWS\
13:53:58 Begin Action: ShowDialogs
13:53:58 Begin Action: DialogShowSdWelcome
13:53:58 End Action DialogShowSdWelcome
13:53:58 Begin Action: DialogShowSdLicense
13:53:58 End Action DialogShowSdLicense
13:53:58 Begin Action: DialogShowSdRegisterUserEx
13:53:58 End Action DialogShowSdRegisterUserEx
13:53:58 Begin Action: DialogShowSdSetupType
13:53:58 [SetupTypeSQL]
13:53:58 Result=302
13:53:58 szDir=C:\MSSQL7
13:53:58 final szDir=C:\MSSQL7
13:53:58 szDataDir=C:\MSSQL7
13:53:58 final szDataDir=C:\MSSQL7
13:53:58 End Action DialogShowSdSetupType
13:53:58 Begin Action: DialogShowSdComponentMult
13:53:58 End Action DialogShowSdComponentMult
13:53:58 Begin Action: DlgCpSortUnicode
13:53:58 Result=1
13:53:58 [DlgCpSortUnicode]
13:53:58 SortId=52
13:53:58 LCID=1033
13:53:58 CompStyle=196609
13:53:58 End Action DlgCpSortUnicode
13:53:58 Begin Action: DlgNetwork
13:53:58 Result=1
13:53:58 [DlgServerNetwork]
13:53:58 NetworkLibs=4095
13:53:58 TCPPort=1433
13:53:58 TCPPrxy=
13:53:58 NMPPipeName=\\.\pipe\sql\query
13:53:58 End Action DlgNetwork
13:53:58 Begin Action: DlgServices
13:53:58 [DlgServices]
13:53:58 Result=1
13:53:58 Local-Domain=3855
13:53:58 AutoStart=61455
13:53:58 End Action DlgServices
13:53:58 Begin Action: DialogShowSdStartCopy
13:53:58 End Action DialogShowSdStartCopy
13:53:58 Begin Action: DlgCPLLicense
13:53:58 End Action DlgCPLLicense
13:53:58 End Action ShowDialogs
13:53:58 Begin Action ProcessBeforeDataMove:
13:53:58 DeinstallStart returned (C:\MSSQL7): 0
13:53:58 End Action ProcessBeforeDataMove:
13:53:58 Begin Action ProcessComponentSelection:
13:53:58 End Action ProcessComponentSelection
13:53:58 Begin Action LogSelectedComponents:
13:53:58 SQLProg
13:53:58 SQLProg\SQLServr
13:53:58 SQLProg\SQLServr\Help
13:53:58 SQLProg\SQLServr\SCMDev
13:53:58 SQLProg\SQLServr\SCMDev\SCMh
13:53:58 SQLProg\SQLServr\SCMDev\SCMX86Lb
13:53:58 SQLProg\SQLServr\SCMDev\SCMALb
13:53:59 SQLProg\ReplSupp
13:53:59 SQLProg\ReplSupp\ReplSys
13:53:59 SQLProg\ReplSupp\ReplSys1
13:53:59 SQLProg\ReplSupp\RepComm
13:53:59 SQLProg\Dat
13:53:59 SQLProg\BaseSys
13:53:59 SQLProg\BaseBinn
13:53:59 Core
13:53:59 CoreSys
13:53:59 ODBC
13:53:59 OLEDB
13:53:59 CoreMisc
13:53:59 Jet
13:53:59 NetCore
13:53:59 CoreInst
13:53:59 Core1033
13:53:59 CoreIntl
13:53:59 CrMi1033
13:53:59 CrMiIntl
13:53:59 SysCore
13:53:59 VOLEDB
13:53:59 VODBC
13:53:59 CrRepCom
13:53:59 {E07FDDBE-5A21-11d2-9DAD-00C04F79D434}
13:53:59 {E07FDDC0-5A21-11d2-9DAD-00C04F79D434}
13:53:59 End Action LogSelectedComponents
13:54:00 SQL program folder: C:\MSSQL7
13:54:00 SQL data folder: C:\MSSQL7
13:54:00 Windows system folder: C:\WINDOWS\SYSTEM\
13:54:00 Prog req: 15751, Data req: 20447, Sys req: 4433
13:54:00 Prog avail: 792068, Data avail: 792068, Sys avail: 792068
13:54:00 Prog req vs. avail, 40631, 792068
13:54:00 Data req vs. avail, 20447, 792068
13:54:00 Sys req vs. avail, 24880, 792068
13:54:00 DisplaySystemPreReq
13:54:00 Begin Action MoveFileData:
13:54:32 End Action MoveFileData
13:54:32 Begin Action ProcessAfterDataMove:
13:54:32 DeinstallSetReference (C:\MSSQL7\sqlservr.exe) returned: 0
13:54:32 End Action ProcessAfterDataMove
13:54:32 Begin Action InstallPkgs:
13:54:32 Setup is installing Microsoft Data Access Components (MDAC) ...
13:54:32 C:\WINDOWS\TEMP\pft2344~TMP\x86\Other\mdac_typ.exe /q:a /c:"setup.exe /qtn"
13:55:44 Process Exit Code: (3010)
13:55:44 Setup is installing Microsoft Distributed Transaction Coordinator (MSDTC) ...
13:55:44 C:\WINDOWS\TEMP\pft2344~TMP\x86\Other\dtcsetup.exe /q:a /r:n
13:56:04 Process Exit Code: (0)
13:56:04 End Action InstallPkgs
13:56:04 Begin Action BuildServer:
13:56:04 SetNewPath returned: 3010
13:56:04 Path successfully updated.
13:56:04 C:\MSSQL7\binn\cnfgsvr.exe -Silent 1 -NoSampleDB 1 -SQLPath "C:\MSSQL7\" -SQLDataPath "C:\MSSQL7\" -SortID 52 -LCIDCompStyle "1033-196609" -HWND 732 -User sa -Pwd
13:58:14 Process Exit Code: (-1)
13:58:14 Setup failed to configure the server. Refer to the server error logs and cnfgsvr.out for more information.
13:58:14 Action CleanUpInstall:
13:58:14 C:\WINDOWS\TEMP\_ISTMP0.DIR\scm.exe -Silent 1 -Action 4 -Service SQLServerAgent
13:58:14 Process Exit Code: (0)
13:58:14 Installation Failed.
~~~~~~~~~~~~~~~end sqlstp.log~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cnfgsvr.out file
~~~~~~~~~~~~~~~~~~~cnfgsvr.out~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~
Starting Service ...
Connecting to Server ...
driver={sql server};server=JMCGUIRE1;UID=sa;PWD=;database=mast er
[Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access denied.
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen (Connect()).
driver={sql server};server=JMCGUIRE1;UID=sa;PWD=;database=mast er
[Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access denied.
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen (Connect()).
driver={sql server};server=.;UID=sa;PWD=;database=master
[Microsoft][ODBC SQL Server Driver][Named Pipes]SQL Server does not exist or access denied.
[Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionOpen (Connect()).
SQL Server configuration failed.
~~~~~~~~~~~~~~~end cnfgsvr.out~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~I am able to easily reproduce the error with the following steps:
1. Install WIN95b
2. Install IE5.5
3. Install MDAC 2.6SP1
4. Install MSDE
MSDE does not install on a win95 machine that has MDAC installed.
If I install MSDE, then MDAC it is OK.
Any thoughts??
Saturday, February 25, 2012
MSDE Install For 98/SE/ME
I understand for Win 2k and XP installs that a simple re-boot after MSDE
installation will start the MSDE service, but for 98/SE/ME, what is
required?
Does the user have to go to Start Menu and start the service? I do not want
to
complicate the installation routine by having to determine the OS and then
adding an automatic launch if user is on 98 for example. I just want to
know
what to tell the user to do in order to start MSDE.
Paul
P.S. My Setup.bat file is:
setup.exe /settings setup.ini /L*V "c:\EquLog.txt"
and my setup.ini file is:
[Options]
INSTANCENAME=COMPNAME01
SECURITYMODE=SQL
SAPWD="MYPASSWORD"
DISABLENETWORKPROTOCOLS=0
This method is working fine on XP boxes.
hi Paul,
"Paul McTeigue" <paul_mcteigue@.msn.com> ha scritto nel messaggio
news:eWQpb54bEHA.904@.TK2MSFTNGP09.phx.gbl...
> I understand for Win 2k and XP installs that a simple re-boot after MSDE
> installation will start the MSDE service, but for 98/SE/ME, what is
> required?
> Does the user have to go to Start Menu and start the service? I do not
want
> to
> complicate the installation routine by having to determine the OS and then
> adding an automatic launch if user is on 98 for example. I just want to
> know
> what to tell the user to do in order to start MSDE.
Win9x platforms do not support Windows NT service control APIs so SQL
Server/MSDE can not be run as service.. it is run as a standard application
instead, so there's no way to "start the relative services at boostratp"...
you can however select, on Service Manager, to "Auto Start" at startup, to
start automatically whenever the computer boots, which will actually put an
entry in the "automatic execution" folder.
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
|||So - after installation on 98/SE/ME - there will be a Start Menu entry
titled "Service Manager"
whereby if you click it you will have the option of auto-starting ?
I am just looking for a clear user instruction for people installing on
those platforms.
Thanks,
Paul
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2m8q1pFk9u42U1@.uni-berlin.de...[vbcol=seagreen]
> hi Paul,
> "Paul McTeigue" <paul_mcteigue@.msn.com> ha scritto nel messaggio
> news:eWQpb54bEHA.904@.TK2MSFTNGP09.phx.gbl...
> want
then
> Win9x platforms do not support Windows NT service control APIs so SQL
> Server/MSDE can not be run as service.. it is run as a standard
application
> instead, so there's no way to "start the relative services at
boostratp"...
> you can however select, on Service Manager, to "Auto Start" at startup, to
> start automatically whenever the computer boots, which will actually put
an
> entry in the "automatic execution" folder.
> --
> 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
>
|||hi Paul,
"Paul McTeigue" <paul_mcteigue@.msn.com> ha scritto nel messaggio
news:Or$M3dCcEHA.2468@.TK2MSFTNGP09.phx.gbl...
> So - after installation on 98/SE/ME - there will be a Start Menu entry
> titled "Service Manager"
> whereby if you click it you will have the option of auto-starting ?
yes, but only for the MSDE instance, not for the SQL Server Agent :-(
> I am just looking for a clear user instruction for people installing on
> those platforms.
"... please check the 'Autostart' option ..." =;-D
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
installation will start the MSDE service, but for 98/SE/ME, what is
required?
Does the user have to go to Start Menu and start the service? I do not want
to
complicate the installation routine by having to determine the OS and then
adding an automatic launch if user is on 98 for example. I just want to
know
what to tell the user to do in order to start MSDE.
Paul
P.S. My Setup.bat file is:
setup.exe /settings setup.ini /L*V "c:\EquLog.txt"
and my setup.ini file is:
[Options]
INSTANCENAME=COMPNAME01
SECURITYMODE=SQL
SAPWD="MYPASSWORD"
DISABLENETWORKPROTOCOLS=0
This method is working fine on XP boxes.
hi Paul,
"Paul McTeigue" <paul_mcteigue@.msn.com> ha scritto nel messaggio
news:eWQpb54bEHA.904@.TK2MSFTNGP09.phx.gbl...
> I understand for Win 2k and XP installs that a simple re-boot after MSDE
> installation will start the MSDE service, but for 98/SE/ME, what is
> required?
> Does the user have to go to Start Menu and start the service? I do not
want
> to
> complicate the installation routine by having to determine the OS and then
> adding an automatic launch if user is on 98 for example. I just want to
> know
> what to tell the user to do in order to start MSDE.
Win9x platforms do not support Windows NT service control APIs so SQL
Server/MSDE can not be run as service.. it is run as a standard application
instead, so there's no way to "start the relative services at boostratp"...
you can however select, on Service Manager, to "Auto Start" at startup, to
start automatically whenever the computer boots, which will actually put an
entry in the "automatic execution" folder.
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
|||So - after installation on 98/SE/ME - there will be a Start Menu entry
titled "Service Manager"
whereby if you click it you will have the option of auto-starting ?
I am just looking for a clear user instruction for people installing on
those platforms.
Thanks,
Paul
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2m8q1pFk9u42U1@.uni-berlin.de...[vbcol=seagreen]
> hi Paul,
> "Paul McTeigue" <paul_mcteigue@.msn.com> ha scritto nel messaggio
> news:eWQpb54bEHA.904@.TK2MSFTNGP09.phx.gbl...
> want
then
> Win9x platforms do not support Windows NT service control APIs so SQL
> Server/MSDE can not be run as service.. it is run as a standard
application
> instead, so there's no way to "start the relative services at
boostratp"...
> you can however select, on Service Manager, to "Auto Start" at startup, to
> start automatically whenever the computer boots, which will actually put
an
> entry in the "automatic execution" folder.
> --
> 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
>
|||hi Paul,
"Paul McTeigue" <paul_mcteigue@.msn.com> ha scritto nel messaggio
news:Or$M3dCcEHA.2468@.TK2MSFTNGP09.phx.gbl...
> So - after installation on 98/SE/ME - there will be a Start Menu entry
> titled "Service Manager"
> whereby if you click it you will have the option of auto-starting ?
yes, but only for the MSDE instance, not for the SQL Server Agent :-(
> I am just looking for a clear user instruction for people installing on
> those platforms.
"... please check the 'Autostart' option ..." =;-D
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
Monday, February 20, 2012
MSDE from Hoster installed
Hello
my DEd win 2003 server, uses MSDE
all is ok, the server run, and can create from script Db
but if i want login or create connection MSDE say wrong pass
i never change the pass or other
i have the server complet reinstalled from hoster image
what i doing wrong ?
hi,
MS News wrote:
> Hello
> my DEd win 2003 server, uses MSDE
> all is ok, the server run, and can create from script Db
> but if i want login or create connection MSDE say wrong pass
> i never change the pass or other
> i have the server complet reinstalled from hoster image
> what i doing wrong ?
assuming you are trying to connect using the standard SQL Server
authentication with the "sa" login and you can't remember it's pasword, you
can login using integrated security (the Windows authentication) using a
local admin member and set the "sa" password to whatever you want via the
system stored procedure sp_password,
http://msdn.microsoft.com/library/de...a-pz_5x44.asp,
in the form
EXEC sp_password @.new = 'whatever', @.loginame = 'sa'
as all local admins members are automatically members of the
BUILTIN\Administrators login group in MSDE too, with sysadmins privileges...
connect via oSql.exe providing the -E parameter to specify integrated
security..
c:\..\>osql.exe -E -S(local)\InstanceName
1>EXEC sp_password @.new = 'whatever', @.loginame = 'sa'
2>GO
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
|||hey thats realy works !
thanks!
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> schrieb im Newsbeitrag
news:3s11vbFlebp5U1@.individual.net...
> hi,
> MS News wrote:
> assuming you are trying to connect using the standard SQL Server
> authentication with the "sa" login and you can't remember it's pasword,
> you can login using integrated security (the Windows authentication) using
> a local admin member and set the "sa" password to whatever you want via
> the system stored procedure sp_password,
> http://msdn.microsoft.com/library/de...a-pz_5x44.asp,
> in the form
> EXEC sp_password @.new = 'whatever', @.loginame = 'sa'
> as all local admins members are automatically members of the
> BUILTIN\Administrators login group in MSDE too, with sysadmins
> privileges...
> connect via oSql.exe providing the -E parameter to specify integrated
> security..
> c:\..\>osql.exe -E -S(local)\InstanceName
> 1>EXEC sp_password @.new = 'whatever', @.loginame = 'sa'
> 2>GO
> --
> 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
>
my DEd win 2003 server, uses MSDE
all is ok, the server run, and can create from script Db
but if i want login or create connection MSDE say wrong pass
i never change the pass or other
i have the server complet reinstalled from hoster image
what i doing wrong ?
hi,
MS News wrote:
> Hello
> my DEd win 2003 server, uses MSDE
> all is ok, the server run, and can create from script Db
> but if i want login or create connection MSDE say wrong pass
> i never change the pass or other
> i have the server complet reinstalled from hoster image
> what i doing wrong ?
assuming you are trying to connect using the standard SQL Server
authentication with the "sa" login and you can't remember it's pasword, you
can login using integrated security (the Windows authentication) using a
local admin member and set the "sa" password to whatever you want via the
system stored procedure sp_password,
http://msdn.microsoft.com/library/de...a-pz_5x44.asp,
in the form
EXEC sp_password @.new = 'whatever', @.loginame = 'sa'
as all local admins members are automatically members of the
BUILTIN\Administrators login group in MSDE too, with sysadmins privileges...
connect via oSql.exe providing the -E parameter to specify integrated
security..
c:\..\>osql.exe -E -S(local)\InstanceName
1>EXEC sp_password @.new = 'whatever', @.loginame = 'sa'
2>GO
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
|||hey thats realy works !
thanks!
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> schrieb im Newsbeitrag
news:3s11vbFlebp5U1@.individual.net...
> hi,
> MS News wrote:
> assuming you are trying to connect using the standard SQL Server
> authentication with the "sa" login and you can't remember it's pasword,
> you can login using integrated security (the Windows authentication) using
> a local admin member and set the "sa" password to whatever you want via
> the system stored procedure sp_password,
> http://msdn.microsoft.com/library/de...a-pz_5x44.asp,
> in the form
> EXEC sp_password @.new = 'whatever', @.loginame = 'sa'
> as all local admins members are automatically members of the
> BUILTIN\Administrators login group in MSDE too, with sysadmins
> privileges...
> connect via oSql.exe providing the -E parameter to specify integrated
> security..
> c:\..\>osql.exe -E -S(local)\InstanceName
> 1>EXEC sp_password @.new = 'whatever', @.loginame = 'sa'
> 2>GO
> --
> 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 for Win CE
Hi
I am looking for MSDE for Win CE.
Any clue of how to get that version
Thank you,
Shmuel Shulman
SBS Technologies LTD
hi,
S Shulman wrote:
> Hi
> I am looking for MSDE for Win CE.
> Any clue of how to get that version
> Thank you,
> Shmuel Shulman
> SBS Technologies LTD
there's no MSDE for Win CE, but SQL Server CE...
http://msdn.microsoft.com/library/de..._server_ce.asp
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
I am looking for MSDE for Win CE.
Any clue of how to get that version
Thank you,
Shmuel Shulman
SBS Technologies LTD
hi,
S Shulman wrote:
> Hi
> I am looking for MSDE for Win CE.
> Any clue of how to get that version
> Thank you,
> Shmuel Shulman
> SBS Technologies LTD
there's no MSDE for Win CE, but SQL Server CE...
http://msdn.microsoft.com/library/de..._server_ce.asp
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
MSDE Error on attempting to create new Access 2000 project
Hi folks
I've just installed MSDE on my Win 2k machine and have attempted to
create a new Access 2000 project. When I do (and using a number of
different Login ID/Password combinations), I get this:
Connection failed:
SQLState: '01000'
SQL Server Error: 123
[Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionOpen
(CreateFile()).
Connection failed:
SQLState: '08001'
SQL Server Error: 123
[Microsoft][ODBC SQL Server Driver]Client unable to establish
connection
can anyone tell me what this means and what I should do. Any help much
appreciated.
thanks
Laurence
Laurence,
See: http://support.microsoft.com/default...b;en-us;233312
It looks like you do not have named pipes installed with your MSDE, but you
are using it from your client.
Russell Fields
"Laurence" <laurencetruman@.yahoo.com> wrote in message
news:c8e229b3.0406090533.5ecefd75@.posting.google.c om...
> Hi folks
> I've just installed MSDE on my Win 2k machine and have attempted to
> create a new Access 2000 project. When I do (and using a number of
> different Login ID/Password combinations), I get this:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 123
> [Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionOpen
> (CreateFile()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 123
> [Microsoft][ODBC SQL Server Driver]Client unable to establish
> connection
> can anyone tell me what this means and what I should do. Any help much
> appreciated.
> thanks
> Laurence
|||Laurence,
Actually, you might find this more helpful (since my first post was to an
old version of MSDE)
ACC2002: "Configuring SQL Server 2000 Desktop Engine" White Paper Available
in Download Center
http://support.microsoft.com/default...b;en-us;301413
Russell Fields
"Laurence" <laurencetruman@.yahoo.com> wrote in message
news:c8e229b3.0406090533.5ecefd75@.posting.google.c om...
> Hi folks
> I've just installed MSDE on my Win 2k machine and have attempted to
> create a new Access 2000 project. When I do (and using a number of
> different Login ID/Password combinations), I get this:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 123
> [Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionOpen
> (CreateFile()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 123
> [Microsoft][ODBC SQL Server Driver]Client unable to establish
> connection
> can anyone tell me what this means and what I should do. Any help much
> appreciated.
> thanks
> Laurence
I've just installed MSDE on my Win 2k machine and have attempted to
create a new Access 2000 project. When I do (and using a number of
different Login ID/Password combinations), I get this:
Connection failed:
SQLState: '01000'
SQL Server Error: 123
[Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionOpen
(CreateFile()).
Connection failed:
SQLState: '08001'
SQL Server Error: 123
[Microsoft][ODBC SQL Server Driver]Client unable to establish
connection
can anyone tell me what this means and what I should do. Any help much
appreciated.
thanks
Laurence
Laurence,
See: http://support.microsoft.com/default...b;en-us;233312
It looks like you do not have named pipes installed with your MSDE, but you
are using it from your client.
Russell Fields
"Laurence" <laurencetruman@.yahoo.com> wrote in message
news:c8e229b3.0406090533.5ecefd75@.posting.google.c om...
> Hi folks
> I've just installed MSDE on my Win 2k machine and have attempted to
> create a new Access 2000 project. When I do (and using a number of
> different Login ID/Password combinations), I get this:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 123
> [Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionOpen
> (CreateFile()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 123
> [Microsoft][ODBC SQL Server Driver]Client unable to establish
> connection
> can anyone tell me what this means and what I should do. Any help much
> appreciated.
> thanks
> Laurence
|||Laurence,
Actually, you might find this more helpful (since my first post was to an
old version of MSDE)
ACC2002: "Configuring SQL Server 2000 Desktop Engine" White Paper Available
in Download Center
http://support.microsoft.com/default...b;en-us;301413
Russell Fields
"Laurence" <laurencetruman@.yahoo.com> wrote in message
news:c8e229b3.0406090533.5ecefd75@.posting.google.c om...
> Hi folks
> I've just installed MSDE on my Win 2k machine and have attempted to
> create a new Access 2000 project. When I do (and using a number of
> different Login ID/Password combinations), I get this:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 123
> [Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionOpen
> (CreateFile()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 123
> [Microsoft][ODBC SQL Server Driver]Client unable to establish
> connection
> can anyone tell me what this means and what I should do. Any help much
> appreciated.
> thanks
> Laurence
Subscribe to:
Posts (Atom)