Showing posts with label servers. Show all posts
Showing posts with label servers. Show all posts

Monday, March 26, 2012

MSDE searching for servers on the network.

Hi,
I have a MSDE installation on the network. I have no need though to
talk to any other MSDE servers or visa versa.
Is it possible to stop MSDE looking for other servers on the network
and also stop other servers finding me?
Thanks
Lee
Hi Lee,
Run svrnetcn.exe and disable all network protocols. Access the MSDE using
shared memory instead (use server name (local) ), even choose the "Hide
Server" option in the properties of TCP in that screen.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Lee Farrant" <leefarrant@.hotmail.com> wrote in message
news:97ad5817.0409160016.4e99863a@.posting.google.c om...
> Hi,
> I have a MSDE installation on the network. I have no need though to
> talk to any other MSDE servers or visa versa.
> Is it possible to stop MSDE looking for other servers on the network
> and also stop other servers finding me?
> Thanks
> Lee
|||Hello Greg,
Thanks for your help I will have a look at these settings.
Lee
"Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message news:<eRyFDDInEHA.1672@.TK2MSFTNGP09.phx.gbl>...[vbcol=seagreen]
> Hi Lee,
> Run svrnetcn.exe and disable all network protocols. Access the MSDE using
> shared memory instead (use server name (local) ), even choose the "Hide
> Server" option in the properties of TCP in that screen.
> HTH,
> --
> Greg Low [MVP]
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "Lee Farrant" <leefarrant@.hotmail.com> wrote in message
> news:97ad5817.0409160016.4e99863a@.posting.google.c om...

Wednesday, March 21, 2012

MSDE not the same on Load Balanced Servers

Hi,
I have two servers that are load balanced and I am
rebuilding one. I installed Application Center on the
box I am rebuilding and it installed MSDE. When I run
SQL Service Manager on the newly built box, It looks like
this:
Server: Web-Server-01\MSAC
Services: SQL Server
On the second server it looks:
Server: Web-Server-02
Services: SQL Server
I would like for them to be exactly the same, how do I
get box 1 to not be appended by \MSAC. I know very
little about SQL so maybe it doesn't even matter. But I
would sure like to know for certain.
Thanks
With the MSDE (and with SQL server), the name of the server on its own
refers to a "default" instance of the product. If you install additional
instances, they have an instance name and are referred to by
servername\instancename.
When you install the MSDE, you can specify the instance name to be used. I'd
suggest making them both have an instance name (ie the same name).
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Ishmeal" <anonymous@.discussions.microsoft.com> wrote in message
news:026b01c49785$a94b37a0$a501280a@.phx.gbl...
> Hi,
> I have two servers that are load balanced and I am
> rebuilding one. I installed Application Center on the
> box I am rebuilding and it installed MSDE. When I run
> SQL Service Manager on the newly built box, It looks like
> this:
> Server: Web-Server-01\MSAC
> Services: SQL Server
> On the second server it looks:
> Server: Web-Server-02
> Services: SQL Server
> I would like for them to be exactly the same, how do I
> get box 1 to not be appended by \MSAC. I know very
> little about SQL so maybe it doesn't even matter. But I
> would sure like to know for certain.
> Thanks

Friday, March 9, 2012

MSDE Installation Problem

I have installed MSDE on a computer but when I try to create an ODBC
connection to it, I can't find the server in the ODBC list of servers
available.
I am trying this on a system that has SQL Server 2000 for Developers on it
What does appear in the list are the following:
(local)
CRA-SERVER-2
Cra-Server-2
I don't know why there are two servers listed plus local, but all three
point to
the database setup under SQL Server 2000 for Developers.
It appears that MSDE installed properly. When I look in Component Services,
it is listed as MSSQL$CDC2, status = Started, Startup type = Automatic,
Logon as Local System. CDC2 is the instance name that I specified in the
Setup portion of the MSDE install package.
The directories specified all seem to have the files and data structures.
When I run the OSQL -E -S \CDC2 I get an error. The error message says:
[DBNETLIB]SQL Server does not exist or access denied.
[DBNETLIB]ConnectionOpen (Connect() ).
When I look at the Task Manager, I have 2 copies of sqlservr.exe running. I
Assume one is for SQL Server 2000 Developer and the other is MSDE. (?)
I am a developer and need an ODBC connection to the database in the MSDE
installed CDC2 server. Can someone point me in the right direction for
resolving
this ODBC/SQL Server problem?
Thanks for your help.
LanceDoes this work with SQL authentication?
Meaning,
Osql -Usa -Ppassword sqlserver\instancename?
If it does, then you might want to check
325022 INFO: MSDE Security and Authentication
http://support.microsoft.com/?id=325022
Cheers,
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

MSDE installation messes up Query Analayzer and Enterprise Manager

Does anyone out there know how to fix the problem with the SQL tools and MSDE?
I have found that if you install MSDE after installing SQL Server's Tools
the tools don't work anymore. Any help or suggestions here would be
appreciated.
Try reapplying latest service pack.
"jdehne" <jdehne@.discussions.microsoft.com> wrote in message
news:8E64752E-84F1-462D-A614-2E6CCF943300@.microsoft.com...
> Does anyone out there know how to fix the problem with the SQL tools and
> MSDE?
> I have found that if you install MSDE after installing SQL Server's Tools
> the tools don't work anymore. Any help or suggestions here would be
> appreciated.

Monday, February 20, 2012

MSDE fails to connect

Hi All
I have a bunch of test/demo servers running on VMware Workstation
Some of those is running Axapta 3.0 sp3 demo version with MSDE 2 as the data
engine (named instance)
I have moved the VMware files around from one host to another
OS starts nicely, I get an IP and get access to the internet
On one server I have SQL2k running whitout problems
All other apps is working nicely
After moving the VMware files I can't connect to the MSDE database anymore?
The MSDE Service has been started (checked using net start)
The IP adress is on a different network on this new host
Any pointers on where I can start trouble shooting?
One note: One of the servers has been cloned at some point the clone still
works as expeccted
Thanks in advance
- Peter
hi Peter,
Peter Lykkegaard wrote:
> Hi All
> I have a bunch of test/demo servers running on VMware Workstation
> Some of those is running Axapta 3.0 sp3 demo version with MSDE 2 as
> the data engine (named instance)
> I have moved the VMware files around from one host to another
> OS starts nicely, I get an IP and get access to the internet
> On one server I have SQL2k running whitout problems
> All other apps is working nicely
> After moving the VMware files I can't connect to the MSDE database
> anymore? The MSDE Service has been started (checked using net start)
> The IP adress is on a different network on this new host
> Any pointers on where I can start trouble shooting?
> One note: One of the servers has been cloned at some point the clone
> still works as expeccted
you can no longer connect locally or remotely?
is the MSDE's errolog file indicating troubles, or the event log?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.16.0 - DbaMgr ver 0.61.0
(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

> you can no longer connect locally or remotely?
Locally

> is the MSDE's errolog file indicating troubles, or the event log?
Ehh could it be because I have no DC for the OS?
Forgot about that - hmm
- changing to workgroup - don't need a DC for this setup ...
It's working now, hmm - bugger
Note to oneself - always check the applicationlog
Thanks/Peter