I have multiple applications that will use the same named instance of MSDE. When I try to setup my second application using the MSDE Deployment addin it thinks that MSDE needs to be installed again. According to the flowchart it should bypass this and
just install my appliation. Any suggestions as to why my setup insists in needs to install another instance? My instance name is the same for all applications.
Thanks,
Bill
Bill in one of the previous messages someone from Microsoft mentioned that it is a known bug in the beta version of the toolkit. Hopefully it will be fixed.
goodluck
dev
|||Thanks for the info. Does anyone know when the full release will be out?
sql
Showing posts with label named. Show all posts
Showing posts with label named. Show all posts
Friday, March 30, 2012
Wednesday, March 21, 2012
MSDE or VS.NET Problem
I recently installed a named MSDE instance and created a DB with SQLDMO. I can see the instance in VS.NET, but can't see the tables that SQLDMO created. When I rerun the script to create the tables, I get a SQL Server ODBC driver error saying the tables already exist. I have tried restarting the machine and the services, but still can't see the tables in VS.NET. The other strange thing is I also can't load data into the tables because SQLDMO says my tables are not in the Tables collection. I didn't get any errors when I originally ran the script that created my tables. When I checked the SQL log, I didn't see any errors, but also didn't see anything indicating the tables were created. Would SQL Server have logged this?
Please copy an replies to pearsonbe@.aol.com.Can you check if the SQLDMO statements used the same login as you are using to view the contents of the database? Do you use the correct name for the tables (server.database.owner.tablename)?|||Yes, I'm using the same login info in the code w/SQLDMO as well as when connecting in Visual Studio. For some reason, the ExecuteImmediate does not work with the DB script that was produced by my SQLDMO DB object. I was able to create a new table in VS and then delete it with SQLDMO, so my current workaround is to just deatch the original DB and reattach to the new DB.
Thanks.
Please copy an replies to pearsonbe@.aol.com.Can you check if the SQLDMO statements used the same login as you are using to view the contents of the database? Do you use the correct name for the tables (server.database.owner.tablename)?|||Yes, I'm using the same login info in the code w/SQLDMO as well as when connecting in Visual Studio. For some reason, the ExecuteImmediate does not work with the DB script that was produced by my SQLDMO DB object. I was able to create a new table in VS and then delete it with SQLDMO, so my current workaround is to just deatch the original DB and reattach to the new DB.
Thanks.
MSDE on machine with SQL Server
Hello,
A named instance of MSDE will be installed on our clients machines along with our VB.Net during the installation. Will this work fine even if the client already has SQL Server on his/her machine. I mean will the installation of named instance of MSDE wor
k smoothly even if SQL Server already exists. If yes, then does that apply for both SQL Server 7 & 2000. If no, then what should I do.
Thanks
dev
You should have no problems, as long as you are installing a uniquely named
instance. This is true even if SQL Server 7 is already installed on the
system.
Jim
"dev" <anonymous@.discussions.microsoft.com> wrote in message
news:B46C4961-748E-47E1-AD22-2A712100428F@.microsoft.com...
> Hello,
> A named instance of MSDE will be installed on our clients machines along
with our VB.Net during the installation. Will this work fine even if the
client already has SQL Server on his/her machine. I mean will the
installation of named instance of MSDE work smoothly even if SQL Server
already exists. If yes, then does that apply for both SQL Server 7 & 2000.
If no, then what should I do.
> Thanks
> dev
sql
A named instance of MSDE will be installed on our clients machines along with our VB.Net during the installation. Will this work fine even if the client already has SQL Server on his/her machine. I mean will the installation of named instance of MSDE wor
k smoothly even if SQL Server already exists. If yes, then does that apply for both SQL Server 7 & 2000. If no, then what should I do.
Thanks
dev
You should have no problems, as long as you are installing a uniquely named
instance. This is true even if SQL Server 7 is already installed on the
system.
Jim
"dev" <anonymous@.discussions.microsoft.com> wrote in message
news:B46C4961-748E-47E1-AD22-2A712100428F@.microsoft.com...
> Hello,
> A named instance of MSDE will be installed on our clients machines along
with our VB.Net during the installation. Will this work fine even if the
client already has SQL Server on his/her machine. I mean will the
installation of named instance of MSDE work smoothly even if SQL Server
already exists. If yes, then does that apply for both SQL Server 7 & 2000.
If no, then what should I do.
> Thanks
> dev
sql
Monday, March 19, 2012
MSDE no show in server explorer
I have installed default instance of SQLServer 2005 DE on Windows Server 2003 host. I also installed a named instance of MSDE rel A. I can connect to the MSDE instance from Management Studio but it does not appear in the list of servers when I try to add the connection in VS2005 server explorer. What am I doing wrong?
- Dick
Anybody?
I can connect to the named MSDE instance (now upgraded to SP4) with management studio and osql, but it does not appear in the server list in VS2005 studio explorer, or in the OS ODBC DataSources utility.
The log shows the MSDE instance is listening on shared memory. I cannot configure it for named pipes because I can only see the default SS2K5 instance in SQL Server Configuration Manager.
All contributions massively appreciated.
|||
MSDE instances listening only on shared memory generally do not show up in the list boxes you mention.
You can configure the MSDE to listen on named pipes (or TCP) through the Server Network Utility.
|||Thanks Peter
That cracked it. Here's what I did:
- I ran Microsoft SQL Server\80\Tools\binn\SVRNETCN.exe and enabled Named Pipes and TCP/IP
- restarted the server instance but it did not fix it.
- rebooted the machine, got various system errors e.g. reporting services could not connect to db. There was a conflict on port 1433.
- re-ran Server Network Configuration utility, set TCP/IP port to 0. (Bit confused by this, I thought MSDE sp 3 sorted out port sharing issue ...? I havn't tried a remote connection yet)
- Ran SQL Configuration Manager and created np aliases for both the default and named instances.
- rebooted and everything fixed. Able to create a System DSN. MSDE instance did not appear in server list when I tried to add a new a connection in VS2005 server explorer, but I was able to type in the server name and connect ok.
As a general observation I have to say I am not a member of SQL Server 2005 fan club yet. It promises simplicity, but delivers frustration.
MSDE names instance as Replication publisher?
I'm trying to setup a named instance of MSDE on my local machine, as a
Replication Publisher and I always get an error. My named instance is called
"MSDE"
Error 18483: Could not connect to server 'mymachine\msde' because
'distributor_admin' is not defined as a remote login at the server.
The only remote thing I can find on the MS support site is:
http://support.microsoft.com/default...;en-us;Q324992
but that really didn't help, since it was talking about IP addresses and not
named instances of MSDE.
Can anyone help me get this resolved?
FYI... i also found this article:
http://support.microsoft.com/default...b;en-us;818334
which talks about server names... when I look at the @.@.ServerName variable,
it returns my hostname and instance name: CORPDALL140451\MSDE
is that the problem? I already have a SQL Server instance with no name
running on my machine, but I must have this MSDE instance be the replication
publisher.
"Derick Bailey" <DerickBailey@.srcp.com> wrote in message
news:eR7q4xUtEHA.3788@.TK2MSFTNGP09.phx.gbl...
> I'm trying to setup a named instance of MSDE on my local machine, as a
> Replication Publisher and I always get an error. My named instance is
> called "MSDE"
> Error 18483: Could not connect to server 'mymachine\msde' because
> 'distributor_admin' is not defined as a remote login at the server.
> The only remote thing I can find on the MS support site is:
> http://support.microsoft.com/default...;en-us;Q324992
> but that really didn't help, since it was talking about IP addresses and
> not named instances of MSDE.
> Can anyone help me get this resolved?
>
Replication Publisher and I always get an error. My named instance is called
"MSDE"
Error 18483: Could not connect to server 'mymachine\msde' because
'distributor_admin' is not defined as a remote login at the server.
The only remote thing I can find on the MS support site is:
http://support.microsoft.com/default...;en-us;Q324992
but that really didn't help, since it was talking about IP addresses and not
named instances of MSDE.
Can anyone help me get this resolved?
FYI... i also found this article:
http://support.microsoft.com/default...b;en-us;818334
which talks about server names... when I look at the @.@.ServerName variable,
it returns my hostname and instance name: CORPDALL140451\MSDE
is that the problem? I already have a SQL Server instance with no name
running on my machine, but I must have this MSDE instance be the replication
publisher.
"Derick Bailey" <DerickBailey@.srcp.com> wrote in message
news:eR7q4xUtEHA.3788@.TK2MSFTNGP09.phx.gbl...
> I'm trying to setup a named instance of MSDE on my local machine, as a
> Replication Publisher and I always get an error. My named instance is
> called "MSDE"
> Error 18483: Could not connect to server 'mymachine\msde' because
> 'distributor_admin' is not defined as a remote login at the server.
> The only remote thing I can find on the MS support site is:
> http://support.microsoft.com/default...;en-us;Q324992
> but that really didn't help, since it was talking about IP addresses and
> not named instances of MSDE.
> Can anyone help me get this resolved?
>
MSDE Named Service Connection Problem
I installed SQL 2000 MSDE 2000RelA on Win2K Adv. Server w/ Win2K SP4 (fully
patched), and operating as the only domain controller. I have also run the
IISLockdown Tool on this server.
I originally ran setup using the following parameters:
setup sapwd="xxxxxxx" and SQL Service Manager was connecting properly.
I later uninstalled MSDE 2000 RelA and re-installed (no reboot in between)
with the following parameters:
setup sapwd="xxxxxxx" instancename=WSUS
I then installed SQL2000 MSDE SP4, and the Service Manager can no longer
connect to any service and appears in the task bar with a blank icon. When I
open the Service Manager, all fields (server,services) are blank. Pressing
start button will give me:
"The service control action cannot be completed as no
service has been selected"
I entered the server's name in the server field, but no services can be
resolved.
I see MSSQL$WSUS service has started. Further down I noticed
SQLAgent$TESTING service had not started. I started that up, but no change.
Also tried to startup MSSQLServerADHelper but it gave me an error.
I then uninstalled SQL2000 MSDE and deleted each of the relevant Registry
keys and SQL Server folder under Program Files.
I again re-installed using the sapwd and instancename parameters but to no
avail.
Can anyone tell me how I can get this working properly?
Thanks!
You could have tried to enter "ComputerName\WSUS" in the service manager
when showed nothing in the server list, and then clicked "Start" button.
Somethimes, for some reason, service manager could not detect any running
SQL/MSDE on the computer/network.
"stantm1" <stantm1@.discussions.microsoft.com> wrote in message
news:5BF4C64E-8D57-4CC1-837B-CB143CCB6329@.microsoft.com...
>I installed SQL 2000 MSDE 2000RelA on Win2K Adv. Server w/ Win2K SP4 (fully
> patched), and operating as the only domain controller. I have also run the
> IISLockdown Tool on this server.
> I originally ran setup using the following parameters:
> setup sapwd="xxxxxxx" and SQL Service Manager was connecting properly.
> I later uninstalled MSDE 2000 RelA and re-installed (no reboot in between)
> with the following parameters:
> setup sapwd="xxxxxxx" instancename=WSUS
> I then installed SQL2000 MSDE SP4, and the Service Manager can no longer
> connect to any service and appears in the task bar with a blank icon. When
> I
> open the Service Manager, all fields (server,services) are blank. Pressing
> start button will give me:
> "The service control action cannot be completed as no
> service has been selected"
> I entered the server's name in the server field, but no services can be
> resolved.
> I see MSSQL$WSUS service has started. Further down I noticed
> SQLAgent$TESTING service had not started. I started that up, but no
> change.
> Also tried to startup MSSQLServerADHelper but it gave me an error.
> I then uninstalled SQL2000 MSDE and deleted each of the relevant Registry
> keys and SQL Server folder under Program Files.
> I again re-installed using the sapwd and instancename parameters but to no
> avail.
> Can anyone tell me how I can get this working properly?
> Thanks!
|||Thanks, Norman. I'll give it a try.
"Norman Yuan" wrote:
> You could have tried to enter "ComputerName\WSUS" in the service manager
> when showed nothing in the server list, and then clicked "Start" button.
> Somethimes, for some reason, service manager could not detect any running
> SQL/MSDE on the computer/network.
> "stantm1" <stantm1@.discussions.microsoft.com> wrote in message
> news:5BF4C64E-8D57-4CC1-837B-CB143CCB6329@.microsoft.com...
>
>
|||Actually it found the instance of sql server just fine. My machine was in
the list of sql servers but when i try to connect to it i have problems.
Just to let you know im using Windows Authentication and i am an
administrator on this machine.
Brent
"Norman Yuan" <NotReal@.NotReal.not> wrote in message
news:usGQBJbLGHA.3496@.TK2MSFTNGP14.phx.gbl...
> You could have tried to enter "ComputerName\WSUS" in the service manager
> when showed nothing in the server list, and then clicked "Start" button.
> Somethimes, for some reason, service manager could not detect any running
> SQL/MSDE on the computer/network.
> "stantm1" <stantm1@.discussions.microsoft.com> wrote in message
> news:5BF4C64E-8D57-4CC1-837B-CB143CCB6329@.microsoft.com...
>
patched), and operating as the only domain controller. I have also run the
IISLockdown Tool on this server.
I originally ran setup using the following parameters:
setup sapwd="xxxxxxx" and SQL Service Manager was connecting properly.
I later uninstalled MSDE 2000 RelA and re-installed (no reboot in between)
with the following parameters:
setup sapwd="xxxxxxx" instancename=WSUS
I then installed SQL2000 MSDE SP4, and the Service Manager can no longer
connect to any service and appears in the task bar with a blank icon. When I
open the Service Manager, all fields (server,services) are blank. Pressing
start button will give me:
"The service control action cannot be completed as no
service has been selected"
I entered the server's name in the server field, but no services can be
resolved.
I see MSSQL$WSUS service has started. Further down I noticed
SQLAgent$TESTING service had not started. I started that up, but no change.
Also tried to startup MSSQLServerADHelper but it gave me an error.
I then uninstalled SQL2000 MSDE and deleted each of the relevant Registry
keys and SQL Server folder under Program Files.
I again re-installed using the sapwd and instancename parameters but to no
avail.
Can anyone tell me how I can get this working properly?
Thanks!
You could have tried to enter "ComputerName\WSUS" in the service manager
when showed nothing in the server list, and then clicked "Start" button.
Somethimes, for some reason, service manager could not detect any running
SQL/MSDE on the computer/network.
"stantm1" <stantm1@.discussions.microsoft.com> wrote in message
news:5BF4C64E-8D57-4CC1-837B-CB143CCB6329@.microsoft.com...
>I installed SQL 2000 MSDE 2000RelA on Win2K Adv. Server w/ Win2K SP4 (fully
> patched), and operating as the only domain controller. I have also run the
> IISLockdown Tool on this server.
> I originally ran setup using the following parameters:
> setup sapwd="xxxxxxx" and SQL Service Manager was connecting properly.
> I later uninstalled MSDE 2000 RelA and re-installed (no reboot in between)
> with the following parameters:
> setup sapwd="xxxxxxx" instancename=WSUS
> I then installed SQL2000 MSDE SP4, and the Service Manager can no longer
> connect to any service and appears in the task bar with a blank icon. When
> I
> open the Service Manager, all fields (server,services) are blank. Pressing
> start button will give me:
> "The service control action cannot be completed as no
> service has been selected"
> I entered the server's name in the server field, but no services can be
> resolved.
> I see MSSQL$WSUS service has started. Further down I noticed
> SQLAgent$TESTING service had not started. I started that up, but no
> change.
> Also tried to startup MSSQLServerADHelper but it gave me an error.
> I then uninstalled SQL2000 MSDE and deleted each of the relevant Registry
> keys and SQL Server folder under Program Files.
> I again re-installed using the sapwd and instancename parameters but to no
> avail.
> Can anyone tell me how I can get this working properly?
> Thanks!
|||Thanks, Norman. I'll give it a try.
"Norman Yuan" wrote:
> You could have tried to enter "ComputerName\WSUS" in the service manager
> when showed nothing in the server list, and then clicked "Start" button.
> Somethimes, for some reason, service manager could not detect any running
> SQL/MSDE on the computer/network.
> "stantm1" <stantm1@.discussions.microsoft.com> wrote in message
> news:5BF4C64E-8D57-4CC1-837B-CB143CCB6329@.microsoft.com...
>
>
|||Actually it found the instance of sql server just fine. My machine was in
the list of sql servers but when i try to connect to it i have problems.
Just to let you know im using Windows Authentication and i am an
administrator on this machine.
Brent
"Norman Yuan" <NotReal@.NotReal.not> wrote in message
news:usGQBJbLGHA.3496@.TK2MSFTNGP14.phx.gbl...
> You could have tried to enter "ComputerName\WSUS" in the service manager
> when showed nothing in the server list, and then clicked "Start" button.
> Somethimes, for some reason, service manager could not detect any running
> SQL/MSDE on the computer/network.
> "stantm1" <stantm1@.discussions.microsoft.com> wrote in message
> news:5BF4C64E-8D57-4CC1-837B-CB143CCB6329@.microsoft.com...
>
Monday, March 12, 2012
MSDE local host failure
Why would the localhost not install but rather our named instance will
install? We have an inconsistent problem with installations. Our app
depends on a named instance and a secondary app depends on local host
so we need both. However, systems that have previous installed,
uninstalled and try to reinstall the current app, only the local host
will install or the named instance will install, but not both. This
doesn't happen on all machines either. We encounter the usual errors
as seen in this group such as 'server not found', etc. and I can
usually get MSDE installed only if after I uninstall, I delete the MSDE
references in the registry. Yet I am baffled how MSDE would install
the named instance but not the local. This has primarily been occuring
on XP sp2 machines and all data resides on the client machine where
MSDE is installed.
Any suggestions?
Thanks.
hi,
Colleen wrote:
> Why would the localhost not install but rather our named instance will
> install? We have an inconsistent problem with installations. Our app
> depends on a named instance and a secondary app depends on local host
> so we need both. However, systems that have previous installed,
> uninstalled and try to reinstall the current app, only the local host
> will install or the named instance will install, but not both. This
> doesn't happen on all machines either. We encounter the usual errors
> as seen in this group such as 'server not found', etc. and I can
> usually get MSDE installed only if after I uninstall, I delete the
> MSDE references in the registry. Yet I am baffled how MSDE would
> install the named instance but not the local. This has primarily
> been occuring on XP sp2 machines and all data resides on the client
> machine where MSDE is installed.
just to test, I installed 2 additional named instances of MSDE (sp3 and sp4)
on a pc hosting 1 deafault instance of MSDE sp4...
and I am unable to reproduce the problem... of course, uninstalling an
instance requires you to manually clean the file system, or manually remove
all file system and windows registry entries...
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
install? We have an inconsistent problem with installations. Our app
depends on a named instance and a secondary app depends on local host
so we need both. However, systems that have previous installed,
uninstalled and try to reinstall the current app, only the local host
will install or the named instance will install, but not both. This
doesn't happen on all machines either. We encounter the usual errors
as seen in this group such as 'server not found', etc. and I can
usually get MSDE installed only if after I uninstall, I delete the MSDE
references in the registry. Yet I am baffled how MSDE would install
the named instance but not the local. This has primarily been occuring
on XP sp2 machines and all data resides on the client machine where
MSDE is installed.
Any suggestions?
Thanks.
hi,
Colleen wrote:
> Why would the localhost not install but rather our named instance will
> install? We have an inconsistent problem with installations. Our app
> depends on a named instance and a secondary app depends on local host
> so we need both. However, systems that have previous installed,
> uninstalled and try to reinstall the current app, only the local host
> will install or the named instance will install, but not both. This
> doesn't happen on all machines either. We encounter the usual errors
> as seen in this group such as 'server not found', etc. and I can
> usually get MSDE installed only if after I uninstall, I delete the
> MSDE references in the registry. Yet I am baffled how MSDE would
> install the named instance but not the local. This has primarily
> been occuring on XP sp2 machines and all data resides on the client
> machine where MSDE is installed.
just to test, I installed 2 additional named instances of MSDE (sp3 and sp4)
on a pc hosting 1 deafault instance of MSDE sp4...
and I am unable to reproduce the problem... of course, uninstalling an
instance requires you to manually clean the file system, or manually remove
all file system and windows registry entries...
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
Friday, March 9, 2012
msde installation question.
Hi,
When i install MSDE it creates a folder named "Microsoft SQL
Server\80\..." in Program Files why it create this folder? Is there any way
to bypass this folder installation. thanks a lot
hi,
"Shoaib Khanzada" <shoaibkhanzada@.hotmail.com> ha scritto nel messaggio
news:uxeO8cpEEHA.1368@.TK2MSFTNGP11.phx.gbl...
> Hi,
> When i install MSDE it creates a folder named "Microsoft SQL
> Server\80\..." in Program Files why it create this folder? Is there any
way
> to bypass this folder installation. thanks a lot
even when specifying a different path for DATADIR and TARGETDIR, MSDE
requires to install some stuff in \Program Files\...
those files, bynaries and executables, are service pack indipendent (the
always are updated at the higher service pack level) and are shared among
all instances installed on the targe pc...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.6.0 - DbaMgr ver 0.52.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
When i install MSDE it creates a folder named "Microsoft SQL
Server\80\..." in Program Files why it create this folder? Is there any way
to bypass this folder installation. thanks a lot
hi,
"Shoaib Khanzada" <shoaibkhanzada@.hotmail.com> ha scritto nel messaggio
news:uxeO8cpEEHA.1368@.TK2MSFTNGP11.phx.gbl...
> Hi,
> When i install MSDE it creates a folder named "Microsoft SQL
> Server\80\..." in Program Files why it create this folder? Is there any
way
> to bypass this folder installation. thanks a lot
even when specifying a different path for DATADIR and TARGETDIR, MSDE
requires to install some stuff in \Program Files\...
those files, bynaries and executables, are service pack indipendent (the
always are updated at the higher service pack level) and are shared among
all instances installed on the targe pc...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.6.0 - DbaMgr ver 0.52.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)