Recently when I try to upgrade my current MSDE2000 (SP3a) to SP4 in Windows
XP – SP2, the system just keep on failing me. He is the scenario:
1. Download the MSDE 2000 SP4 from Microsoft site
2. Extract the MSDE SP4
3. Run the following command via command prompt or batch file:
echo off
echo "Start to Upgrade MSDE SP4 ... "
setup.exe /UPGRADESP SQLRUN INSTANCENAME=JSNG SECURITYMODE=SQL
UPGRADEUSER=sa UPGRADEPWD=Th3B3st /L*v c:\MSDE_Log.log
echo "SP4 Upgrade Process completed!"
4. Once the above batch file was run, the standard configuration
screen (gathering information) will be triggered
5. However, after a while the installation will just stopped (before
the title of the windows has changed to show the instance name)
6. When I checked on the verbose log, I have found out that the failure
of the installation is due to the system has failed to configure the server.
PFB for the last few rows of the verbose log:
=== Logging stopped: 8/22/2006 17:36:49 ===
MSI (c) (90:88) [17:36:49:865]: Note: 1: 1729
MSI (c) (90:88) [17:36:49:865]: Product: Microsoft SQL Server Desktop Engine
-- Configuration failed.
MSI (c) (90:88) [17:36:49:865]: Grabbed execution mutex.
MSI (c) (90:88) [17:36:49:865]: Cleaning up uninstalled install packages, if
any exist
MSI (c) (90:88) [17:36:49:865]: MainEngineThread is returning 1603
=== Verbose logging stopped: 8/22/2006 17:36:49 ===
7. Since this is the configuration error, so I have tried to locate
the cnfgsvr.out and hope to get some hints from there, but unfortunately the
config server file is still not updated yet where it still keep the old info
during the installation of MSDE 2000 SP3a.
8. When I try to locate the error (value = 3), I have found out the
its due to the system has detected blank sa password, but I am sure that the
password that I has provided is correct. PFB for the error recorded in the
verbose log:
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{EFB70B01-B1F3-4960-AB69-4A280084A60C}
Starting custom action UpgDetectBlankSaLogin()
Entering Function MyMsiEvaluateCondition
MsiEvaluateCondition for VersionNT returned TRUE
End Function MyMsiEvaluateCondition
An error was encountered during connection to server: 1
Ending custom action UpgDetectBlankSaLogin().
Action ended 9:37:45:
UpgDetectBlankSaLogin.2D02443E_7002_4C0B_ABC9_EAB2 C064397B. Return value 3.
Action ended 9:37:45: INSTALL. Return value 3.
Property(S): UpgradeCode = {421A321C-2214-4713-B3EB-253F2FBCCE49}
Property(S): SqlDataDir = C:\Program Files\Microsoft SQL Server\
Property(S): SqlProgramDir = C:\Program Files\Microsoft SQL Server\
Property(S): SqlInstanceName = EASYSHIP
Property(S): SqlSecurityMode = SQL
Property(S): SqlSa...
Property(S): SqlDisableNetworkProtocols = 0
Property(S): SqlDoUpgrade = 1
Property(S): ProductName = Microsoft SQL Server Desktop Engine (EASYSHIP)
Property(S): VersionNT = 501
Property(S): ALLUSERS = 1
Property(S): ARPNOMODIFY = 1
Property(S): DefaultUIFont = Tahoma8
9. I have even try to use a different command line and yet it failed.
PFB for the alternative command line that I have used:
setup.exe /UPGRADESP SQLRUN INSTANCENAME=JSNG SECURITYMODE=SQL SAPWD=Th3B3st
/L*v
10. I have tried the same in a Windows 2000 Std Server - SP4, and yet it
failed.
During my testing, I have closed down all SQL related activities, including
the followings:
1. Microsoft OutLook
2. SQL Agent Service
3. Easyship Scheduler
But I still experience the above.
I have tried to re-run the same in one of my fresh Windows XP (in virtual
machine), and everything just works fine. Could it be any unclean registry
entry that fail this? Or could it be any software component that is
incompatible with this? Does it have anything to do with the version of MS
Installer being installed in my machine? FYI, I have installed the latest MS
Installer 3.1 before when I tried to install SQL Express, however after I
have remove it, the problem still persist.
Do you have any idea on the above? PFA for the versbose log.
HI,
I am also facing the same issue in my domain.
Unable to find much details.
Is your issue resolved?If yes kindly help me out.
Thanks in advance,
Harish K
EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com
|||HI,
I am also facing the same issue in my domain.
Unable to find much details.
Is your issue resolved?If yes kindly help me out.
Thanks in advance,
Harish K
EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com
sql
Showing posts with label sp3a. Show all posts
Showing posts with label sp3a. Show all posts
Friday, March 30, 2012
Wednesday, March 28, 2012
MSDE SP3a Upgrade problem
I just upgraded my desktop engine MSDE 1.0 to MSDE 2000 SP3a. Everything seemed to go well, MSSQLSERVER AND SQLSERVER Agent Services are running, problem is, I can no longer see the particular instance on the network from Enterprise Manager.
The installation instructions specified that if the Instance was to accept connections from applications on other computers not to specify the DISABLENETWORKPROTOCOLS parameter, so I didn't.
I'm a little green with this, can anyone suggest a place to start troubleshooting?Can you pull it up in Query Analyzer. Just type in (local) or whatever your instance name is for the connection server and see if it connects.
The installation instructions specified that if the Instance was to accept connections from applications on other computers not to specify the DISABLENETWORKPROTOCOLS parameter, so I didn't.
I'm a little green with this, can anyone suggest a place to start troubleshooting?Can you pull it up in Query Analyzer. Just type in (local) or whatever your instance name is for the connection server and see if it connects.
MSDE SP3a on a Server with SQL Server 2000 SP4
A few questions here.
1. I have noticed a problem when MSDE SP3a is installed on a server with SQL
Server SP4. The Registry key value SQLPath at
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\80\Tools\ClientSetup loses the last character and that makes the path
to osql, invalid when executing a post replication script. It also breaks
accessing Query Analyzer and SQL Profiler from Enterprise manager among other
problems I'm sure. Is this a known problem? I can't seem to find any
reference to it anywhere in the KB, although that doesn't mean too much.
2. With the problem in question 1, is installing MSDE SP3a on a server with
SQL Server SP4 a supported thing to do? If not, is an installation program
supposed to deliver multiple versions of MSDE and decide at install time
which version is needed for the server in question? This poses a problem if
one releases software with the MSDE SP3a redist and a new service pack for
SQL Server/MSDE is release after. From what I can tell Microsoft doesn't
really handle this, i.e. Windows SharePoint Services comes with a version of
MSDE SP3a and I haven't seen an update to include MSDE SP4 yet.
3. Again following the previous questions, is it ok to install MSDE SP4 on
servers that have SQL Server 2000 SP2 or SP3a?
Thanks in advance for your time to answer my questions.
Paul
hi Paul,
Paul Degneau wrote:
> A few questions here.
> 1. I have noticed a problem when MSDE SP3a is installed on a server
> with SQL Server SP4. The Registry key value SQLPath at
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
> Server\80\Tools\ClientSetup loses the last character and that makes
> the path to osql, invalid when executing a post replication script.
> It also breaks accessing Query Analyzer and SQL Profiler from
> Enterprise manager among other problems I'm sure. Is this a known
> problem? I can't seem to find any reference to it anywhere in the
> KB, although that doesn't mean too much.
I've reproduced your reported feedback on a Win2003 standard VMWare virtual
machine, updated at Windows update today fixes but Win2003 sp1...
after installing a default instance of SQL Server 2000 Dev Edition and
upgrading it to sp4 I've the reported registry entry..
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\80\Tools\ClientSetup
SQLPath = C:\Program Files\Microsoft SQL Server\80\Tools
installing MSDE sp3 from the
http://www.microsoft.com/sql/downloads/2000/sp3.asp package resulted in the
reported behavior, truncating the SQLPath key to C:\Program Files\Microsoft
SQL Server\80\Tool (without "s") and of course inhibiting the call from
Enterprise Manager to launch QA and Profiler..
running oSql.exe from the command line works as expected... can not
understand the
>and that makes the path to osql,
>invalid when executing a post replication script.
but if the registry key is inspected to run oSql, of course it will fail...
just to test, I fixed the registry entry and installed MSDE from the MSDE
Release A package, http://www.microsoft.com/sql/msde/do.../download.asp,
with the very same result
as additional side note, unistalling the MSDE sp3 instance (that from
http://www.microsoft.com/sql/downloads/2000/sp3.asp package) cleared the
"Startup" folder from the "SQL Server Service Manager" link
I'll pass this "feature" to Microsoft support..
> 2. With the problem in question 1, is installing MSDE SP3a on a
> server with SQL Server SP4 a supported thing to do? If not, is an
> installation program supposed to deliver multiple versions of MSDE
> and decide at install time which version is needed for the server in
> question? This poses a problem if one releases software with the
> MSDE SP3a redist and a new service pack for SQL Server/MSDE is
> release after. From what I can tell Microsoft doesn't really handle
> this, i.e. Windows SharePoint Services comes with a version of MSDE
> SP3a and I haven't seen an update to include MSDE SP4 yet.
AFAIK, an updated version of MSDE Release A updated at service pack 4 has
been promised, but I've no idea about the time frame... about Share Point
WMSDE I do not really know... WMSDE is a specialised version of MSDE and I
expect an updated version will be available... but that's my opinion..
no refresh of SQL Server installation package has been publicised.. you have
to go from the standard path.. install the RTM version and then (manually)
install the desired service pack level (sp3 is the supported SQL Server 2000
version on Win2003 platform)
as regard MSDE, the currently available packages do not (for sure) grant you
a way to decide at run time the service pack level to be installed.. if you
choose sp4 there you are, the same for sp3...
> 3. Again following the previous questions, is it ok to install MSDE
> SP4 on servers that have SQL Server 2000 SP2 or SP3a?
>
actually it should be safe, but consider that installing sp4 updates all
shared bins (those in \Program Files\Microsoft SQL Server\80 folder) to it's
service pack level, but MSDE does not include the full set of tools and bin
but a bunch of them like osql, bcp, svrnecn.exe, SQL-DMO components... a
little mix will be the result
on non Win2003/WinXP systems it will additionaly upgrade MDAC stack to
2.8sp1 (that from WinXP sp2), but this is another story...
but I do think, at the end of all this, that it has been tested
I'll foward the registry stuff ...
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
1. I have noticed a problem when MSDE SP3a is installed on a server with SQL
Server SP4. The Registry key value SQLPath at
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\80\Tools\ClientSetup loses the last character and that makes the path
to osql, invalid when executing a post replication script. It also breaks
accessing Query Analyzer and SQL Profiler from Enterprise manager among other
problems I'm sure. Is this a known problem? I can't seem to find any
reference to it anywhere in the KB, although that doesn't mean too much.
2. With the problem in question 1, is installing MSDE SP3a on a server with
SQL Server SP4 a supported thing to do? If not, is an installation program
supposed to deliver multiple versions of MSDE and decide at install time
which version is needed for the server in question? This poses a problem if
one releases software with the MSDE SP3a redist and a new service pack for
SQL Server/MSDE is release after. From what I can tell Microsoft doesn't
really handle this, i.e. Windows SharePoint Services comes with a version of
MSDE SP3a and I haven't seen an update to include MSDE SP4 yet.
3. Again following the previous questions, is it ok to install MSDE SP4 on
servers that have SQL Server 2000 SP2 or SP3a?
Thanks in advance for your time to answer my questions.
Paul
hi Paul,
Paul Degneau wrote:
> A few questions here.
> 1. I have noticed a problem when MSDE SP3a is installed on a server
> with SQL Server SP4. The Registry key value SQLPath at
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
> Server\80\Tools\ClientSetup loses the last character and that makes
> the path to osql, invalid when executing a post replication script.
> It also breaks accessing Query Analyzer and SQL Profiler from
> Enterprise manager among other problems I'm sure. Is this a known
> problem? I can't seem to find any reference to it anywhere in the
> KB, although that doesn't mean too much.
I've reproduced your reported feedback on a Win2003 standard VMWare virtual
machine, updated at Windows update today fixes but Win2003 sp1...
after installing a default instance of SQL Server 2000 Dev Edition and
upgrading it to sp4 I've the reported registry entry..
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\80\Tools\ClientSetup
SQLPath = C:\Program Files\Microsoft SQL Server\80\Tools
installing MSDE sp3 from the
http://www.microsoft.com/sql/downloads/2000/sp3.asp package resulted in the
reported behavior, truncating the SQLPath key to C:\Program Files\Microsoft
SQL Server\80\Tool (without "s") and of course inhibiting the call from
Enterprise Manager to launch QA and Profiler..
running oSql.exe from the command line works as expected... can not
understand the
>and that makes the path to osql,
>invalid when executing a post replication script.
but if the registry key is inspected to run oSql, of course it will fail...
just to test, I fixed the registry entry and installed MSDE from the MSDE
Release A package, http://www.microsoft.com/sql/msde/do.../download.asp,
with the very same result
as additional side note, unistalling the MSDE sp3 instance (that from
http://www.microsoft.com/sql/downloads/2000/sp3.asp package) cleared the
"Startup" folder from the "SQL Server Service Manager" link
I'll pass this "feature" to Microsoft support..
> 2. With the problem in question 1, is installing MSDE SP3a on a
> server with SQL Server SP4 a supported thing to do? If not, is an
> installation program supposed to deliver multiple versions of MSDE
> and decide at install time which version is needed for the server in
> question? This poses a problem if one releases software with the
> MSDE SP3a redist and a new service pack for SQL Server/MSDE is
> release after. From what I can tell Microsoft doesn't really handle
> this, i.e. Windows SharePoint Services comes with a version of MSDE
> SP3a and I haven't seen an update to include MSDE SP4 yet.
AFAIK, an updated version of MSDE Release A updated at service pack 4 has
been promised, but I've no idea about the time frame... about Share Point
WMSDE I do not really know... WMSDE is a specialised version of MSDE and I
expect an updated version will be available... but that's my opinion..
no refresh of SQL Server installation package has been publicised.. you have
to go from the standard path.. install the RTM version and then (manually)
install the desired service pack level (sp3 is the supported SQL Server 2000
version on Win2003 platform)
as regard MSDE, the currently available packages do not (for sure) grant you
a way to decide at run time the service pack level to be installed.. if you
choose sp4 there you are, the same for sp3...
> 3. Again following the previous questions, is it ok to install MSDE
> SP4 on servers that have SQL Server 2000 SP2 or SP3a?
>
actually it should be safe, but consider that installing sp4 updates all
shared bins (those in \Program Files\Microsoft SQL Server\80 folder) to it's
service pack level, but MSDE does not include the full set of tools and bin
but a bunch of them like osql, bcp, svrnecn.exe, SQL-DMO components... a
little mix will be the result
on non Win2003/WinXP systems it will additionaly upgrade MDAC stack to
2.8sp1 (that from WinXP sp2), but this is another story...
but I do think, at the end of all this, that it has been tested
I'll foward the registry stuff ...
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 sp3a install w/ no password
I was just wondering how I could install an instance of MSDE sp3a (on an XP
machine) without a SAPWD. Thanks.
Anthony
hi Anthony,
Anthony wrote:
> I was just wondering how I could install an instance of MSDE sp3a (on
> an XP machine) without a SAPWD. Thanks.
just provide the
BLANKSAPWD=1
parameter to the setup.exe boostrap installer...
http://msdn.microsoft.com/library/de...stsql_84xl.asp
BTW, just consider this is not a best practice... :D
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
|||Thanks a million. And I agree, probably not a best practice.
Anthony
"Andrea Montanari" wrote:
> hi Anthony,
> Anthony wrote:
> just provide the
> BLANKSAPWD=1
> parameter to the setup.exe boostrap installer...
> http://msdn.microsoft.com/library/de...stsql_84xl.asp
> BTW, just consider this is not a best practice... :D
> --
> 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
>
>
machine) without a SAPWD. Thanks.
Anthony
hi Anthony,
Anthony wrote:
> I was just wondering how I could install an instance of MSDE sp3a (on
> an XP machine) without a SAPWD. Thanks.
just provide the
BLANKSAPWD=1
parameter to the setup.exe boostrap installer...
http://msdn.microsoft.com/library/de...stsql_84xl.asp
BTW, just consider this is not a best practice... :D
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
|||Thanks a million. And I agree, probably not a best practice.
Anthony
"Andrea Montanari" wrote:
> hi Anthony,
> Anthony wrote:
> just provide the
> BLANKSAPWD=1
> parameter to the setup.exe boostrap installer...
> http://msdn.microsoft.com/library/de...stsql_84xl.asp
> BTW, just consider this is not a best practice... :D
> --
> 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
>
>
MSDE SP3a directly on top of SP2?
Hi,
Can MSDE SP3a be installed on top of SP2 without first uninstalling the
latter?
Cheers,
Adrian
hi Adrian,
Adrian wrote:
> Hi,
> Can MSDE SP3a be installed on top of SP2 without first uninstalling
> the latter?
> Cheers,
> Adrian
MSDE Rel A, updated at sp3a level, from the
http://www.microsoft.com/sql/msde/do...s/download.asp package, can not
upgrad existing instances at this service pack level, but only install new
instances..
but you can use the package from
http://www.microsoft.com/sql/downloads/2000/sp3.mspx , or better
http://www.microsoft.com/sql/downloads/2000/sp4.mspx for service pack 4, to
upgrade existing instances to the current/desired sp level without removing
them...
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
|||Thanks!
Adrian
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3j25l7Fnt9l6U1@.individual.net...
> hi Adrian,
> Adrian wrote:
> MSDE Rel A, updated at sp3a level, from the
> http://www.microsoft.com/sql/msde/do...s/download.asp package, can not
> upgrad existing instances at this service pack level, but only install new
> instances..
> but you can use the package from
> http://www.microsoft.com/sql/downloads/2000/sp3.mspx , or better
> http://www.microsoft.com/sql/downloads/2000/sp4.mspx for service pack 4,
> to upgrade existing instances to the current/desired sp level without
> removing them...
> --
> 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
>
Can MSDE SP3a be installed on top of SP2 without first uninstalling the
latter?
Cheers,
Adrian
hi Adrian,
Adrian wrote:
> Hi,
> Can MSDE SP3a be installed on top of SP2 without first uninstalling
> the latter?
> Cheers,
> Adrian
MSDE Rel A, updated at sp3a level, from the
http://www.microsoft.com/sql/msde/do...s/download.asp package, can not
upgrad existing instances at this service pack level, but only install new
instances..
but you can use the package from
http://www.microsoft.com/sql/downloads/2000/sp3.mspx , or better
http://www.microsoft.com/sql/downloads/2000/sp4.mspx for service pack 4, to
upgrade existing instances to the current/desired sp level without removing
them...
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
|||Thanks!
Adrian
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3j25l7Fnt9l6U1@.individual.net...
> hi Adrian,
> Adrian wrote:
> MSDE Rel A, updated at sp3a level, from the
> http://www.microsoft.com/sql/msde/do...s/download.asp package, can not
> upgrad existing instances at this service pack level, but only install new
> instances..
> but you can use the package from
> http://www.microsoft.com/sql/downloads/2000/sp3.mspx , or better
> http://www.microsoft.com/sql/downloads/2000/sp4.mspx for service pack 4,
> to upgrade existing instances to the current/desired sp level without
> removing them...
> --
> 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 SP3a and XP SP2 on Localhost
I've upgraded to SP 2 for Windows XP and now none of my apps can see MSDE
default instance on localhost (i.e. not over the network). I found where an
upgrade to SP3 was required for MSDE to coexist with XP SP2, so I upgraded
and it's still not working.
Is there something else I'm missing?
thanks in advance
XP SP2 installs a new local firewall that prevents applications from opening
listening ports. You will need to configure the local firewall to allow
sqlservr.exe open listening ports.
See:
http://www.microsoft.com/sql/techinf...inxpsp2faq.asp
Jim
"tg2" <tg2@.discussions.microsoft.com> wrote in message
news:344BFC99-5751-46FB-B637-75A70398763B@.microsoft.com...
> I've upgraded to SP 2 for Windows XP and now none of my apps can see MSDE
> default instance on localhost (i.e. not over the network). I found where
an
> upgrade to SP3 was required for MSDE to coexist with XP SP2, so I upgraded
> and it's still not working.
> Is there something else I'm missing?
> thanks in advance
|||Except when running on the localhost (i.e. NOT using the network), the
firewall doesn't come into play. My application is using shared memory to
connect to the MSDE database and as such, never opens a network library --
thus opening the firewall doesn't fix the problem.
But thank you for your reply anyway...
"Jim Young" wrote:
> XP SP2 installs a new local firewall that prevents applications from opening
> listening ports. You will need to configure the local firewall to allow
> sqlservr.exe open listening ports.
> See:
> http://www.microsoft.com/sql/techinf...inxpsp2faq.asp
> Jim
> "tg2" <tg2@.discussions.microsoft.com> wrote in message
> news:344BFC99-5751-46FB-B637-75A70398763B@.microsoft.com...
> an
>
>
|||I have precisely the same problem. My application relies entirely on local
instance of MSDE.
Process associated with sqlservr does not show any port to be opened when
checked with "netstat" command. Any ideas how to work around it?
"tg2" wrote:
> Except when running on the localhost (i.e. NOT using the network), the
> firewall doesn't come into play. My application is using shared memory to
> connect to the MSDE database and as such, never opens a network library --
> thus opening the firewall doesn't fix the problem.
> But thank you for your reply anyway...
>
sql
default instance on localhost (i.e. not over the network). I found where an
upgrade to SP3 was required for MSDE to coexist with XP SP2, so I upgraded
and it's still not working.
Is there something else I'm missing?
thanks in advance
XP SP2 installs a new local firewall that prevents applications from opening
listening ports. You will need to configure the local firewall to allow
sqlservr.exe open listening ports.
See:
http://www.microsoft.com/sql/techinf...inxpsp2faq.asp
Jim
"tg2" <tg2@.discussions.microsoft.com> wrote in message
news:344BFC99-5751-46FB-B637-75A70398763B@.microsoft.com...
> I've upgraded to SP 2 for Windows XP and now none of my apps can see MSDE
> default instance on localhost (i.e. not over the network). I found where
an
> upgrade to SP3 was required for MSDE to coexist with XP SP2, so I upgraded
> and it's still not working.
> Is there something else I'm missing?
> thanks in advance
|||Except when running on the localhost (i.e. NOT using the network), the
firewall doesn't come into play. My application is using shared memory to
connect to the MSDE database and as such, never opens a network library --
thus opening the firewall doesn't fix the problem.
But thank you for your reply anyway...
"Jim Young" wrote:
> XP SP2 installs a new local firewall that prevents applications from opening
> listening ports. You will need to configure the local firewall to allow
> sqlservr.exe open listening ports.
> See:
> http://www.microsoft.com/sql/techinf...inxpsp2faq.asp
> Jim
> "tg2" <tg2@.discussions.microsoft.com> wrote in message
> news:344BFC99-5751-46FB-B637-75A70398763B@.microsoft.com...
> an
>
>
|||I have precisely the same problem. My application relies entirely on local
instance of MSDE.
Process associated with sqlservr does not show any port to be opened when
checked with "netstat" command. Any ideas how to work around it?
"tg2" wrote:
> Except when running on the localhost (i.e. NOT using the network), the
> firewall doesn't come into play. My application is using shared memory to
> connect to the MSDE database and as such, never opens a network library --
> thus opening the firewall doesn't fix the problem.
> But thank you for your reply anyway...
>
sql
MSDE SP3a and XP SP2
Hi
According to various things I've read, XP SP2 will close off SQL Server
ports unless SQL/MSDE SP3 is installed.
However, I've installed MSDE 2000a (equivalent to MSDE 2000 SP3a) with
XP Pro SP2 and no network machine can see the DB server.
I uninstall XP SP2 and the network can see the DB server fine.
Can anybody throw any light onto this?
Thanks
Tony
Hi Tony,
XP SP2 installs an Internet Connection Firewall by default. It will block
the ports you need. You will need to "punch a hole" in the firewall for the
MSDE port (normally 1433 but you can change it using svrnetcn.exe).
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Tony Taylor" <tony@.postopticsNOSPAM.co.uk> wrote in message
news:e1DMi4dhEHA.2052@.tk2msftngp13.phx.gbl...
> Hi
> According to various things I've read, XP SP2 will close off SQL Server
> ports unless SQL/MSDE SP3 is installed.
> However, I've installed MSDE 2000a (equivalent to MSDE 2000 SP3a) with
> XP Pro SP2 and no network machine can see the DB server.
> I uninstall XP SP2 and the network can see the DB server fine.
> Can anybody throw any light onto this?
> Thanks
> Tony
|||Greg Low [MVP] wrote:
> Hi Tony,
> XP SP2 installs an Internet Connection Firewall by default. It will block
> the ports you need. You will need to "punch a hole" in the firewall for the
> MSDE port (normally 1433 but you can change it using svrnetcn.exe).
> HTH,
>
Hi Greg
Thanks for getting back quickly.
How can I find which port the server is listening on?
We're using a named instance which won't use the standard 1433.
With XP SP2, I've run netstat and the sqlservr.exe PID is not listed so
I can't get the port from that. svrnetcn.exe tells me the port is 0 (I
assume that's because XP SP2 has switched it off).
Thanks again
Tony
|||hi Tony,
"Tony Taylor" <tony@.postopticsNOSPAM.co.uk> ha scritto nel messaggio
news:%23tWgd9ehEHA.3912@.TK2MSFTNGP11.phx.gbl...
> How can I find which port the server is listening on?
> We're using a named instance which won't use the standard 1433.
> With XP SP2, I've run netstat and the sqlservr.exe PID is not listed so
> I can't get the port from that. svrnetcn.exe tells me the port is 0 (I
> assume that's because XP SP2 has switched it off).
Named instaces are resolved by the host listening on UDP port 1434, which
then redirect tha specific calls to a dinamically assigned port (as
default)... this is a dynamic port assignement behaviour...
with Windows XP sp2 Windows Firewall which blocs all these connections, you
have to manual set the port you want them to use, so chose a fixed port for
your named instance with Server Network Utility (svrnetcn.exe), open that
port on the Windows Firewall, and, for all remote client, use Client Network
Utility (cloconfg.exe) to map connections to that static port
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
|||You can also add a firewall exception for sqlserver.exe, rather than opening
the port wide open. If other executables need to accept connections, also add
exceptions for them. That will cover any port, but only for that executable.
"Andrea Montanari" wrote:
> hi Tony,
> "Tony Taylor" <tony@.postopticsNOSPAM.co.uk> ha scritto nel messaggio
> news:%23tWgd9ehEHA.3912@.TK2MSFTNGP11.phx.gbl...
> Named instaces are resolved by the host listening on UDP port 1434, which
> then redirect tha specific calls to a dinamically assigned port (as
> default)... this is a dynamic port assignement behaviour...
> with Windows XP sp2 Windows Firewall which blocs all these connections, you
> have to manual set the port you want them to use, so chose a fixed port for
> your named instance with Server Network Utility (svrnetcn.exe), open that
> port on the Windows Firewall, and, for all remote client, use Client Network
> Utility (cloconfg.exe) to map connections to that static port
> --
> 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 Damian,
"Damian" <Damian@.discussions.microsoft.com> ha scritto nel messaggio
news:9F11A754-13A0-4033-81E4-C8354D510EEA@.microsoft.com...
> You can also add a firewall exception for sqlserver.exe, rather than
opening
> the port wide open. If other executables need to accept connections, also
add
> exceptions for them. That will cover any port, but only for that
executable.
still do not have Windows Firewall enabled, but I do think the problem is
outside calls to SQL Server and not the opposite, requiring that
sqlserver.exe should be added to the exceptions list..
but will investigate as soon as I get WinXP sp2 installed
you have to cover outside calls from IIS, winforms apps and so on...
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
|||Damian wrote:
[vbcol=seagreen]
> You can also add a firewall exception for sqlserver.exe, rather than opening
> the port wide open. If other executables need to accept connections, also add
> exceptions for them. That will cover any port, but only for that executable.
> "Andrea Montanari" wrote:
>
Hi chaps
I've tried the follwing:
use svrnetcn.exe to assign a static port to the named instance, open
that port in Windows Firewall and use cliconfg.exe to map connections to
that port
and
allow sqlservr.exe through as an exception in Windows Firewall
but neither have worked. Maybe I've missed something.
Has anyone actually had any success connecting across a network with XP
SP2 on the MSDE box?
Thanks
Tony
According to various things I've read, XP SP2 will close off SQL Server
ports unless SQL/MSDE SP3 is installed.
However, I've installed MSDE 2000a (equivalent to MSDE 2000 SP3a) with
XP Pro SP2 and no network machine can see the DB server.
I uninstall XP SP2 and the network can see the DB server fine.
Can anybody throw any light onto this?
Thanks
Tony
Hi Tony,
XP SP2 installs an Internet Connection Firewall by default. It will block
the ports you need. You will need to "punch a hole" in the firewall for the
MSDE port (normally 1433 but you can change it using svrnetcn.exe).
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Tony Taylor" <tony@.postopticsNOSPAM.co.uk> wrote in message
news:e1DMi4dhEHA.2052@.tk2msftngp13.phx.gbl...
> Hi
> According to various things I've read, XP SP2 will close off SQL Server
> ports unless SQL/MSDE SP3 is installed.
> However, I've installed MSDE 2000a (equivalent to MSDE 2000 SP3a) with
> XP Pro SP2 and no network machine can see the DB server.
> I uninstall XP SP2 and the network can see the DB server fine.
> Can anybody throw any light onto this?
> Thanks
> Tony
|||Greg Low [MVP] wrote:
> Hi Tony,
> XP SP2 installs an Internet Connection Firewall by default. It will block
> the ports you need. You will need to "punch a hole" in the firewall for the
> MSDE port (normally 1433 but you can change it using svrnetcn.exe).
> HTH,
>
Hi Greg
Thanks for getting back quickly.
How can I find which port the server is listening on?
We're using a named instance which won't use the standard 1433.
With XP SP2, I've run netstat and the sqlservr.exe PID is not listed so
I can't get the port from that. svrnetcn.exe tells me the port is 0 (I
assume that's because XP SP2 has switched it off).
Thanks again
Tony
|||hi Tony,
"Tony Taylor" <tony@.postopticsNOSPAM.co.uk> ha scritto nel messaggio
news:%23tWgd9ehEHA.3912@.TK2MSFTNGP11.phx.gbl...
> How can I find which port the server is listening on?
> We're using a named instance which won't use the standard 1433.
> With XP SP2, I've run netstat and the sqlservr.exe PID is not listed so
> I can't get the port from that. svrnetcn.exe tells me the port is 0 (I
> assume that's because XP SP2 has switched it off).
Named instaces are resolved by the host listening on UDP port 1434, which
then redirect tha specific calls to a dinamically assigned port (as
default)... this is a dynamic port assignement behaviour...
with Windows XP sp2 Windows Firewall which blocs all these connections, you
have to manual set the port you want them to use, so chose a fixed port for
your named instance with Server Network Utility (svrnetcn.exe), open that
port on the Windows Firewall, and, for all remote client, use Client Network
Utility (cloconfg.exe) to map connections to that static port
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
|||You can also add a firewall exception for sqlserver.exe, rather than opening
the port wide open. If other executables need to accept connections, also add
exceptions for them. That will cover any port, but only for that executable.
"Andrea Montanari" wrote:
> hi Tony,
> "Tony Taylor" <tony@.postopticsNOSPAM.co.uk> ha scritto nel messaggio
> news:%23tWgd9ehEHA.3912@.TK2MSFTNGP11.phx.gbl...
> Named instaces are resolved by the host listening on UDP port 1434, which
> then redirect tha specific calls to a dinamically assigned port (as
> default)... this is a dynamic port assignement behaviour...
> with Windows XP sp2 Windows Firewall which blocs all these connections, you
> have to manual set the port you want them to use, so chose a fixed port for
> your named instance with Server Network Utility (svrnetcn.exe), open that
> port on the Windows Firewall, and, for all remote client, use Client Network
> Utility (cloconfg.exe) to map connections to that static port
> --
> 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 Damian,
"Damian" <Damian@.discussions.microsoft.com> ha scritto nel messaggio
news:9F11A754-13A0-4033-81E4-C8354D510EEA@.microsoft.com...
> You can also add a firewall exception for sqlserver.exe, rather than
opening
> the port wide open. If other executables need to accept connections, also
add
> exceptions for them. That will cover any port, but only for that
executable.
still do not have Windows Firewall enabled, but I do think the problem is
outside calls to SQL Server and not the opposite, requiring that
sqlserver.exe should be added to the exceptions list..
but will investigate as soon as I get WinXP sp2 installed
you have to cover outside calls from IIS, winforms apps and so on...
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
|||Damian wrote:
[vbcol=seagreen]
> You can also add a firewall exception for sqlserver.exe, rather than opening
> the port wide open. If other executables need to accept connections, also add
> exceptions for them. That will cover any port, but only for that executable.
> "Andrea Montanari" wrote:
>
Hi chaps
I've tried the follwing:
use svrnetcn.exe to assign a static port to the named instance, open
that port in Windows Firewall and use cliconfg.exe to map connections to
that port
and
allow sqlservr.exe through as an exception in Windows Firewall
but neither have worked. Maybe I've missed something.
Has anyone actually had any success connecting across a network with XP
SP2 on the MSDE box?
Thanks
Tony
MSDE sp3a & XP-sp2
My clients are reporting they cannot connect to the msde database using my
application - generic failed to connect message.
My software application installs the MSDE. Their computer is a brand new
machine with XP-sp2 installed. The sp2 is not an upgrade. We have only
seen this phenomena with a machine where we cannot uninstall sp2. On
machines we can, our application can connect. On most (to all) machines
where we install xp-sp2 ourselves there is no problem.
Any ideas?
Check wheter the firewall of the XPs opened up the port to connect to the
msde, if not open up.
For a fast try deactivate the firewallfor checking, if its working open up
dedicated ports.
HTH, Jens Smeyer
http://www.sqlserver2005.de
"Robert A. DiFrancesco" <bob.difrancesco@.comcash.com> schrieb im Newsbeitrag
news:u6h0w7TQFHA.3596@.TK2MSFTNGP15.phx.gbl...
> My clients are reporting they cannot connect to the msde database using my
> application - generic failed to connect message.
> My software application installs the MSDE. Their computer is a brand new
> machine with XP-sp2 installed. The sp2 is not an upgrade. We have only
> seen this phenomena with a machine where we cannot uninstall sp2. On
> machines we can, our application can connect. On most (to all) machines
> where we install xp-sp2 ourselves there is no problem.
> Any ideas?
>
|||Did all that.
What could be different about a machine pre-loaded with xp-sp2?
"Jens Smeyer" <Jens@.Remove_this_For_Contacting.sqlserver2005.de> wrote in
message news:%23Pbrs%23TQFHA.1172@.TK2MSFTNGP12.phx.gbl...
> Check wheter the firewall of the XPs opened up the port to connect to the
> msde, if not open up.
> For a fast try deactivate the firewallfor checking, if its working open up
> dedicated ports.
>
> HTH, Jens Smeyer
> --
> http://www.sqlserver2005.de
> --
>
> "Robert A. DiFrancesco" <bob.difrancesco@.comcash.com> schrieb im
> Newsbeitrag news:u6h0w7TQFHA.3596@.TK2MSFTNGP15.phx.gbl...
>
application - generic failed to connect message.
My software application installs the MSDE. Their computer is a brand new
machine with XP-sp2 installed. The sp2 is not an upgrade. We have only
seen this phenomena with a machine where we cannot uninstall sp2. On
machines we can, our application can connect. On most (to all) machines
where we install xp-sp2 ourselves there is no problem.
Any ideas?
Check wheter the firewall of the XPs opened up the port to connect to the
msde, if not open up.
For a fast try deactivate the firewallfor checking, if its working open up
dedicated ports.
HTH, Jens Smeyer
http://www.sqlserver2005.de
"Robert A. DiFrancesco" <bob.difrancesco@.comcash.com> schrieb im Newsbeitrag
news:u6h0w7TQFHA.3596@.TK2MSFTNGP15.phx.gbl...
> My clients are reporting they cannot connect to the msde database using my
> application - generic failed to connect message.
> My software application installs the MSDE. Their computer is a brand new
> machine with XP-sp2 installed. The sp2 is not an upgrade. We have only
> seen this phenomena with a machine where we cannot uninstall sp2. On
> machines we can, our application can connect. On most (to all) machines
> where we install xp-sp2 ourselves there is no problem.
> Any ideas?
>
|||Did all that.
What could be different about a machine pre-loaded with xp-sp2?
"Jens Smeyer" <Jens@.Remove_this_For_Contacting.sqlserver2005.de> wrote in
message news:%23Pbrs%23TQFHA.1172@.TK2MSFTNGP12.phx.gbl...
> Check wheter the firewall of the XPs opened up the port to connect to the
> msde, if not open up.
> For a fast try deactivate the firewallfor checking, if its working open up
> dedicated ports.
>
> HTH, Jens Smeyer
> --
> http://www.sqlserver2005.de
> --
>
> "Robert A. DiFrancesco" <bob.difrancesco@.comcash.com> schrieb im
> Newsbeitrag news:u6h0w7TQFHA.3596@.TK2MSFTNGP15.phx.gbl...
>
MSDE sp3a & XP-sp2
My clients are reporting they cannot connect to the msde database using my
application - generic failed to connect message.
My software application installs the MSDE. Their computer is a brand new
machine with XP-sp2 installed. The sp2 is not an upgrade. We have only
seen this phenomena with a machine where we cannot uninstall sp2. On
machines we can, our application can connect. On most (to all) machines
where we install xp-sp2 ourselves there is no problem.
Any ideas?Check wheter the firewall of the XPs opened up the port to connect to the
msde, if not open up.
For a fast try deactivate the firewallfor checking, if its working open up
dedicated ports.
HTH, Jens Smeyer
http://www.sqlserver2005.de
--
"Robert A. DiFrancesco" <bob.difrancesco@.comcash.com> schrieb im Newsbeitrag
news:u6h0w7TQFHA.3596@.TK2MSFTNGP15.phx.gbl...
> My clients are reporting they cannot connect to the msde database using my
> application - generic failed to connect message.
> My software application installs the MSDE. Their computer is a brand new
> machine with XP-sp2 installed. The sp2 is not an upgrade. We have only
> seen this phenomena with a machine where we cannot uninstall sp2. On
> machines we can, our application can connect. On most (to all) machines
> where we install xp-sp2 ourselves there is no problem.
> Any ideas?
>|||Did all that.
What could be different about a machine pre-loaded with xp-sp2'
"Jens Smeyer" <Jens@.Remove_this_For_Contacting.sqlserver2005.de> wrote in
message news:%23Pbrs%23TQFHA.1172@.TK2MSFTNGP12.phx.gbl...
> Check wheter the firewall of the XPs opened up the port to connect to the
> msde, if not open up.
> For a fast try deactivate the firewallfor checking, if its working open up
> dedicated ports.
>
> HTH, Jens Smeyer
> --
> http://www.sqlserver2005.de
> --
>
> "Robert A. DiFrancesco" <bob.difrancesco@.comcash.com> schrieb im
> Newsbeitrag news:u6h0w7TQFHA.3596@.TK2MSFTNGP15.phx.gbl...
>
application - generic failed to connect message.
My software application installs the MSDE. Their computer is a brand new
machine with XP-sp2 installed. The sp2 is not an upgrade. We have only
seen this phenomena with a machine where we cannot uninstall sp2. On
machines we can, our application can connect. On most (to all) machines
where we install xp-sp2 ourselves there is no problem.
Any ideas?Check wheter the firewall of the XPs opened up the port to connect to the
msde, if not open up.
For a fast try deactivate the firewallfor checking, if its working open up
dedicated ports.
HTH, Jens Smeyer
http://www.sqlserver2005.de
--
"Robert A. DiFrancesco" <bob.difrancesco@.comcash.com> schrieb im Newsbeitrag
news:u6h0w7TQFHA.3596@.TK2MSFTNGP15.phx.gbl...
> My clients are reporting they cannot connect to the msde database using my
> application - generic failed to connect message.
> My software application installs the MSDE. Their computer is a brand new
> machine with XP-sp2 installed. The sp2 is not an upgrade. We have only
> seen this phenomena with a machine where we cannot uninstall sp2. On
> machines we can, our application can connect. On most (to all) machines
> where we install xp-sp2 ourselves there is no problem.
> Any ideas?
>|||Did all that.
What could be different about a machine pre-loaded with xp-sp2'
"Jens Smeyer" <Jens@.Remove_this_For_Contacting.sqlserver2005.de> wrote in
message news:%23Pbrs%23TQFHA.1172@.TK2MSFTNGP12.phx.gbl...
> Check wheter the firewall of the XPs opened up the port to connect to the
> msde, if not open up.
> For a fast try deactivate the firewallfor checking, if its working open up
> dedicated ports.
>
> HTH, Jens Smeyer
> --
> http://www.sqlserver2005.de
> --
>
> "Robert A. DiFrancesco" <bob.difrancesco@.comcash.com> schrieb im
> Newsbeitrag news:u6h0w7TQFHA.3596@.TK2MSFTNGP15.phx.gbl...
>
Monday, March 19, 2012
MSDE newbie
I Just installed MDSE2000A (ithink it already comes with SP3a), by doing
Setup.exe /qb+ INSTANCENAME=MOC DISABLENETWORKPROTOCOLS=1 SAPWD=moc
I downloaded the northwind database and tried to install it by doing
osql -E -Q "EXEC sp_attach_db N'Northwind', N'c:\SQL Server 2000 Sample
Databases\northwind.mdf'"
the response was
[Shared Memory]Invalid connection.
[Shared Memory]ConnectionOpen (Invalid Instance()).
what have I done wrong?
You did not specify th instance you want to connect to, this can be done
with the switch -S
osql -E -Q "EXEC sp_attach_db N'Northwind', N'c:\SQL Server 2000 Sample
Databases\northwind.mdf' -SServername\Instancename
Would be on the the local server ".\MOC"
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Joo Costa" <JooCosta@.discussions.microsoft.com> schrieb im Newsbeitrag
news:520F0379-78B1-449C-9864-896E04C5C910@.microsoft.com...
>I Just installed MDSE2000A (ithink it already comes with SP3a), by doing
> Setup.exe /qb+ INSTANCENAME=MOC DISABLENETWORKPROTOCOLS=1 SAPWD=moc
> I downloaded the northwind database and tried to install it by doing
> osql -E -Q "EXEC sp_attach_db N'Northwind', N'c:\SQL Server 2000 Sample
> Databases\northwind.mdf'"
> the response was
> [Shared Memory]Invalid connection.
> [Shared Memory]ConnectionOpen (Invalid Instance()).
> what have I done wrong?
|||thanks, now I have unather problem, I transcribed the line below:
osql -E -Q "EXEC sp_attach_db N'Northwind', N'c:\SQL Server 2000 Sample
Databases\northwind.mdf'" -S.\MOC
the answer was:
Msg 5105, Level 16, State 4, Server RAINBOWARRIOR\MOC, Line 1
Device activation error. The physical file name 'c:\SQL Server 2000 Sample
Databases\northwind.mdf' may be incorrect.
"Jens Sü?meyer" wrote:
> You did not specify th instance you want to connect to, this can be done
> with the switch -S
> osql -E -Q "EXEC sp_attach_db N'Northwind', N'c:\SQL Server 2000 Sample
> Databases\northwind.mdf' -SServername\Instancename
> Would be on the the local server ".\MOC"
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>
> "Jo?o Costa" <JooCosta@.discussions.microsoft.com> schrieb im Newsbeitrag
> news:520F0379-78B1-449C-9864-896E04C5C910@.microsoft.com...
>
>
|||The problem is that there are spaces in the pathname, if you could get
around this you should use a simple path which doesnt contain any space
perhaps c:\sql. If you cant you have to doublequote the Quotes.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Joo Costa" <JooCosta@.discussions.microsoft.com> schrieb im Newsbeitrag
news:6A7F0B79-0B83-46C3-A1D6-C48EB86E0C8B@.microsoft.com...[vbcol=seagreen]
> thanks, now I have unather problem, I transcribed the line below:
> osql -E -Q "EXEC sp_attach_db N'Northwind', N'c:\SQL Server 2000 Sample
> Databases\northwind.mdf'" -S.\MOC
> the answer was:
> Msg 5105, Level 16, State 4, Server RAINBOWARRIOR\MOC, Line 1
> Device activation error. The physical file name 'c:\SQL Server 2000 Sample
> Databases\northwind.mdf' may be incorrect.
> "Jens Smeyer" wrote:
|||thanks!
"Jens Sü?meyer" wrote:
> The problem is that there are spaces in the pathname, if you could get
> around this you should use a simple path which doesn′t contain any space
> perhaps c:\sql. If you can′t you have to doublequote the Quotes.
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>
> "Jo?o Costa" <JooCosta@.discussions.microsoft.com> schrieb im Newsbeitrag
> news:6A7F0B79-0B83-46C3-A1D6-C48EB86E0C8B@.microsoft.com...
>
>
Setup.exe /qb+ INSTANCENAME=MOC DISABLENETWORKPROTOCOLS=1 SAPWD=moc
I downloaded the northwind database and tried to install it by doing
osql -E -Q "EXEC sp_attach_db N'Northwind', N'c:\SQL Server 2000 Sample
Databases\northwind.mdf'"
the response was
[Shared Memory]Invalid connection.
[Shared Memory]ConnectionOpen (Invalid Instance()).
what have I done wrong?
You did not specify th instance you want to connect to, this can be done
with the switch -S
osql -E -Q "EXEC sp_attach_db N'Northwind', N'c:\SQL Server 2000 Sample
Databases\northwind.mdf' -SServername\Instancename
Would be on the the local server ".\MOC"
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Joo Costa" <JooCosta@.discussions.microsoft.com> schrieb im Newsbeitrag
news:520F0379-78B1-449C-9864-896E04C5C910@.microsoft.com...
>I Just installed MDSE2000A (ithink it already comes with SP3a), by doing
> Setup.exe /qb+ INSTANCENAME=MOC DISABLENETWORKPROTOCOLS=1 SAPWD=moc
> I downloaded the northwind database and tried to install it by doing
> osql -E -Q "EXEC sp_attach_db N'Northwind', N'c:\SQL Server 2000 Sample
> Databases\northwind.mdf'"
> the response was
> [Shared Memory]Invalid connection.
> [Shared Memory]ConnectionOpen (Invalid Instance()).
> what have I done wrong?
|||thanks, now I have unather problem, I transcribed the line below:
osql -E -Q "EXEC sp_attach_db N'Northwind', N'c:\SQL Server 2000 Sample
Databases\northwind.mdf'" -S.\MOC
the answer was:
Msg 5105, Level 16, State 4, Server RAINBOWARRIOR\MOC, Line 1
Device activation error. The physical file name 'c:\SQL Server 2000 Sample
Databases\northwind.mdf' may be incorrect.
"Jens Sü?meyer" wrote:
> You did not specify th instance you want to connect to, this can be done
> with the switch -S
> osql -E -Q "EXEC sp_attach_db N'Northwind', N'c:\SQL Server 2000 Sample
> Databases\northwind.mdf' -SServername\Instancename
> Would be on the the local server ".\MOC"
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>
> "Jo?o Costa" <JooCosta@.discussions.microsoft.com> schrieb im Newsbeitrag
> news:520F0379-78B1-449C-9864-896E04C5C910@.microsoft.com...
>
>
|||The problem is that there are spaces in the pathname, if you could get
around this you should use a simple path which doesnt contain any space
perhaps c:\sql. If you cant you have to doublequote the Quotes.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Joo Costa" <JooCosta@.discussions.microsoft.com> schrieb im Newsbeitrag
news:6A7F0B79-0B83-46C3-A1D6-C48EB86E0C8B@.microsoft.com...[vbcol=seagreen]
> thanks, now I have unather problem, I transcribed the line below:
> osql -E -Q "EXEC sp_attach_db N'Northwind', N'c:\SQL Server 2000 Sample
> Databases\northwind.mdf'" -S.\MOC
> the answer was:
> Msg 5105, Level 16, State 4, Server RAINBOWARRIOR\MOC, Line 1
> Device activation error. The physical file name 'c:\SQL Server 2000 Sample
> Databases\northwind.mdf' may be incorrect.
> "Jens Smeyer" wrote:
|||thanks!
"Jens Sü?meyer" wrote:
> The problem is that there are spaces in the pathname, if you could get
> around this you should use a simple path which doesn′t contain any space
> perhaps c:\sql. If you can′t you have to doublequote the Quotes.
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>
> "Jo?o Costa" <JooCosta@.discussions.microsoft.com> schrieb im Newsbeitrag
> news:6A7F0B79-0B83-46C3-A1D6-C48EB86E0C8B@.microsoft.com...
>
>
MSDE memory Usage
It seems that the MSDE running SP3a is eating up about 100MB every few days
on my system. Once I reboot it settles down but starts it up again. Is
there a memory leak? Is there a way to calm down the SQLSERVER.EXE memory
usuage?
Thanks
The SQL Server 2000 database engine is designed to take advantage of as much
memory as it can without impacting other applications. If other applications
start running on the computer the database engine will dynamically release
memory for their use. You can also tailor how much memory the database
engine uses by setting configuration options.
For more information, see:
http://msdn.microsoft.com/library/?u...asp?frame=true
Alan Brewer [MSFT]
Content Architect
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
on my system. Once I reboot it settles down but starts it up again. Is
there a memory leak? Is there a way to calm down the SQLSERVER.EXE memory
usuage?
Thanks
The SQL Server 2000 database engine is designed to take advantage of as much
memory as it can without impacting other applications. If other applications
start running on the computer the database engine will dynamically release
memory for their use. You can also tailor how much memory the database
engine uses by setting configuration options.
For more information, see:
http://msdn.microsoft.com/library/?u...asp?frame=true
Alan Brewer [MSFT]
Content Architect
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
Friday, March 9, 2012
MSDE installation/connection issues
I installed MSDE (sp3a) in a Windows 2000 server SP4. This is configured to
be a domain controller and (AD turned on). I can use MSDE webadmin to
access the database instance fine. I have a couple of problems.
1. MSSQLServerADHelper service does not startup.
System log message is:
The MSSQLServerADHelper service terminated with service-specific error
3221225572.
Corresponding Application log error is:
'0' is an invalid number of start up parameters. This service takes two
start up parameters.
2.Despite following the instructions in KB article: 840219 I still 'm not
able to login to MSDE using OSQL from a command prompt. Error message is:
Cr>osql -U domain\administrator -P xxxx
Login failed for user 'domain\administrator'. Reason: Not associated with a
trusted SQL Server connection.
Is something wrong with my syntax for the value for the -U parameter? I
restarted the SQL server and the agent services after following the steps in
840219.
Any suggestions appreciated.
hi,
"public.microsoft.com" <lakamsani AT gmail.com> ha scritto nel messaggio
news:%23kZ5Z$cbEHA.3684@.TK2MSFTNGP09.phx.gbl...
> I installed MSDE (sp3a) in a Windows 2000 server SP4. This is configured
to
> be a domain controller and (AD turned on). I can use MSDE webadmin to
> access the database instance fine. I have a couple of problems.
> 1. MSSQLServerADHelper service does not startup.
> System log message is:
> The MSSQLServerADHelper service terminated with service-specific error
> 3221225572.
please have a look at http://tinyurl.com/6qwgg
> 2.Despite following the instructions in KB article: 840219 I still 'm not
> able to login to MSDE using OSQL from a command prompt. Error message is:
> Cr>osql -U domain\administrator -P xxxx
> Login failed for user 'domain\administrator'. Reason: Not associated with
a
> trusted SQL Server connection.
> Is something wrong with my syntax for the value for the -U parameter? I
> restarted the SQL server and the agent services after following the steps
in
> 840219.
for trusted connections, you shoul'd pass the -E parameter (where -E
specifys a trusted connection using you actual WindowsNT login credential)
instead that providing SQL Server authenticated related credentials...
tipically
c:\>osql -E
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
be a domain controller and (AD turned on). I can use MSDE webadmin to
access the database instance fine. I have a couple of problems.
1. MSSQLServerADHelper service does not startup.
System log message is:
The MSSQLServerADHelper service terminated with service-specific error
3221225572.
Corresponding Application log error is:
'0' is an invalid number of start up parameters. This service takes two
start up parameters.
2.Despite following the instructions in KB article: 840219 I still 'm not
able to login to MSDE using OSQL from a command prompt. Error message is:
Cr>osql -U domain\administrator -P xxxx
Login failed for user 'domain\administrator'. Reason: Not associated with a
trusted SQL Server connection.
Is something wrong with my syntax for the value for the -U parameter? I
restarted the SQL server and the agent services after following the steps in
840219.
Any suggestions appreciated.
hi,
"public.microsoft.com" <lakamsani AT gmail.com> ha scritto nel messaggio
news:%23kZ5Z$cbEHA.3684@.TK2MSFTNGP09.phx.gbl...
> I installed MSDE (sp3a) in a Windows 2000 server SP4. This is configured
to
> be a domain controller and (AD turned on). I can use MSDE webadmin to
> access the database instance fine. I have a couple of problems.
> 1. MSSQLServerADHelper service does not startup.
> System log message is:
> The MSSQLServerADHelper service terminated with service-specific error
> 3221225572.
please have a look at http://tinyurl.com/6qwgg
> 2.Despite following the instructions in KB article: 840219 I still 'm not
> able to login to MSDE using OSQL from a command prompt. Error message is:
> Cr>osql -U domain\administrator -P xxxx
> Login failed for user 'domain\administrator'. Reason: Not associated with
a
> trusted SQL Server connection.
> Is something wrong with my syntax for the value for the -U parameter? I
> restarted the SQL server and the agent services after following the steps
in
> 840219.
for trusted connections, you shoul'd pass the -E parameter (where -E
specifys a trusted connection using you actual WindowsNT login credential)
instead that providing SQL Server authenticated related credentials...
tipically
c:\>osql -E
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
MSDE Installation problem.
I have recently installed MSDE and SP3a on my Windows XP
Pro machine. XP SP2 was installed prior to the MSDE
installation. The installation of both MSDE & SP3a
completed without error.
When I log in the server icon appears on the taskbar.
When I place the mouse pointer over the icon "Unknown -
\\ - MSSQLServer" appears.
When I right click the icon and attempt to start, I
receive the following.
"Error The handle is invalid."
I click OK.
The following error appears.
"An error 6 - (The handle is invalid.) occurred while
performing the service operation on the MSSQLSeerver
service."
I click stop and then receive the same errors in the same
order after being asked if I am sure I wish to stop.
I applied a strong password when installing.
Thoughts?
I am seeing the same symptoms as you are. I just installed VS.Net 2003 and MSDE on a brand spanking new hard disk with windows xp sp2 on it. Though, I don't know if it is the latest version of MSDE.
If I open the sql manager there is nothing in the server field. When I try using "local" and click on the refresh services button I get an error saying "The network path is not found."
Any ideas how I can get MSDE running?
thanks!|||Likewise, same problem, though I'm working off win2k and reached msde need
through a limited period copy of Visual.net (for learning purposes).
I'm afraid I'm not at the pc at the moment, but I installed the msde desktop
patch and wasn't sure whether should also have installed the two other
patches that were available.
I await with interest!
Ivor
"anonymous@.discussions.microsoft.com" wrote:
> I have recently installed MSDE and SP3a on my Windows XP
> Pro machine. XP SP2 was installed prior to the MSDE
> installation. The installation of both MSDE & SP3a
> completed without error.
> When I log in the server icon appears on the taskbar.
> When I place the mouse pointer over the icon "Unknown -
> \\ - MSSQLServer" appears.
> When I right click the icon and attempt to start, I
> receive the following.
> "Error The handle is invalid."
> I click OK.
> The following error appears.
> "An error 6 - (The handle is invalid.) occurred while
> performing the service operation on the MSSQLSeerver
> service."
> I click stop and then receive the same errors in the same
> order after being asked if I am sure I wish to stop.
> I applied a strong password when installing.
> Thoughts?
>
|||I have the same problem.... Any help would really be appreciated..
_cCp
Originally posted by Ivor
Likewise, same problem, though I'm working off win2k and reached msde need
through a limited period copy of Visual.net (for learning purposes).
I'm afraid I'm not at the pc at the moment, but I installed the msde desktop
patch and wasn't sure whether should also have installed the two other
patches that were available.
I await with interest!
Ivor
"anonymous@.discussions.microsoft.com" wrote:
> I have recently installed MSDE and SP3a on my Windows XP
> Pro machine. XP SP2 was installed prior to the MSDE
> installation. The installation of both MSDE & SP3a
> completed without error.
> When I log in the server icon appears on the taskbar.
> When I place the mouse pointer over the icon "Unknown -
> \\ - MSSQLServer" appears.
> When I right click the icon and attempt to start, I
> receive the following.
> "Error The handle is invalid."
> I click OK.
> The following error appears.
> "An error 6 - (The handle is invalid.) occurred while
> performing the service operation on the MSSQLSeerver
> service."
> I click stop and then receive the same errors in the same
> order after being asked if I am sure I wish to stop.
> I applied a strong password when installing.
> Thoughts?
>
account in windows, you need to change some of the security policies. I'm
not on the machine at the moment, try a search in Knowledge Base or email me
on marmite REMOVE THIS BIT@.fastmail.fm
"plummernh" wrote:
> I have the same problem.... Any help would really be appreciated..
> _cCp
> Ivor wrote:
>
> --
> plummernh
> Posted via http://www.mcse.ms
> View this thread: http://www.mcse.ms/message1050720.html
>
Pro machine. XP SP2 was installed prior to the MSDE
installation. The installation of both MSDE & SP3a
completed without error.
When I log in the server icon appears on the taskbar.
When I place the mouse pointer over the icon "Unknown -
\\ - MSSQLServer" appears.
When I right click the icon and attempt to start, I
receive the following.
"Error The handle is invalid."
I click OK.
The following error appears.
"An error 6 - (The handle is invalid.) occurred while
performing the service operation on the MSSQLSeerver
service."
I click stop and then receive the same errors in the same
order after being asked if I am sure I wish to stop.
I applied a strong password when installing.
Thoughts?
I am seeing the same symptoms as you are. I just installed VS.Net 2003 and MSDE on a brand spanking new hard disk with windows xp sp2 on it. Though, I don't know if it is the latest version of MSDE.
If I open the sql manager there is nothing in the server field. When I try using "local" and click on the refresh services button I get an error saying "The network path is not found."
Any ideas how I can get MSDE running?
thanks!|||Likewise, same problem, though I'm working off win2k and reached msde need
through a limited period copy of Visual.net (for learning purposes).
I'm afraid I'm not at the pc at the moment, but I installed the msde desktop
patch and wasn't sure whether should also have installed the two other
patches that were available.
I await with interest!
Ivor
"anonymous@.discussions.microsoft.com" wrote:
> I have recently installed MSDE and SP3a on my Windows XP
> Pro machine. XP SP2 was installed prior to the MSDE
> installation. The installation of both MSDE & SP3a
> completed without error.
> When I log in the server icon appears on the taskbar.
> When I place the mouse pointer over the icon "Unknown -
> \\ - MSSQLServer" appears.
> When I right click the icon and attempt to start, I
> receive the following.
> "Error The handle is invalid."
> I click OK.
> The following error appears.
> "An error 6 - (The handle is invalid.) occurred while
> performing the service operation on the MSSQLSeerver
> service."
> I click stop and then receive the same errors in the same
> order after being asked if I am sure I wish to stop.
> I applied a strong password when installing.
> Thoughts?
>
|||I have the same problem.... Any help would really be appreciated..
_cCp
Quote:
Likewise, same problem, though I'm working off win2k and reached msde need
through a limited period copy of Visual.net (for learning purposes).
I'm afraid I'm not at the pc at the moment, but I installed the msde desktop
patch and wasn't sure whether should also have installed the two other
patches that were available.
I await with interest!
Ivor
"anonymous@.discussions.microsoft.com" wrote:
> I have recently installed MSDE and SP3a on my Windows XP
> Pro machine. XP SP2 was installed prior to the MSDE
> installation. The installation of both MSDE & SP3a
> completed without error.
> When I log in the server icon appears on the taskbar.
> When I place the mouse pointer over the icon "Unknown -
> \\ - MSSQLServer" appears.
> When I right click the icon and attempt to start, I
> receive the following.
> "Error The handle is invalid."
> I click OK.
> The following error appears.
> "An error 6 - (The handle is invalid.) occurred while
> performing the service operation on the MSSQLSeerver
> service."
> I click stop and then receive the same errors in the same
> order after being asked if I am sure I wish to stop.
> I applied a strong password when installing.
> Thoughts?
>
account in windows, you need to change some of the security policies. I'm
not on the machine at the moment, try a search in Knowledge Base or email me
on marmite REMOVE THIS BIT@.fastmail.fm
"plummernh" wrote:
> I have the same problem.... Any help would really be appreciated..
> _cCp
> Ivor wrote:
>
> --
> plummernh
> Posted via http://www.mcse.ms
> View this thread: http://www.mcse.ms/message1050720.html
>
Wednesday, March 7, 2012
MSDE install runs after reboot
After installing MSDE SP3a on a windows server 2003 machine, I am prompted for a reboot. Upon rebooting, the installer still seems to be running as a dialog pops up saying something about configuring MSDE. Then the MSDE service is restarted.
This may not sound like a problem, but I am starting the MSDE installer from InstallShield and after rebooting I have no idea when MSDE is done with the database and when I can start running my db config scripts.
What is MSDE doing after reboot? Is it necessary? When do I know it's done? I'm temted to just have my script wait for a minute before running, but that's not very professional, is it?
Thanks,
hi,
"yaknuts" <yaknuts@.discussions.microsoft.com> ha scritto nel messaggio
news:BE797E25-E978-4ED8-8B15-5ABF4AD6174E@.microsoft.com...
> What is MSDE doing after reboot? Is it necessary? When do I know it's
done? I'm temted to
>just have my script wait for a minute before running, but that's not very
professional, is it?
after reboot, a lot of COM object are registred, including SQL-DMO , MDAC if
versoion required...
service are set...
some users forced not rebooting passing the REBOOT=""ReallySuppress""
WindowsInstaller parameter, but I'm not very confidentent with =;-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
|||Well, I wish there was a way I could tell it to not restart the service after it has already rebooted. The Reboot isn't my main concern, but more or less after the reboot, the service I just installed with my installshield package is started, and wants t
o run the config script, however, MSDE is still being modfied and the services are restarted again WHILE mine are accessing it, causing error,
hopefully you understand my dilemma, as it's really frustrating to me and there should be a way to get around this...
Thanks,
Jacob
"Andrea Montanari" wrote:
> hi,
> "yaknuts" <yaknuts@.discussions.microsoft.com> ha scritto nel messaggio
> news:BE797E25-E978-4ED8-8B15-5ABF4AD6174E@.microsoft.com...
> done? I'm temted to
> professional, is it?
> after reboot, a lot of COM object are registred, including SQL-DMO , MDAC if
> versoion required...
> service are set...
> some users forced not rebooting passing the REBOOT=""ReallySuppress""
> WindowsInstaller parameter, but I'm not very confidentent with =;-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
>
|||hi Jacob,
"Jacob Schroeder (yaknuts)" <Jacob Schroeder
(yaknuts)@.discussions.microsoft.com> ha scritto nel messaggio
news:603168F6-92B6-4F94-B6DF-F8633B78A0AA@.microsoft.com...
> Well, I wish there was a way I could tell it to not restart the service
after it has already
>rebooted. The Reboot isn't my main concern, but more or less after the
reboot, the
>service I just installed with my installshield package is started, and
wants to run the
>config script, however, MSDE is still being modfied and the services are
restarted
>again WHILE mine are accessing it, causing error,
> hopefully you understand my dilemma, as it's really frustrating to me and
there should
>be a way to get around this...
unfortunately I'm not a Wise pro =;-D
I do install MSDE as a separate package... self contained.... so I do not
care about reboot requirements...
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
|||Did you wite your own service app?
You could
- work with dependencies
- use a delay, since it's a one time thing. Either use a fixed periode, or
detect if the MSDE services you need are started
JAn
"Jacob Schroeder (yaknuts)" <Jacob Schroeder
(yaknuts)@.discussions.microsoft.com> wrote in message
news:603168F6-92B6-4F94-B6DF-F8633B78A0AA@.microsoft.com...
> Well, I wish there was a way I could tell it to not restart the service
after it has already rebooted. The Reboot isn't my main concern, but more
or less after the reboot, the service I just installed with my installshield
package is started, and wants to run the config script, however, MSDE is
still being modfied and the services are restarted again WHILE mine are
accessing it, causing error,
> hopefully you understand my dilemma, as it's really frustrating to me and
there should be a way to get around this...[vbcol=seagreen]
> Thanks,
> Jacob
>
> "Andrea Montanari" wrote:
it's[vbcol=seagreen]
very[vbcol=seagreen]
MDAC if[vbcol=seagreen]
This may not sound like a problem, but I am starting the MSDE installer from InstallShield and after rebooting I have no idea when MSDE is done with the database and when I can start running my db config scripts.
What is MSDE doing after reboot? Is it necessary? When do I know it's done? I'm temted to just have my script wait for a minute before running, but that's not very professional, is it?
Thanks,
hi,
"yaknuts" <yaknuts@.discussions.microsoft.com> ha scritto nel messaggio
news:BE797E25-E978-4ED8-8B15-5ABF4AD6174E@.microsoft.com...
> What is MSDE doing after reboot? Is it necessary? When do I know it's
done? I'm temted to
>just have my script wait for a minute before running, but that's not very
professional, is it?
after reboot, a lot of COM object are registred, including SQL-DMO , MDAC if
versoion required...
service are set...
some users forced not rebooting passing the REBOOT=""ReallySuppress""
WindowsInstaller parameter, but I'm not very confidentent with =;-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
|||Well, I wish there was a way I could tell it to not restart the service after it has already rebooted. The Reboot isn't my main concern, but more or less after the reboot, the service I just installed with my installshield package is started, and wants t
o run the config script, however, MSDE is still being modfied and the services are restarted again WHILE mine are accessing it, causing error,
hopefully you understand my dilemma, as it's really frustrating to me and there should be a way to get around this...
Thanks,
Jacob
"Andrea Montanari" wrote:
> hi,
> "yaknuts" <yaknuts@.discussions.microsoft.com> ha scritto nel messaggio
> news:BE797E25-E978-4ED8-8B15-5ABF4AD6174E@.microsoft.com...
> done? I'm temted to
> professional, is it?
> after reboot, a lot of COM object are registred, including SQL-DMO , MDAC if
> versoion required...
> service are set...
> some users forced not rebooting passing the REBOOT=""ReallySuppress""
> WindowsInstaller parameter, but I'm not very confidentent with =;-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
>
|||hi Jacob,
"Jacob Schroeder (yaknuts)" <Jacob Schroeder
(yaknuts)@.discussions.microsoft.com> ha scritto nel messaggio
news:603168F6-92B6-4F94-B6DF-F8633B78A0AA@.microsoft.com...
> Well, I wish there was a way I could tell it to not restart the service
after it has already
>rebooted. The Reboot isn't my main concern, but more or less after the
reboot, the
>service I just installed with my installshield package is started, and
wants to run the
>config script, however, MSDE is still being modfied and the services are
restarted
>again WHILE mine are accessing it, causing error,
> hopefully you understand my dilemma, as it's really frustrating to me and
there should
>be a way to get around this...
unfortunately I'm not a Wise pro =;-D
I do install MSDE as a separate package... self contained.... so I do not
care about reboot requirements...
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
|||Did you wite your own service app?
You could
- work with dependencies
- use a delay, since it's a one time thing. Either use a fixed periode, or
detect if the MSDE services you need are started
JAn
"Jacob Schroeder (yaknuts)" <Jacob Schroeder
(yaknuts)@.discussions.microsoft.com> wrote in message
news:603168F6-92B6-4F94-B6DF-F8633B78A0AA@.microsoft.com...
> Well, I wish there was a way I could tell it to not restart the service
after it has already rebooted. The Reboot isn't my main concern, but more
or less after the reboot, the service I just installed with my installshield
package is started, and wants to run the config script, however, MSDE is
still being modfied and the services are restarted again WHILE mine are
accessing it, causing error,
> hopefully you understand my dilemma, as it's really frustrating to me and
there should be a way to get around this...[vbcol=seagreen]
> Thanks,
> Jacob
>
> "Andrea Montanari" wrote:
it's[vbcol=seagreen]
very[vbcol=seagreen]
MDAC if[vbcol=seagreen]
MSDE Install problem
I installed MSDE SP3A with sapwd=abc123 instancename=msde_1. I went to services and started mssql$msde_1 and sqlagent$msde_1. In the system tray, I clicked the sql service manager. I put msde_1 in the server name and hit refresh services, but I get an error stating "The Network Path was not found".
Can someone give me a clue as to what I am doing wrong?
I'm new to MSDE and would like to use it with MSACCESS Projects.This folder should exist and contain the log file if the MSDE Service actually could start at all: C:\Program Files\Microsoft SQL Server\LOG
Now, if you don't have a service called MSSQL$msde_1, then the installation failed. Please review the installation log file.|||Unistall, the try this option
create a file named "Settings.ini"
[Options]
SAPWD=YourPassword
DISABLENETWORKPROTOCOLS=0
SECURITYMODE=SQL
DATADIR="C:\MSDE"
TARGETDIR="C:\MSDE"
then run this from command promt or create a .bat file
setup.exe /settings Settings.ini /L*v C:/MSDELog.log|||I reinstalled with listed settings and Instancename= MSDE01. I do have a service called MSSQL$MSDE01 which I started. I have also started the service SQLAgent$MSDE01.
The problem I am now getting is on trying to open a new project in MSACCESS. It pops up with a SQL Server logon screen. I have the Trusted Connection checked, and nothing appears in the Server Name dropdown list box. I have typed both MSSQL$MSDE01 and MSDE01 as the server name, but in both cases I get the following error:
Connection failed:
SQLState:'01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
Connection Failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.|||I don't speak very good english
See the attached image.
Can someone give me a clue as to what I am doing wrong?
I'm new to MSDE and would like to use it with MSACCESS Projects.This folder should exist and contain the log file if the MSDE Service actually could start at all: C:\Program Files\Microsoft SQL Server\LOG
Now, if you don't have a service called MSSQL$msde_1, then the installation failed. Please review the installation log file.|||Unistall, the try this option
create a file named "Settings.ini"
[Options]
SAPWD=YourPassword
DISABLENETWORKPROTOCOLS=0
SECURITYMODE=SQL
DATADIR="C:\MSDE"
TARGETDIR="C:\MSDE"
then run this from command promt or create a .bat file
setup.exe /settings Settings.ini /L*v C:/MSDELog.log|||I reinstalled with listed settings and Instancename= MSDE01. I do have a service called MSSQL$MSDE01 which I started. I have also started the service SQLAgent$MSDE01.
The problem I am now getting is on trying to open a new project in MSACCESS. It pops up with a SQL Server logon screen. I have the Trusted Connection checked, and nothing appears in the Server Name dropdown list box. I have typed both MSSQL$MSDE01 and MSDE01 as the server name, but in both cases I get the following error:
Connection failed:
SQLState:'01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
Connection Failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.|||I don't speak very good english
See the attached image.
Subscribe to:
Posts (Atom)