Hi,
Seen this question posted in several places, but none of the fixes stated
have done the trick. I'm trying to patch several MSDE instances installed by
Sharepoint. Instance names are SHAREPOINT.All three instances are installed
on W2k3 Servers. When I run the install from the cmd prompt, I use:
<install Dir>\setup /upgradesp sqlrun INSTANCENAME=SHAREPOINT /L*v
c:\MSDELog.log
I have also tried
<install Dir>\setup /upgradesp sqlrun INSTANCENAME=SHAREPOINT
DISABLENETWORKPROTOCOLS=0 /L*v c:\MSDELog.log
Same thing happens. I get an errors that states:"The instance name specified
is invalid". I know this to be untrue - I can query the databases in it
using SQL Client tools (Query analyser)
I've checked out the install package that was used in the registry(
HKEY_CLASSES_ROOT\Installer\Products\95C756568A324 7948B0EAB40BE0DE4F4\SourceList)
which suggests SQLRUN16.msi was used for the install. As this is the case,
all the documentation says I can use SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE
for the installation. However, it still fails.
I have also had to install SP4 onto several instances created by the MS CRM
Outlook client. To do this I have used the following cmd in the cmd prompt:
<install Dir>\setup /upgradesp sqlrun INSTANCENAME=CRM /L*v c:\MSDELog.log
This works perfectly.However, I cannot do this on any of my SHAREPOINT
Instances.
Can anyone assist please?
Many Thanks
John
hi John,
John wrote:
> Hi,
> Seen this question posted in several places, but none of the fixes
> stated have done the trick. I'm trying to patch several MSDE
> instances installed by Sharepoint. Instance names are SHAREPOINT.All
> three instances are installed on W2k3 Servers. When I run the install
> from the cmd prompt, I use:
from the sp4 readme file,
"MSDE 2000 SP4 updates instances of SQL Server 2000 MSDE 2000 and MSDE 2000
Release A. "
Share Point installs a different version of MSDE, known as WMSDE where some
intrinsic MSDE limits has been removed (2gb data file per database) in order
to fullfill Share Point needs and requirements...
so, in my understanding, I think you have to get the new WMSDE package to
upgrade your Share Point instances...
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
|||Hi Andrea
First of all, many thanks for the reply. Could you post a URL to where I can
download the new WMSDE Patch? I've searched, but all I could find was a
Critical Update and a service pack for Sharepoint. Do I need to install the
who service pack? I thought I had already done that, and my SMS 2003 is not
telling me that the Service Pack is required, only the msde instance
requires updating
Many Thanks
Regards,
John
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3h8f6oFfh31iU1@.individual.net...
> hi John,
> John wrote:
> from the sp4 readme file,
> "MSDE 2000 SP4 updates instances of SQL Server 2000 MSDE 2000 and MSDE
> 2000 Release A. "
> Share Point installs a different version of MSDE, known as WMSDE where
> some intrinsic MSDE limits has been removed (2gb data file per database)
> in order to fullfill Share Point needs and requirements...
> so, in my understanding, I think you have to get the new WMSDE package to
> upgrade your Share Point instances...
> --
> 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
>
|||hi John,
John wrote:
> Hi Andrea
> First of all, many thanks for the reply. Could you post a URL to
> where I can download the new WMSDE Patch? I've searched, but all I
> could find was a Critical Update and a service pack for Sharepoint.
> Do I need to install the who service pack? I thought I had already
> done that, and my SMS 2003 is not telling me that the Service Pack is
> required, only the msde instance requires updating
>
unfortunately I'm not a Share Point guy... have you tried asking in its NG
hyerarchy?
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
|||Hi Andrea. Thanks for all your help, I'll try there.
Regards,
John
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3hb3r4Fg7op9U1@.individual.net...
> hi John,
> John wrote:
> unfortunately I'm not a Share Point guy... have you tried asking in its NG
> hyerarchy?
> --
> 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
>
Showing posts with label instances. Show all posts
Showing posts with label instances. Show all posts
Friday, March 30, 2012
Monday, March 26, 2012
MSDE running on same machine as SQL Sever 2000?
Hi,
I currently have 2 instances of MSDE running on a server to support two
different applications. We have decided to obtain the full SQL 2000 std for
another project. Can SQL Server 2000 run on the same machine as Server MSDE?
Will I need to migrate the existing databases that are currently using MSDE
to SQL Server 2000 once it is installed?
Thanks
You CAN run MSDE and another edition on the same machine.
Hal Berenson, President
PredictableIT, LLC
www.predictableit.com
"Jedi Dave" <Jedi Dave@.discussions.microsoft.com> wrote in message
news:748798E1-F1A2-4F2B-8C81-30CD70B19F68@.microsoft.com...
> Hi,
> I currently have 2 instances of MSDE running on a server to support two
> different applications. We have decided to obtain the full SQL 2000 std
> for
> another project. Can SQL Server 2000 run on the same machine as Server
> MSDE?
> Will I need to migrate the existing databases that are currently using
> MSDE
> to SQL Server 2000 once it is installed?
> Thanks
sql
I currently have 2 instances of MSDE running on a server to support two
different applications. We have decided to obtain the full SQL 2000 std for
another project. Can SQL Server 2000 run on the same machine as Server MSDE?
Will I need to migrate the existing databases that are currently using MSDE
to SQL Server 2000 once it is installed?
Thanks
You CAN run MSDE and another edition on the same machine.
Hal Berenson, President
PredictableIT, LLC
www.predictableit.com
"Jedi Dave" <Jedi Dave@.discussions.microsoft.com> wrote in message
news:748798E1-F1A2-4F2B-8C81-30CD70B19F68@.microsoft.com...
> Hi,
> I currently have 2 instances of MSDE running on a server to support two
> different applications. We have decided to obtain the full SQL 2000 std
> for
> another project. Can SQL Server 2000 run on the same machine as Server
> MSDE?
> Will I need to migrate the existing databases that are currently using
> MSDE
> to SQL Server 2000 once it is installed?
> Thanks
sql
MSDE Replication issue
I am trying merge replication between two instances of MSDE on two
different machines on LAN.
I have setup the snapshot agent . when I try running the agent using
sp_start_job @.job_name='MergeSnapshot'
I get an error message saying job name ('MergeSnapshot') does not exist
I am new to replication and trying this for the first time...
Any help is appreciated.
Hello,
Please check out this article:
http://support.microsoft.com/default...b;en-us;324992
regards,
Henk Steunenberg
<prabhusangeeta@.yahoo.com> wrote in message
news:1133288220.042242.206490@.g44g2000cwa.googlegr oups.com...
>I am trying merge replication between two instances of MSDE on two
> different machines on LAN.
> I have setup the snapshot agent . when I try running the agent using
> sp_start_job @.job_name='MergeSnapshot'
> I get an error message saying job name ('MergeSnapshot') does not exist
> I am new to replication and trying this for the first time...
> Any help is appreciated.
>
different machines on LAN.
I have setup the snapshot agent . when I try running the agent using
sp_start_job @.job_name='MergeSnapshot'
I get an error message saying job name ('MergeSnapshot') does not exist
I am new to replication and trying this for the first time...
Any help is appreciated.
Hello,
Please check out this article:
http://support.microsoft.com/default...b;en-us;324992
regards,
Henk Steunenberg
<prabhusangeeta@.yahoo.com> wrote in message
news:1133288220.042242.206490@.g44g2000cwa.googlegr oups.com...
>I am trying merge replication between two instances of MSDE on two
> different machines on LAN.
> I have setup the snapshot agent . when I try running the agent using
> sp_start_job @.job_name='MergeSnapshot'
> I get an error message saying job name ('MergeSnapshot') does not exist
> I am new to replication and trying this for the first time...
> Any help is appreciated.
>
Monday, March 19, 2012
MSDE multiple instances
Hello there,
I want to install multiple instances of MSDE on XP prof edition. How many
instances can i create on a single machine?
Also, any URL for this would be helpful?
Thanks,
David
hi David,
David wrote:
> Hello there,
> I want to install multiple instances of MSDE on XP prof edition. How
> many instances can i create on a single machine?
> Also, any URL for this would be helpful?
> Thanks,
> David
you can install up to 16 instances per server, but this is a theorical limit
as you will not have enought resources to serve all of them..
each additional running instance will add about 20mb of RAM requirement but
this only is the initial load, as the real load will depend on instance
activity that will end up at the Win32 process limit of addressing up to 2gb
of RAM, and many running instances will of course bring your server down to
knees...
for additional information about SQL Server memory management, please have a
look at excellent Ken Henderson's article at
http://msdn.microsoft.com/library/de...v_03252004.asp
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
I want to install multiple instances of MSDE on XP prof edition. How many
instances can i create on a single machine?
Also, any URL for this would be helpful?
Thanks,
David
hi David,
David wrote:
> Hello there,
> I want to install multiple instances of MSDE on XP prof edition. How
> many instances can i create on a single machine?
> Also, any URL for this would be helpful?
> Thanks,
> David
you can install up to 16 instances per server, but this is a theorical limit
as you will not have enought resources to serve all of them..
each additional running instance will add about 20mb of RAM requirement but
this only is the initial load, as the real load will depend on instance
activity that will end up at the Win32 process limit of addressing up to 2gb
of RAM, and many running instances will of course bring your server down to
knees...
for additional information about SQL Server memory management, please have a
look at excellent Ken Henderson's article at
http://msdn.microsoft.com/library/de...v_03252004.asp
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 Multiple Instance
I am trying to set up multiple instances of MSDE 2000 for use by Trend Micro virus scan products. I have the instance set up but I am trying to access svrnetcn.exe to set up named pipes and TCP/IP and I keep getting a 126 error "The Specified Module could not be found". Any ideas how to set this up.
thanks,
eric
Moving thread to Express/MSDE forum.|||This seems to be a general Windows error that indicates that you are either missing certain DLLs that are required to launch this program. The only information I found on this specific to SQL is at http://www.experts-exchange.com/Databases/Microsoft_SQL_Server/Q_21455359.html. Check that out and see if it sheds light on your situation.
Mike
|||I had this same issue and ended up searching for that 126 error message. I found a somewhat related reference to an older service pack being installed than what it wanted, so maybe SVRNETCN.exe or some of its required files were corrupted. Who knows. Maybe at some point I installed an older version of MSDE over a newer version and broke it. I went to add/remove programs and removed that new Instance of Trend from the system. Then I download the MSDE 2000 SP4 install package and installed that on the system for Trend (setup.exe INSTANCENAME=Trend SAPWD="strongpwd" SECURITYMODE=sql). Once that was on I used OSQL and checked the version of MSDE to verify SP4 was there. Then I ran SVRNETCN.exe with no problems and enabled "Named Pipes" and "TCP/IP". Then I ran the Trend Control Manager install with no errors.
If you need any more specific information than that let me know and I'll dig up links for you. Good luck.
Monday, March 12, 2012
MSDE instances
Is it possible to install MSDE from more than 1 application. 2 different
companies on one server, or is this a restriction.
hi Dave,
"Dave" <Dave@.discussions.microsoft.com> ha scritto nel messaggio
news:06823492-068B-4B58-A6AA-F99E78C9C9B9@.microsoft.com
> Is it possible to install MSDE from more than 1 application. 2
> different companies on one server, or is this a restriction.
SQL Server 2000 (and thus MSDE 2000) change the initial SQL Server situation
where 1 server allowed only 1 installed instance
now it is possible to install up to 16 instances per server, at different
service pack level..
only 1 instance can be the default instance, known as "ComputerName" or
"(Local)", while other instances become named instaces, known as
"ComputerName\InstanceName" or "(Local)\InstanceName"
in order the clients to connect to MSDE 2000 MDAC 2.6 stack must be
installed whith, among other "things", provides the necessary code to
perform redirection to the appropriate instance port... this is performed
serverside by SQL Server Resolution Service, which operates on UDP port
1434, that returns the appropriate network endpoints to use for a particular
SQL Server/MSDE instance.
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||"Andrea Montanari" wrote:
> hi Dave,
> "Dave" <Dave@.discussions.microsoft.com> ha scritto nel messaggio
> news:06823492-068B-4B58-A6AA-F99E78C9C9B9@.microsoft.com
> SQL Server 2000 (and thus MSDE 2000) change the initial SQL Server situation
> where 1 server allowed only 1 installed instance
> now it is possible to install up to 16 instances per server, at different
> service pack level..
> only 1 instance can be the default instance, known as "ComputerName" or
> "(Local)", while other instances become named instaces, known as
> "ComputerName\InstanceName" or "(Local)\InstanceName"
> in order the clients to connect to MSDE 2000 MDAC 2.6 stack must be
> installed whith, among other "things", provides the necessary code to
> perform redirection to the appropriate instance port... this is performed
> serverside by SQL Server Resolution Service, which operates on UDP port
> 1434, that returns the appropriate network endpoints to use for a particular
> SQL Server/MSDE instance.
Andrea
They have given me a command line to invoke which they say will install the
new instance. I'm concerned about overwriting the initial instance which I
believe is also a named instance. The command line they gave me was with
their disc inserted in E drive EXE /I E:\SETUP\MSDE\SQLRUN01.MSI /Q
TARGETDIR="C:\PROGRAM FILES\NETWORK ASSOCIATES\EPO\"
COLLATION=SQL_LATIN1_GENERAL_CP1_CI_AS SAPWD=<PASSWORD> REBOOT=R
I have one instance already. Is this going to overwrite it?
Thanks,
Dave
|||Dave wrote:
> "Andrea Montanari" wrote:
>
> Andrea
> They have given me a command line to invoke which they say will install the
> new instance. I'm concerned about overwriting the initial instance which I
> believe is also a named instance. The command line they gave me was with
> their disc inserted in E drive EXE /I E:\SETUP\MSDE\SQLRUN01.MSI /Q
> TARGETDIR="C:\PROGRAM FILES\NETWORK ASSOCIATES\EPO\"
> COLLATION=SQL_LATIN1_GENERAL_CP1_CI_AS SAPWD=<PASSWORD> REBOOT=R
> I have one instance already. Is this going to overwrite it?
>
Hi Dave,
AFAIK only one default instance is allowed to exist - all other
instances must be named instances.
there's an command line parameter for specifying the instance:
INSTANCENAME="name"
you'll also have to adjust the instance name in the application
which is going to access the sql server.
HTH,
Gerald
|||Hi Gerald,
Yes, that's true and that's why you should specify a unique instance name
for your application. It will avoid it "colliding" with other apps trying to
use the default instance.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Gerald Aichholzer" <gary@.sbox.tugraz.at> wrote in message
news:41c92c88$1@.e-post.inode.at...
> Dave wrote:
> Hi Dave,
> AFAIK only one default instance is allowed to exist - all other
> instances must be named instances.
> there's an command line parameter for specifying the instance:
> INSTANCENAME="name"
> you'll also have to adjust the instance name in the application
> which is going to access the sql server.
> HTH,
> Gerald
>
companies on one server, or is this a restriction.
hi Dave,
"Dave" <Dave@.discussions.microsoft.com> ha scritto nel messaggio
news:06823492-068B-4B58-A6AA-F99E78C9C9B9@.microsoft.com
> Is it possible to install MSDE from more than 1 application. 2
> different companies on one server, or is this a restriction.
SQL Server 2000 (and thus MSDE 2000) change the initial SQL Server situation
where 1 server allowed only 1 installed instance
now it is possible to install up to 16 instances per server, at different
service pack level..
only 1 instance can be the default instance, known as "ComputerName" or
"(Local)", while other instances become named instaces, known as
"ComputerName\InstanceName" or "(Local)\InstanceName"
in order the clients to connect to MSDE 2000 MDAC 2.6 stack must be
installed whith, among other "things", provides the necessary code to
perform redirection to the appropriate instance port... this is performed
serverside by SQL Server Resolution Service, which operates on UDP port
1434, that returns the appropriate network endpoints to use for a particular
SQL Server/MSDE instance.
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||"Andrea Montanari" wrote:
> hi Dave,
> "Dave" <Dave@.discussions.microsoft.com> ha scritto nel messaggio
> news:06823492-068B-4B58-A6AA-F99E78C9C9B9@.microsoft.com
> SQL Server 2000 (and thus MSDE 2000) change the initial SQL Server situation
> where 1 server allowed only 1 installed instance
> now it is possible to install up to 16 instances per server, at different
> service pack level..
> only 1 instance can be the default instance, known as "ComputerName" or
> "(Local)", while other instances become named instaces, known as
> "ComputerName\InstanceName" or "(Local)\InstanceName"
> in order the clients to connect to MSDE 2000 MDAC 2.6 stack must be
> installed whith, among other "things", provides the necessary code to
> perform redirection to the appropriate instance port... this is performed
> serverside by SQL Server Resolution Service, which operates on UDP port
> 1434, that returns the appropriate network endpoints to use for a particular
> SQL Server/MSDE instance.
Andrea
They have given me a command line to invoke which they say will install the
new instance. I'm concerned about overwriting the initial instance which I
believe is also a named instance. The command line they gave me was with
their disc inserted in E drive EXE /I E:\SETUP\MSDE\SQLRUN01.MSI /Q
TARGETDIR="C:\PROGRAM FILES\NETWORK ASSOCIATES\EPO\"
COLLATION=SQL_LATIN1_GENERAL_CP1_CI_AS SAPWD=<PASSWORD> REBOOT=R
I have one instance already. Is this going to overwrite it?
Thanks,
Dave
|||Dave wrote:
> "Andrea Montanari" wrote:
>
> Andrea
> They have given me a command line to invoke which they say will install the
> new instance. I'm concerned about overwriting the initial instance which I
> believe is also a named instance. The command line they gave me was with
> their disc inserted in E drive EXE /I E:\SETUP\MSDE\SQLRUN01.MSI /Q
> TARGETDIR="C:\PROGRAM FILES\NETWORK ASSOCIATES\EPO\"
> COLLATION=SQL_LATIN1_GENERAL_CP1_CI_AS SAPWD=<PASSWORD> REBOOT=R
> I have one instance already. Is this going to overwrite it?
>
Hi Dave,
AFAIK only one default instance is allowed to exist - all other
instances must be named instances.
there's an command line parameter for specifying the instance:
INSTANCENAME="name"
you'll also have to adjust the instance name in the application
which is going to access the sql server.
HTH,
Gerald
|||Hi Gerald,
Yes, that's true and that's why you should specify a unique instance name
for your application. It will avoid it "colliding" with other apps trying to
use the default instance.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Gerald Aichholzer" <gary@.sbox.tugraz.at> wrote in message
news:41c92c88$1@.e-post.inode.at...
> Dave wrote:
> Hi Dave,
> AFAIK only one default instance is allowed to exist - all other
> instances must be named instances.
> there's an command line parameter for specifying the instance:
> INSTANCENAME="name"
> you'll also have to adjust the instance name in the application
> which is going to access the sql server.
> HTH,
> Gerald
>
MSDE Instances
Hello everyone. After finally getting MSDE installed, I
am having trouble with instances. At bootup the instance
that is loading is the wrong one, and is not working. The
instance that is loading is just "computername," and I
need "computername\instance" to load. I have checked the
registry for the other instance and it is not there. The
only place I can find this instance is when I open the SQL
Server Service Manager and click the drop down menu for
server. When I select the "computername\instance" from
the drop down menu everything works fine, it is just
initially it loads a defective instance. Anyone have any
ideas?
Thanks,
Chris
hi Chris,
"Chris" <ckujawa@.kcpag.com> ha scritto nel messaggio
news:010701c4ac9d$fa3d49a0$a501280a@.phx.gbl
> Hello everyone. After finally getting MSDE installed, I
> am having trouble with instances. At bootup the instance
> that is loading is the wrong one, and is not working. The
> instance that is loading is just "computername," and I
> need "computername\instance" to load. I have checked the
> registry for the other instance and it is not there. The
> only place I can find this instance is when I open the SQL
> Server Service Manager and click the drop down menu for
> server. When I select the "computername\instance" from
> the drop down menu everything works fine, it is just
> initially it loads a defective instance. Anyone have any
> ideas?
Just a question... to understand...
you do have 2 MSDE instances installed...
a default instance and a named instance... please verify that both (or the
instance you are interestd in) services are set to start at bootstrap,
inspecting the Windows services manager (control panel->administrative
tools->services).. startup has to be "Automatic"...
why the default instance is not working?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi, and thank you for the reply. Sorry that I did not
make this more clear to begin with. No, I do not have two
instances installed, and I don't want two instances
installed. I guess somewhere in the middle of all the
trouble I had installing MSDE it created some kind of
bogus instance. All the readings I have read say that a
default instance in the registry will be located under
MSSQL Server and a named instance will be under Microsoft
SQL Server. I have deleted the MSSQL Server key and then
everything works fine until I reboot, then the key is re-
created. I can log off and back on after the key is
deleted and it works like it is supposed to.
When I open SVRNETCN.exe it says that I have two instances
installed:
1.) computername
2.) computername\instancename
I cannot find a way to get rid of "computername" and that
is the way that it is loading by default.
Let me know if you need more info and I hope I made it a
little more clear.
Thanks,
Chris[vbcol=seagreen]
>--Original Message--
>hi Chris,
>"Chris" <ckujawa@.kcpag.com> ha scritto nel messaggio
>news:010701c4ac9d$fa3d49a0$a501280a@.phx.gbl
instance[vbcol=seagreen]
The[vbcol=seagreen]
the[vbcol=seagreen]
The[vbcol=seagreen]
SQL[vbcol=seagreen]
any
>Just a question... to understand...
>you do have 2 MSDE instances installed...
>a default instance and a named instance... please verify
that both (or the
>instance you are interestd in) services are set to start
at bootstrap,
>inspecting the Windows services manager (control panel-
>administrative
>tools->services).. startup has to be "Automatic"...
>why the default instance is not working?
>--
>Andrea Montanari (Microsoft MVP - SQL Server)
>http://www.asql.biz/DbaMgr.shtm
http://italy.mvps.org
>DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
>(my vb6+sql-dmo little try to provide MS MSDE 1.0 and
MSDE 2000 a visual
>interface)
>-- remove DMO to reply
>.
>
|||hi Chris,
"Chris" <ckujawa@.kcpag.com> ha scritto nel messaggio
news:089801c4ad48$ccdfdc10$a501280a@.phx.gbl
> Hi, and thank you for the reply. Sorry that I did not
> make this more clear to begin with. No, I do not have two
> instances installed, and I don't want two instances
> installed. I guess somewhere in the middle of all the
> trouble I had installing MSDE it created some kind of
> bogus instance. All the readings I have read say that a
> default instance in the registry will be located under
> MSSQL Server and a named instance will be under Microsoft
> SQL Server. I have deleted the MSSQL Server key and then
> everything works fine until I reboot, then the key is re-
> created. I can log off and back on after the key is
> deleted and it works like it is supposed to.
> When I open SVRNETCN.exe it says that I have two instances
> installed:
> 1.) computername
> 2.) computername\instancename
> I cannot find a way to get rid of "computername" and that
> is the way that it is loading by default.
> Let me know if you need more info and I hope I made it a
> little more clear.
>
ok... you do have 2 MSDE instances installed =;-D
a default instance, and a named instance named "instancename"...
and both of them shoul'd run at startup as this is the default setting
(please verify checking the services management tool)
and please do not delete registy keys that easy, becouse, as someone
elsewhere stated:
>"And by the way, editing the registry is extremely dangerous and I'm not
>responsible if you make a mistake and your hair is sure to fall out and you
>will catch pneumonia blah blah blah..." =:-)
so SQL Server Service Manager should list both instances, and both should be
running...
if you want to remove an MSDE instance, you should find an entry in the
Add/Remove programs applet, and please use that...
if you want to "manually" remove an MSDE instance,
http://support.microsoft.com/default...;EN-US;Q290991 Knowledge
Base article explains exactely the tasks to be performed as
http://support.microsoft.com/default...b;en-us;320873 does...
the second article uses a tool from the Platform SDK, Msizap.exe, which can
clear the Windows Installer entries too...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
am having trouble with instances. At bootup the instance
that is loading is the wrong one, and is not working. The
instance that is loading is just "computername," and I
need "computername\instance" to load. I have checked the
registry for the other instance and it is not there. The
only place I can find this instance is when I open the SQL
Server Service Manager and click the drop down menu for
server. When I select the "computername\instance" from
the drop down menu everything works fine, it is just
initially it loads a defective instance. Anyone have any
ideas?
Thanks,
Chris
hi Chris,
"Chris" <ckujawa@.kcpag.com> ha scritto nel messaggio
news:010701c4ac9d$fa3d49a0$a501280a@.phx.gbl
> Hello everyone. After finally getting MSDE installed, I
> am having trouble with instances. At bootup the instance
> that is loading is the wrong one, and is not working. The
> instance that is loading is just "computername," and I
> need "computername\instance" to load. I have checked the
> registry for the other instance and it is not there. The
> only place I can find this instance is when I open the SQL
> Server Service Manager and click the drop down menu for
> server. When I select the "computername\instance" from
> the drop down menu everything works fine, it is just
> initially it loads a defective instance. Anyone have any
> ideas?
Just a question... to understand...
you do have 2 MSDE instances installed...
a default instance and a named instance... please verify that both (or the
instance you are interestd in) services are set to start at bootstrap,
inspecting the Windows services manager (control panel->administrative
tools->services).. startup has to be "Automatic"...
why the default instance is not working?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi, and thank you for the reply. Sorry that I did not
make this more clear to begin with. No, I do not have two
instances installed, and I don't want two instances
installed. I guess somewhere in the middle of all the
trouble I had installing MSDE it created some kind of
bogus instance. All the readings I have read say that a
default instance in the registry will be located under
MSSQL Server and a named instance will be under Microsoft
SQL Server. I have deleted the MSSQL Server key and then
everything works fine until I reboot, then the key is re-
created. I can log off and back on after the key is
deleted and it works like it is supposed to.
When I open SVRNETCN.exe it says that I have two instances
installed:
1.) computername
2.) computername\instancename
I cannot find a way to get rid of "computername" and that
is the way that it is loading by default.
Let me know if you need more info and I hope I made it a
little more clear.
Thanks,
Chris[vbcol=seagreen]
>--Original Message--
>hi Chris,
>"Chris" <ckujawa@.kcpag.com> ha scritto nel messaggio
>news:010701c4ac9d$fa3d49a0$a501280a@.phx.gbl
instance[vbcol=seagreen]
The[vbcol=seagreen]
the[vbcol=seagreen]
The[vbcol=seagreen]
SQL[vbcol=seagreen]
any
>Just a question... to understand...
>you do have 2 MSDE instances installed...
>a default instance and a named instance... please verify
that both (or the
>instance you are interestd in) services are set to start
at bootstrap,
>inspecting the Windows services manager (control panel-
>administrative
>tools->services).. startup has to be "Automatic"...
>why the default instance is not working?
>--
>Andrea Montanari (Microsoft MVP - SQL Server)
>http://www.asql.biz/DbaMgr.shtm
http://italy.mvps.org
>DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
>(my vb6+sql-dmo little try to provide MS MSDE 1.0 and
MSDE 2000 a visual
>interface)
>-- remove DMO to reply
>.
>
|||hi Chris,
"Chris" <ckujawa@.kcpag.com> ha scritto nel messaggio
news:089801c4ad48$ccdfdc10$a501280a@.phx.gbl
> Hi, and thank you for the reply. Sorry that I did not
> make this more clear to begin with. No, I do not have two
> instances installed, and I don't want two instances
> installed. I guess somewhere in the middle of all the
> trouble I had installing MSDE it created some kind of
> bogus instance. All the readings I have read say that a
> default instance in the registry will be located under
> MSSQL Server and a named instance will be under Microsoft
> SQL Server. I have deleted the MSSQL Server key and then
> everything works fine until I reboot, then the key is re-
> created. I can log off and back on after the key is
> deleted and it works like it is supposed to.
> When I open SVRNETCN.exe it says that I have two instances
> installed:
> 1.) computername
> 2.) computername\instancename
> I cannot find a way to get rid of "computername" and that
> is the way that it is loading by default.
> Let me know if you need more info and I hope I made it a
> little more clear.
>
ok... you do have 2 MSDE instances installed =;-D
a default instance, and a named instance named "instancename"...
and both of them shoul'd run at startup as this is the default setting
(please verify checking the services management tool)
and please do not delete registy keys that easy, becouse, as someone
elsewhere stated:
>"And by the way, editing the registry is extremely dangerous and I'm not
>responsible if you make a mistake and your hair is sure to fall out and you
>will catch pneumonia blah blah blah..." =:-)
so SQL Server Service Manager should list both instances, and both should be
running...
if you want to remove an MSDE instance, you should find an entry in the
Add/Remove programs applet, and please use that...
if you want to "manually" remove an MSDE instance,
http://support.microsoft.com/default...;EN-US;Q290991 Knowledge
Base article explains exactely the tasks to be performed as
http://support.microsoft.com/default...b;en-us;320873 does...
the second article uses a tool from the Platform SDK, Msizap.exe, which can
clear the Windows Installer entries too...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Friday, March 9, 2012
MSDE instance registration in Enterprise Manager
Hi All,
I'm trying to register an instance of MSDE on a remote machine using EM on my desktop. The remote machine has 2
named instances of MSDE running. I am able to register 1 instance with no problems. I had to register it using
"RemoteServer1\InstanceName" rather than just the remote machines name.
For the life of me I can not get the other instance to register. I get the "SQL Server does not exist or access
denied" error. I've tried just registering the 2nd instance without the first with the same results. I can see
no difference in the way either of the 2 instances were set up or in their properties. I am a machine admin on
the remote machine and am connecting using Windows Auth.
What am I missing and how can I register that 2nd instance?
Thank you.
gdr
Gary D. Rezek
University Networking Systems and Services
South Dakota State University
hi Gary,
Gary D. Rezek wrote:
> Hi All,
> I'm trying to register an instance of MSDE on a remote machine using
> EM on my desktop. The remote machine has 2 named instances of MSDE
> running. I am able to register 1 instance with no problems. I had to
> register it using "RemoteServer1\InstanceName" rather than just the
> remote machines name.
this is normal as a named instance full qualified name is
ComputerName\InstanceName...
> For the life of me I can not get the other instance to register. I
> get the "SQL Server does not exist or access denied" error. I've
> tried just registering the 2nd instance without the first with the
> same results. I can see no difference in the way either of the 2
> instances were set up or in their properties. I am a machine admin on
> the remote machine and am connecting using Windows Auth. What am I
> missing and how can I register that 2nd instance?
at least 1 difference must be present... the name... MSDE/SQL Server 2000
can be installed as a default instance or a named instance... but only a
default instance can be present, wit up to other 15 named instances per
computer...
as you already saw, a default instance is available as ComputerName, where a
named instance will be as ComputerName\InstanceName...
you can inspect your (remote) services for MSSQLSERVER and
MSSQL$InstanceName to see what is going on...
MSDE installs by default disabling network protocols, thus not allowing
remote connections... please verify using the Server Network Utiliy
(svrnetcn.exe) that the "failing" instance has enabled network protocols...
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
|||Hi Andrea,
Thanks for your answer. It eventually led me to http://tinyurl.com/8q95s this post. In that post I found this
quote...
"You need to look for a line in the error log which states:
"SQL server listening on TCP, Shared Memory, Named Pipes.
"If you only have Shared Memory on this list, then only local connections are allowed."
In the instance I have been trying to connect, Shared Memory is the only thing listed in the errorlog, so no
TCP/IP or Named Pipes. I asked the individual who is responsible for the application which created this instance
of MSDE (and also the one who asked me WHY can't he connect through EM), I learned that this is the way it
should be. :^/ I've worked with MSDE very, very little, but I still should have looked at the ErrorLog to
begin with.
Thank you very much for your help
gdr
Gary D. Rezek
University Networking Systems and Services
South Dakota State University
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message news:3jg2rjFpnmhnU1@.individual.net...
> hi Gary,
> Gary D. Rezek wrote:
> this is normal as a named instance full qualified name is ComputerName\InstanceName...
>
> at least 1 difference must be present... the name... MSDE/SQL Server 2000 can be installed as a default
> instance or a named instance... but only a default instance can be present, wit up to other 15 named instances
> per computer...
> as you already saw, a default instance is available as ComputerName, where a named instance will be as
> ComputerName\InstanceName...
> you can inspect your (remote) services for MSSQLSERVER and MSSQL$InstanceName to see what is going on...
> MSDE installs by default disabling network protocols, thus not allowing remote connections... please verify
> using the Server Network Utiliy (svrnetcn.exe) that the "failing" instance has enabled network protocols...
> --
> 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
>
|||h Gary,
Gary D. Rezek wrote:
> Hi Andrea,
> Thanks for your answer. It eventually led me to
> http://tinyurl.com/8q95s this post. In that post I found this quote...
> "You need to look for a line in the error log which states:
> "SQL server listening on TCP, Shared Memory, Named Pipes.
> "If you only have Shared Memory on this list, then only local
> connections are allowed."
you always have to verify (on the server using Server Network Utility
[svrnetcn.exe] and on the client using Client Network Utility
[cliconfg.exe]) that a common network protocol is available for the client
and the server to dialog...
> In the instance I have been trying to connect, Shared Memory is the
> only thing listed in the errorlog, so no TCP/IP or Named Pipes. I
> asked the individual who is responsible for the application which
> created this instance of MSDE (and also the one who asked me WHY
> can't he connect through EM), I learned that this is the way it
> should be. :^/
if Shared Memory is the only protocol that "must" be enabled, then no remote
connections will be available... but it can be ok in local scenarios
..
MSDE will then actually be used as a local desktop database..
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
I'm trying to register an instance of MSDE on a remote machine using EM on my desktop. The remote machine has 2
named instances of MSDE running. I am able to register 1 instance with no problems. I had to register it using
"RemoteServer1\InstanceName" rather than just the remote machines name.
For the life of me I can not get the other instance to register. I get the "SQL Server does not exist or access
denied" error. I've tried just registering the 2nd instance without the first with the same results. I can see
no difference in the way either of the 2 instances were set up or in their properties. I am a machine admin on
the remote machine and am connecting using Windows Auth.
What am I missing and how can I register that 2nd instance?
Thank you.
gdr
Gary D. Rezek
University Networking Systems and Services
South Dakota State University
hi Gary,
Gary D. Rezek wrote:
> Hi All,
> I'm trying to register an instance of MSDE on a remote machine using
> EM on my desktop. The remote machine has 2 named instances of MSDE
> running. I am able to register 1 instance with no problems. I had to
> register it using "RemoteServer1\InstanceName" rather than just the
> remote machines name.
this is normal as a named instance full qualified name is
ComputerName\InstanceName...
> For the life of me I can not get the other instance to register. I
> get the "SQL Server does not exist or access denied" error. I've
> tried just registering the 2nd instance without the first with the
> same results. I can see no difference in the way either of the 2
> instances were set up or in their properties. I am a machine admin on
> the remote machine and am connecting using Windows Auth. What am I
> missing and how can I register that 2nd instance?
at least 1 difference must be present... the name... MSDE/SQL Server 2000
can be installed as a default instance or a named instance... but only a
default instance can be present, wit up to other 15 named instances per
computer...
as you already saw, a default instance is available as ComputerName, where a
named instance will be as ComputerName\InstanceName...
you can inspect your (remote) services for MSSQLSERVER and
MSSQL$InstanceName to see what is going on...
MSDE installs by default disabling network protocols, thus not allowing
remote connections... please verify using the Server Network Utiliy
(svrnetcn.exe) that the "failing" instance has enabled network protocols...
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
|||Hi Andrea,
Thanks for your answer. It eventually led me to http://tinyurl.com/8q95s this post. In that post I found this
quote...
"You need to look for a line in the error log which states:
"SQL server listening on TCP, Shared Memory, Named Pipes.
"If you only have Shared Memory on this list, then only local connections are allowed."
In the instance I have been trying to connect, Shared Memory is the only thing listed in the errorlog, so no
TCP/IP or Named Pipes. I asked the individual who is responsible for the application which created this instance
of MSDE (and also the one who asked me WHY can't he connect through EM), I learned that this is the way it
should be. :^/ I've worked with MSDE very, very little, but I still should have looked at the ErrorLog to
begin with.
Thank you very much for your help
gdr
Gary D. Rezek
University Networking Systems and Services
South Dakota State University
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message news:3jg2rjFpnmhnU1@.individual.net...
> hi Gary,
> Gary D. Rezek wrote:
> this is normal as a named instance full qualified name is ComputerName\InstanceName...
>
> at least 1 difference must be present... the name... MSDE/SQL Server 2000 can be installed as a default
> instance or a named instance... but only a default instance can be present, wit up to other 15 named instances
> per computer...
> as you already saw, a default instance is available as ComputerName, where a named instance will be as
> ComputerName\InstanceName...
> you can inspect your (remote) services for MSSQLSERVER and MSSQL$InstanceName to see what is going on...
> MSDE installs by default disabling network protocols, thus not allowing remote connections... please verify
> using the Server Network Utiliy (svrnetcn.exe) that the "failing" instance has enabled network protocols...
> --
> 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
>
|||h Gary,
Gary D. Rezek wrote:
> Hi Andrea,
> Thanks for your answer. It eventually led me to
> http://tinyurl.com/8q95s this post. In that post I found this quote...
> "You need to look for a line in the error log which states:
> "SQL server listening on TCP, Shared Memory, Named Pipes.
> "If you only have Shared Memory on this list, then only local
> connections are allowed."
you always have to verify (on the server using Server Network Utility
[svrnetcn.exe] and on the client using Client Network Utility
[cliconfg.exe]) that a common network protocol is available for the client
and the server to dialog...
> In the instance I have been trying to connect, Shared Memory is the
> only thing listed in the errorlog, so no TCP/IP or Named Pipes. I
> asked the individual who is responsible for the application which
> created this instance of MSDE (and also the one who asked me WHY
> can't he connect through EM), I learned that this is the way it
> should be. :^/
if Shared Memory is the only protocol that "must" be enabled, then no remote
connections will be available... but it can be ok in local scenarios
..MSDE will then actually be used as a local desktop database..
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
Subscribe to:
Posts (Atom)