Showing posts with label client. Show all posts
Showing posts with label client. Show all posts

Wednesday, March 28, 2012

MSDE Sp3 client connection

Hi, I am trying to connect to a MSDE Sp3 database remotely, however I always
got "server does not exist or access denied". I was told that the problem is
from sp3.
Any idea how can I solved the problem'
Met vriendelijke groet,
Guoqi Zheng
Tel: +31 (0) 23 5343545
http://www.meetholland.comMSDE has limitations on how many workloads it can accept, not what kind of
connections it can take. One question though, what kind of OS is MSDE
running on? Windows 98 does not provide Named Pipes support, so you may
have to change your connection protocol to TCP/IP sockets. Also TCP/IP
sockets runs on port 1433 by default, if there is a hardware or software
firewall blocking that port, you will be in trouble.
The biggest troubleshooting step I can suggest is to just try and map
another shared network resource from that computer -- printer, shared drive,
ipc$ (if available), whatever. Do you have any problems with that? Can you
connect after that?
Good luck. Hope that helps.
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"Guoqi Zheng" <no@.sorry.com> wrote in message
news:%23uJUoH9zDHA.2568@.TK2MSFTNGP09.phx.gbl...
quote:

> Hi, I am trying to connect to a MSDE Sp3 database remotely, however I

always
quote:

> got "server does not exist or access denied". I was told that the problem

is
quote:

> from sp3.
> Any idea how can I solved the problem'
> --
> Met vriendelijke groet,
> Guoqi Zheng
> Tel: +31 (0) 23 5343545
> http://www.meetholland.com
>
|||Thanks a lot for your quick reply. It is running under MS 2003 server web
edition.
The server is a dedicated server, I can not put any shared driver there.
What should I do'
Met vriendelijke groet,
Guoqi Zheng
Tel: +31 (0) 23 5343545
http://www.meetholland.com
"Andy Svendsen" <andymcdba1@.NOMORESPAM.yahoo.com> д?
:uZPzzN9zDHA.2180@.TK2MSFTNGP12.phx.gbl...
quote:

> MSDE has limitations on how many workloads it can accept, not what kind of
> connections it can take. One question though, what kind of OS is MSDE
> running on? Windows 98 does not provide Named Pipes support, so you may
> have to change your connection protocol to TCP/IP sockets. Also TCP/IP
> sockets runs on port 1433 by default, if there is a hardware or software
> firewall blocking that port, you will be in trouble.
> The biggest troubleshooting step I can suggest is to just try and map
> another shared network resource from that computer -- printer, shared

drive,
quote:

> ipc$ (if available), whatever. Do you have any problems with that? Can

you
quote:

> connect after that?
> Good luck. Hope that helps.
> --
> ****************************************
***************************
> Andy S.
> MCSE NT/2000, MCDBA SQL 7/2000
> andymcdba1@.NOMORESPAM.yahoo.com
> Please remove NOMORESPAM before replying.
> Always keep your antivirus and Microsoft software
> up to date with the latest definitions and product updates.
> Be suspicious of every email attachment, I will never send
> or post anything other than the text of a http:// link nor
> post the link directly to a file for downloading.
> This posting is provided "as is" with no warranties
> and confers no rights.
> ****************************************
***************************
> "Guoqi Zheng" <no@.sorry.com> wrote in message
> news:%23uJUoH9zDHA.2568@.TK2MSFTNGP09.phx.gbl...
> always
m[QUOTE]
> is
>
|||Check the firewall logs with the network admin.
Verify that your client application is sending TCP traffic not SMB. (Named
Pipes)
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

MSDE Sp3 client connection

Which mode are you authenticating with NT or SQL Server ?
The defaut MSDE mode is NT Authentication, which may cuase
connectivity issues.
MarkI am using mix mode. The problem has been solvoed now...
It is because of firewall... problem of our ISP.
Met vriendelijke groet,
Guoqi Zheng
Tel: +31 (0) 23 5343545
http://www.meetholland.com
"Mark Story" <anonymous@.discussions.microsoft.com> д?
:04c001c3d07e$09fda3a0$a601280a@.phx.gbl...
quote:

> Which mode are you authenticating with NT or SQL Server ?
> The defaut MSDE mode is NT Authentication, which may cuase
> connectivity issues.
> Mark

Monday, March 26, 2012

MSDE scalability

Hi all,
Im currently evaluating a change from Sybase ASA to MSDE
(sql server desktop engine) on all client sites.
We cannot afford to buy a bigger edition of MSDE, so it
is paramount to our decision that MSDE can handle the
expected workload.
We have estimated our maximum load to be 10 requests per.
second, and have run basic tests to ensure MSDE can
handle it. The results were good.
It would be very interesting to hear from anybody with
actual project experience with MSDE. Anybody with an
oppinion on MSDE in a production enviroment should also
let their voices be heard.
Best Regards
AlexHi
Your post is implying that MSDE is a different database engine to standard
SQL Server, which it isn't, therefore the throughput should be as good. You
are limited by database size and number of connections though.
John
"Alex" <alex_pedersen@.accenture_com> wrote in message
news:101b01c38bd9$dd00ff20$a301280a@.phx.gbl...
> Hi all,
> Im currently evaluating a change from Sybase ASA to MSDE
> (sql server desktop engine) on all client sites.
> We cannot afford to buy a bigger edition of MSDE, so it
> is paramount to our decision that MSDE can handle the
> expected workload.
> We have estimated our maximum load to be 10 requests per.
> second, and have run basic tests to ensure MSDE can
> handle it. The results were good.
> It would be very interesting to hear from anybody with
> actual project experience with MSDE. Anybody with an
> oppinion on MSDE in a production enviroment should also
> let their voices be heard.
> Best Regards
> Alex

Friday, March 23, 2012

Msde plus sql server 2000 client tools?

Hi,
I'm want to know if its legal to install on another computer the MSDE 2000
(which is free), and after that install the sql server 2000 client tool
only. this without purchasing the sql server 2000 additional time.
Thanks.
hi,
"Tomer" <Tomer@.dannet.co.il> ha scritto nel messaggio
news:O9fTlzkPEHA.624@.TK2MSFTNGP11.phx.gbl...
> Hi,
> I'm want to know if its legal to install on another computer the MSDE 2000
> (which is free), and after that install the sql server 2000 client tool
> only. this without purchasing the sql server 2000 additional time.
there's actually an open question to Microsoft representatives about this...
at the moment it seems not to be legitimate to use ANY SQL Server tool to
connect to MSDE instances but oSql.exe and/or third parties tools...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Currently it is not legal to use Enterprise Manager / Query Analyzer /
Profiler etc. without a valid client license. There are other tools you can
use to manage MSDE: http://www.aspfaq.com/2442
"Tomer" <Tomer@.dannet.co.il> wrote in message
news:O9fTlzkPEHA.624@.TK2MSFTNGP11.phx.gbl...
> Hi,
> I'm want to know if its legal to install on another computer the MSDE 2000
> (which is free), and after that install the sql server 2000 client tool
> only. this without purchasing the sql server 2000 additional time.
> Thanks.
>

Wednesday, March 21, 2012

MSDE over firewall

Succesfully created a MSDE 2000 rel A backend on 2003
server. I can connect a MS Access project frontend to it
from an XP client on the same LAN segment. I can connect
the same frontend over the internet to this server when
set out in the firewall's DMZ.
And now for my next trick! When I tuck the MSDE server
back behind the firewall and open up TCP and UDP ports at
1433 and 1434 for both incoming and outgoing traffic, I
cannot connect. I include a filtered log showing traffic
between the Access client on the Internet and the firewall
for detail. It appears that the Netgear firewall passes
packets to the server but it times out in a little less
than a minute... I am looking forward to any ideas that
may move this project forward!
TimeProtocolSrcDstApplication
Message
13:58:28UDP645521434ms-sql-m
[Service access request successful]
13:58:28TCP645532418cas[Access
Policy not found, dropping packet]
13:58:31TCP645532418cas[Access
Policy not found, dropping packet]
13:58:37TCP645532418cas[Access
Policy not found, dropping packet]
13:58:51TCP645582418cas[Access
Policy not found, dropping packet]
13:58:54TCP645582418cas[Access
Policy not found, dropping packet]
13:59:00TCP645582418cas[Access
Policy not found, dropping packet]
13:59:14TCP64564445ms-ds[Access
Policy not found, dropping packet]
13:59:14TCP64565139netbios-ssn
[Access Policy not found, dropping packet]
13:59:17TCP64565139netbios-ssn
[Access Policy not found, dropping packet]
13:59:17TCP64564445ms-ds[Access
Policy not found, dropping packet]
13:59:20UDP645521434ms-sql-m
[Connection timed out.Bytes transferred : 137]
13:59:23TCP64565139netbios-ssn
[Access Policy not found, dropping packet]
13:59:23TCP64564445ms-ds[Access
Policy not found, dropping packet]
From your trace it appears that many more IP ports (than 1433 & 1434) are
being attempted to be used.
I suspect it's failing because of the attempt to do name resolution.
Steve
"Ed Morra" <ed@.orl-inc.com> wrote in message
news:36f801c4297b$6a642240$a601280a@.phx.gbl...
> Succesfully created a MSDE 2000 rel A backend on 2003
> server. I can connect a MS Access project frontend to it
> from an XP client on the same LAN segment. I can connect
> the same frontend over the internet to this server when
> set out in the firewall's DMZ.
> And now for my next trick! When I tuck the MSDE server
> back behind the firewall and open up TCP and UDP ports at
> 1433 and 1434 for both incoming and outgoing traffic, I
> cannot connect. I include a filtered log showing traffic
> between the Access client on the Internet and the firewall
> for detail. It appears that the Netgear firewall passes
> packets to the server but it times out in a little less
> than a minute... I am looking forward to any ideas that
> may move this project forward!
> Time Protocol Src Dst Application
> Message
> 13:58:28 UDP 64552 1434 ms-sql-m
> [Service access request successful]
> 13:58:28 TCP 64553 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:31 TCP 64553 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:37 TCP 64553 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:51 TCP 64558 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:54 TCP 64558 2418 cas [Access
> Policy not found, dropping packet]
> 13:59:00 TCP 64558 2418 cas [Access
> Policy not found, dropping packet]
> 13:59:14 TCP 64564 445 ms-ds [Access
> Policy not found, dropping packet]
> 13:59:14 TCP 64565 139 netbios-ssn
> [Access Policy not found, dropping packet]
> 13:59:17 TCP 64565 139 netbios-ssn
> [Access Policy not found, dropping packet]
> 13:59:17 TCP 64564 445 ms-ds [Access
> Policy not found, dropping packet]
> 13:59:20 UDP 64552 1434 ms-sql-m
> [Connection timed out.Bytes transferred : 137]
> 13:59:23 TCP 64565 139 netbios-ssn
> [Access Policy not found, dropping packet]
> 13:59:23 TCP 64564 445 ms-ds [Access
> Policy not found, dropping packet]
>

MSDE over firewall

Succesfully created a MSDE 2000 rel A backend on 2003
server. I can connect a MS Access project frontend to it
from an XP client on the same LAN segment. I can connect
the same frontend over the internet to this server when
set out in the firewall's DMZ.
And now for my next trick! When I tuck the MSDE server
back behind the firewall and open up TCP and UDP ports at
1433 and 1434 for both incoming and outgoing traffic, I
cannot connect. I include a filtered log showing traffic
between the Access client on the Internet and the firewall
for detail. It appears that the Netgear firewall passes
packets to the server but it times out in a little less
than a minute... I am looking forward to any ideas that
may move this project forward!
Time Protocol Src Dst Application
Message
13:58:28 UDP 64552 1434 ms-sql-m
[Service access request successful]
13:58:28 TCP 64553 2418 cas [Access
Policy not found, dropping packet]
13:58:31 TCP 64553 2418 cas [Access
Policy not found, dropping packet]
13:58:37 TCP 64553 2418 cas [Access
Policy not found, dropping packet]
13:58:51 TCP 64558 2418 cas [Access
Policy not found, dropping packet]
13:58:54 TCP 64558 2418 cas [Access
Policy not found, dropping packet]
13:59:00 TCP 64558 2418 cas [Access
Policy not found, dropping packet]
13:59:14 TCP 64564 445 ms-ds [Access
Policy not found, dropping packet]
13:59:14 TCP 64565 139 netbios-ssn
[Access Policy not found, dropping packet]
13:59:17 TCP 64565 139 netbios-ssn
[Access Policy not found, dropping packet]
13:59:17 TCP 64564 445 ms-ds [Access
Policy not found, dropping packet]
13:59:20 UDP 64552 1434 ms-sql-m
[Connection timed out.Bytes transferred : 137]
13:59:23 TCP 64565 139 netbios-ssn
[Access Policy not found, dropping packet]
13:59:23 TCP 64564 445 ms-ds [Access
Policy not found, dropping packet]From your trace it appears that many more IP ports (than 1433 & 1434) are
being attempted to be used.
I suspect it's failing because of the attempt to do name resolution.
Steve
"Ed Morra" <ed@.orl-inc.com> wrote in message
news:36f801c4297b$6a642240$a601280a@.phx.gbl...
> Succesfully created a MSDE 2000 rel A backend on 2003
> server. I can connect a MS Access project frontend to it
> from an XP client on the same LAN segment. I can connect
> the same frontend over the internet to this server when
> set out in the firewall's DMZ.
> And now for my next trick! When I tuck the MSDE server
> back behind the firewall and open up TCP and UDP ports at
> 1433 and 1434 for both incoming and outgoing traffic, I
> cannot connect. I include a filtered log showing traffic
> between the Access client on the Internet and the firewall
> for detail. It appears that the Netgear firewall passes
> packets to the server but it times out in a little less
> than a minute... I am looking forward to any ideas that
> may move this project forward!
> Time Protocol Src Dst Application
> Message
> 13:58:28 UDP 64552 1434 ms-sql-m
> [Service access request successful]
> 13:58:28 TCP 64553 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:31 TCP 64553 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:37 TCP 64553 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:51 TCP 64558 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:54 TCP 64558 2418 cas [Access
> Policy not found, dropping packet]
> 13:59:00 TCP 64558 2418 cas [Access
> Policy not found, dropping packet]
> 13:59:14 TCP 64564 445 ms-ds [Access
> Policy not found, dropping packet]
> 13:59:14 TCP 64565 139 netbios-ssn
> [Access Policy not found, dropping packet]
> 13:59:17 TCP 64565 139 netbios-ssn
> [Access Policy not found, dropping packet]
> 13:59:17 TCP 64564 445 ms-ds [Access
> Policy not found, dropping packet]
> 13:59:20 UDP 64552 1434 ms-sql-m
> [Connection timed out.Bytes transferred : 137]
> 13:59:23 TCP 64565 139 netbios-ssn
> [Access Policy not found, dropping packet]
> 13:59:23 TCP 64564 445 ms-ds [Access
> Policy not found, dropping packet]
>

MSDE Not connecting remotely

Hi Guys,
I have a client who is running SBS2003. We are in the process of moving an
msde 2000 database from WIN2000 server to this server.
We have installed MSDE 2000 and it is running on the new server. We can
connect and access the DB locally. However, we cannot establish a connection
from any PCs on the network. There is no firewall between the PCs and the
server. We have done a port scan on both servers and port 1433 is open on
the old server and not the new one. The netstat command however says the
port is open on the new server.
Can anyone tell me how to open up port 1433 on the server or any other
solutions?Dave,
You should be able to use C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\svrnetcn.exe to configure which library the instance
listens on (like TCP/IP).
If you do a netstat -aon | find ":1433" is sql have the port open?
Hope that helps,
David Copeland
Microsoft Small Business Server Support
This posting is provided "AS IS" with no warranties, and confers no rights.
SBS Newsgroups:
SBS v4.x: microsoft.public.backoffice.smallbiz
SBS 2000: microsoft.public.backoffice.smallbiz2000
SBS 2003: microsoft.public.windows.server.sbs
"Dave" <Dave@.discussions.microsoft.com> wrote in message
news:AE297F27-ACB5-4C46-B652-9E29EE39DC0C@.microsoft.com...
> Hi Guys,
> I have a client who is running SBS2003. We are in the process of moving
an
> msde 2000 database from WIN2000 server to this server.
> We have installed MSDE 2000 and it is running on the new server. We can
> connect and access the DB locally. However, we cannot establish a
connection
> from any PCs on the network. There is no firewall between the PCs and the
> server. We have done a port scan on both servers and port 1433 is open on
> the old server and not the new one. The netstat command however says the
> port is open on the new server.
> Can anyone tell me how to open up port 1433 on the server or any other
> solutions?|||Dave,
Are you trying to get to the MSDE from the external side or internal side?
Do you have ISA installed? Is the SBS 2003 Std. Ed. or Premium Edition?
--
Hope that helps,
David Copeland
Microsoft Small Business Server Support
This posting is provided "AS IS" with no warranties, and confers no rights.
SBS Newsgroups:
SBS v4.x: microsoft.public.backoffice.smallbiz
SBS 2000: microsoft.public.backoffice.smallbiz2000
SBS 2003: microsoft.public.windows.server.sbs
"Dave" <Dave@.discussions.microsoft.com> wrote in message
news:AE297F27-ACB5-4C46-B652-9E29EE39DC0C@.microsoft.com...
> Hi Guys,
> I have a client who is running SBS2003. We are in the process of moving
an
> msde 2000 database from WIN2000 server to this server.
> We have installed MSDE 2000 and it is running on the new server. We can
> connect and access the DB locally. However, we cannot establish a
connection
> from any PCs on the network. There is no firewall between the PCs and the
> server. We have done a port scan on both servers and port 1433 is open on
> the old server and not the new one. The netstat command however says the
> port is open on the new server.
> Can anyone tell me how to open up port 1433 on the server or any other
> solutions?|||Hi Dave,
Use Client Network Utility from the client to configure for Network
Library(TCP/IP) and connection parameters (server name, 1433).
Ravi
"Dave" <Dave@.discussions.microsoft.com> wrote in message news:<AE297F27-ACB5-4C46-B652-9E29EE39DC0C@.microsoft.com>...
> Hi Guys,
> I have a client who is running SBS2003. We are in the process of moving an
> msde 2000 database from WIN2000 server to this server.
> We have installed MSDE 2000 and it is running on the new server. We can
> connect and access the DB locally. However, we cannot establish a connection
> from any PCs on the network. There is no firewall between the PCs and the
> server. We have done a port scan on both servers and port 1433 is open on
> the old server and not the new one. The netstat command however says the
> port is open on the new server.
> Can anyone tell me how to open up port 1433 on the server or any other
> solutions?|||> Are you trying to get to the MSDE from the external side or internal side?
> Do you have ISA installed? Is the SBS 2003 Std. Ed. or Premium Edition?
I am trying to access the MSDE from the internal network.
We are running SBS 2003 Std which does not include SQL server or ISA (It
sounds like it would have been a good idea to buy premium now doesn't it?)
I have run the svrnetcn.exe and TCP\IP is included. I have run the netstat
command you asked me to run and received the following information:
TCP 0.0.0.0:1433 0.0.0.0:0 Listening 5596|||Where will I find the Client Network Utility on MSDE2000? Will I need to
install MSDE onto my PC? I am using MSDE Plus 2.1 to try to establish a
connection. It works locally on the server.
I have tried creating an ODBC connection to the server, specifying port
1433, but this connection failed.
Is there a way to open port 1433 on SBS2003?
"Ravi" wrote:
> Hi Dave,
> Use Client Network Utility from the client to configure for Network
> Library(TCP/IP) and connection parameters (server name, 1433).
> Ravi
> "Dave" <Dave@.discussions.microsoft.com> wrote in message news:<AE297F27-ACB5-4C46-B652-9E29EE39DC0C@.microsoft.com>...
> > Hi Guys,
> >
> > I have a client who is running SBS2003. We are in the process of moving an
> > msde 2000 database from WIN2000 server to this server.
> >
> > We have installed MSDE 2000 and it is running on the new server. We can
> > connect and access the DB locally. However, we cannot establish a connection
> > from any PCs on the network. There is no firewall between the PCs and the
> > server. We have done a port scan on both servers and port 1433 is open on
> > the old server and not the new one. The netstat command however says the
> > port is open on the new server.
> >
> > Can anyone tell me how to open up port 1433 on the server or any other
> > solutions?
>|||If you install the sql server client tools you will get this client
network utility.
"Dave" <Dave@.discussions.microsoft.com> wrote in message news:<F83A4647-58A5-4D55-8FAB-23D900D6070A@.microsoft.com>...
> Where will I find the Client Network Utility on MSDE2000? Will I need to
> install MSDE onto my PC? I am using MSDE Plus 2.1 to try to establish a
> connection. It works locally on the server.
> I have tried creating an ODBC connection to the server, specifying port
> 1433, but this connection failed.
> Is there a way to open port 1433 on SBS2003?
> "Ravi" wrote:
> > Hi Dave,
> >
> > Use Client Network Utility from the client to configure for Network
> > Library(TCP/IP) and connection parameters (server name, 1433).
> >
> > Ravi
> >
> > "Dave" <Dave@.discussions.microsoft.com> wrote in message news:<AE297F27-ACB5-4C46-B652-9E29EE39DC0C@.microsoft.com>...
> > > Hi Guys,
> > >
> > > I have a client who is running SBS2003. We are in the process of moving an
> > > msde 2000 database from WIN2000 server to this server.
> > >
> > > We have installed MSDE 2000 and it is running on the new server. We can
> > > connect and access the DB locally. However, we cannot establish a connection
> > > from any PCs on the network. There is no firewall between the PCs and the
> > > server. We have done a port scan on both servers and port 1433 is open on
> > > the old server and not the new one. The netstat command however says the
> > > port is open on the new server.
> > >
> > > Can anyone tell me how to open up port 1433 on the server or any other
> > > solutions?|||Dave,
At least on the server take a look at \%systemroom$\system32\cliconfg.exe.
If you run the tasklist /svc with the process id from the netstat -aon for
port 1433 does it show it as being owned by SQL? For example
netstat -aon | find ":1433"
TCP 0.0.0.0:1433 0.0.0.0:0 Listening 5596
tasklist /svc | find "5596"
You might also take a look in \program files\microsoft sql
server\instancename\log directory at the ERRORLOG files to verify that the
instance you are expecting on TCP Port 1433 is the one you expect.. since by
default SBS 2003 will install an SBSMonitoring (MSDE) and SharePoint (WMSDE)
instance (both of which are only configured to use Shared Memory)
Hope that helps,
David Copeland
Microsoft Small Business Server Support
This posting is provided "AS IS" with no warranties, and confers no rights.
SBS Newsgroups:
SBS v4.x: microsoft.public.backoffice.smallbiz
SBS 2000: microsoft.public.backoffice.smallbiz2000
SBS 2003: microsoft.public.windows.server.sbs
"Ravi" <sayravi@.yahoo.com> wrote in message
news:838d29e0.0410180905.f443d40@.posting.google.com...
> If you install the sql server client tools you will get this client
> network utility.
> "Dave" <Dave@.discussions.microsoft.com> wrote in message
news:<F83A4647-58A5-4D55-8FAB-23D900D6070A@.microsoft.com>...
> > Where will I find the Client Network Utility on MSDE2000? Will I need
to
> > install MSDE onto my PC? I am using MSDE Plus 2.1 to try to establish a
> > connection. It works locally on the server.
> >
> > I have tried creating an ODBC connection to the server, specifying port
> > 1433, but this connection failed.
> >
> > Is there a way to open port 1433 on SBS2003?
> >
> > "Ravi" wrote:
> >
> > > Hi Dave,
> > >
> > > Use Client Network Utility from the client to configure for Network
> > > Library(TCP/IP) and connection parameters (server name, 1433).
> > >
> > > Ravi
> > >
> > > "Dave" <Dave@.discussions.microsoft.com> wrote in message
news:<AE297F27-ACB5-4C46-B652-9E29EE39DC0C@.microsoft.com>...
> > > > Hi Guys,
> > > >
> > > > I have a client who is running SBS2003. We are in the process of
moving an
> > > > msde 2000 database from WIN2000 server to this server.
> > > >
> > > > We have installed MSDE 2000 and it is running on the new server. We
can
> > > > connect and access the DB locally. However, we cannot establish a
connection
> > > > from any PCs on the network. There is no firewall between the PCs
and the
> > > > server. We have done a port scan on both servers and port 1433 is
open on
> > > > the old server and not the new one. The netstat command however
says the
> > > > port is open on the new server.
> > > >
> > > > Can anyone tell me how to open up port 1433 on the server or any
other
> > > > solutions?

MSDE Not connecting remotely

Hi Guys,
I have a client who is running SBS2003. We are in the process of moving an
msde 2000 database from WIN2000 server to this server.
We have installed MSDE 2000 and it is running on the new server. We can
connect and access the DB locally. However, we cannot establish a connection
from any PCs on the network. There is no firewall between the PCs and the
server. We have done a port scan on both servers and port 1433 is open on
the old server and not the new one. The netstat command however says the
port is open on the new server.
Can anyone tell me how to open up port 1433 on the server or any other
solutions?
Dave,
You should be able to use C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\svrnetcn.exe to configure which library the instance
listens on (like TCP/IP).
If you do a netstat -aon | find ":1433" is sql have the port open?

Hope that helps,
David Copeland
Microsoft Small Business Server Support
This posting is provided "AS IS" with no warranties, and confers no rights.
SBS Newsgroups:
SBS v4.x: microsoft.public.backoffice.smallbiz
SBS 2000: microsoft.public.backoffice.smallbiz2000
SBS 2003: microsoft.public.windows.server.sbs
"Dave" <Dave@.discussions.microsoft.com> wrote in message
news:AE297F27-ACB5-4C46-B652-9E29EE39DC0C@.microsoft.com...
> Hi Guys,
> I have a client who is running SBS2003. We are in the process of moving
an
> msde 2000 database from WIN2000 server to this server.
> We have installed MSDE 2000 and it is running on the new server. We can
> connect and access the DB locally. However, we cannot establish a
connection
> from any PCs on the network. There is no firewall between the PCs and the
> server. We have done a port scan on both servers and port 1433 is open on
> the old server and not the new one. The netstat command however says the
> port is open on the new server.
> Can anyone tell me how to open up port 1433 on the server or any other
> solutions?
|||Dave,
Are you trying to get to the MSDE from the external side or internal side?
Do you have ISA installed? Is the SBS 2003 Std. Ed. or Premium Edition?
Hope that helps,
David Copeland
Microsoft Small Business Server Support
This posting is provided "AS IS" with no warranties, and confers no rights.
SBS Newsgroups:
SBS v4.x: microsoft.public.backoffice.smallbiz
SBS 2000: microsoft.public.backoffice.smallbiz2000
SBS 2003: microsoft.public.windows.server.sbs
"Dave" <Dave@.discussions.microsoft.com> wrote in message
news:AE297F27-ACB5-4C46-B652-9E29EE39DC0C@.microsoft.com...
> Hi Guys,
> I have a client who is running SBS2003. We are in the process of moving
an
> msde 2000 database from WIN2000 server to this server.
> We have installed MSDE 2000 and it is running on the new server. We can
> connect and access the DB locally. However, we cannot establish a
connection
> from any PCs on the network. There is no firewall between the PCs and the
> server. We have done a port scan on both servers and port 1433 is open on
> the old server and not the new one. The netstat command however says the
> port is open on the new server.
> Can anyone tell me how to open up port 1433 on the server or any other
> solutions?
|||Hi Dave,
Use Client Network Utility from the client to configure for Network
Library(TCP/IP) and connection parameters (server name, 1433).
Ravi
"Dave" <Dave@.discussions.microsoft.com> wrote in message news:<AE297F27-ACB5-4C46-B652-9E29EE39DC0C@.microsoft.com>...
> Hi Guys,
> I have a client who is running SBS2003. We are in the process of moving an
> msde 2000 database from WIN2000 server to this server.
> We have installed MSDE 2000 and it is running on the new server. We can
> connect and access the DB locally. However, we cannot establish a connection
> from any PCs on the network. There is no firewall between the PCs and the
> server. We have done a port scan on both servers and port 1433 is open on
> the old server and not the new one. The netstat command however says the
> port is open on the new server.
> Can anyone tell me how to open up port 1433 on the server or any other
> solutions?
|||> Are you trying to get to the MSDE from the external side or internal side?
> Do you have ISA installed? Is the SBS 2003 Std. Ed. or Premium Edition?
I am trying to access the MSDE from the internal network.
We are running SBS 2003 Std which does not include SQL server or ISA (It
sounds like it would have been a good idea to buy premium now doesn't it?)
I have run the svrnetcn.exe and TCP\IP is included. I have run the netstat
command you asked me to run and received the following information:
TCP 0.0.0.0:1433 0.0.0.0:0 Listening 5596
|||Where will I find the Client Network Utility on MSDE2000? Will I need to
install MSDE onto my PC? I am using MSDE Plus 2.1 to try to establish a
connection. It works locally on the server.
I have tried creating an ODBC connection to the server, specifying port
1433, but this connection failed.
Is there a way to open port 1433 on SBS2003?
"Ravi" wrote:

> Hi Dave,
> Use Client Network Utility from the client to configure for Network
> Library(TCP/IP) and connection parameters (server name, 1433).
> Ravi
> "Dave" <Dave@.discussions.microsoft.com> wrote in message news:<AE297F27-ACB5-4C46-B652-9E29EE39DC0C@.microsoft.com>...
>
|||If you install the sql server client tools you will get this client
network utility.
"Dave" <Dave@.discussions.microsoft.com> wrote in message news:<F83A4647-58A5-4D55-8FAB-23D900D6070A@.microsoft.com>...[vbcol=seagreen]
> Where will I find the Client Network Utility on MSDE2000? Will I need to
> install MSDE onto my PC? I am using MSDE Plus 2.1 to try to establish a
> connection. It works locally on the server.
> I have tried creating an ODBC connection to the server, specifying port
> 1433, but this connection failed.
> Is there a way to open port 1433 on SBS2003?
> "Ravi" wrote:
|||Dave,
At least on the server take a look at \%systemroom$\system32\cliconfg.exe.
If you run the tasklist /svc with the process id from the netstat -aon for
port 1433 does it show it as being owned by SQL? For example
netstat -aon | find ":1433"
TCP 0.0.0.0:1433 0.0.0.0:0 Listening 5596
tasklist /svc | find "5596"
You might also take a look in \program files\microsoft sql
server\instancename\log directory at the ERRORLOG files to verify that the
instance you are expecting on TCP Port 1433 is the one you expect.. since by
default SBS 2003 will install an SBSMonitoring (MSDE) and SharePoint (WMSDE)
instance (both of which are only configured to use Shared Memory)

Hope that helps,
David Copeland
Microsoft Small Business Server Support
This posting is provided "AS IS" with no warranties, and confers no rights.
SBS Newsgroups:
SBS v4.x: microsoft.public.backoffice.smallbiz
SBS 2000: microsoft.public.backoffice.smallbiz2000
SBS 2003: microsoft.public.windows.server.sbs
"Ravi" <sayravi@.yahoo.com> wrote in message
news:838d29e0.0410180905.f443d40@.posting.google.co m...
> If you install the sql server client tools you will get this client
> network utility.
> "Dave" <Dave@.discussions.microsoft.com> wrote in message
news:<F83A4647-58A5-4D55-8FAB-23D900D6070A@.microsoft.com>...[vbcol=seagreen]
to[vbcol=seagreen]
news:<AE297F27-ACB5-4C46-B652-9E29EE39DC0C@.microsoft.com>...[vbcol=seagreen]
moving an[vbcol=seagreen]
can[vbcol=seagreen]
connection[vbcol=seagreen]
and the[vbcol=seagreen]
open on[vbcol=seagreen]
says the[vbcol=seagreen]
other[vbcol=seagreen]

MSDE Not connecting remotely

Hi Guys,
I have a client who is running SBS2003. We are in the process of moving an
msde 2000 database from WIN2000 server to this server.
We have installed MSDE 2000 and it is running on the new server. We can
connect and access the DB locally. However, we cannot establish a connectio
n
from any PCs on the network. There is no firewall between the PCs and the
server. We have done a port scan on both servers and port 1433 is open on
the old server and not the new one. The netstat command however says the
port is open on the new server.
Can anyone tell me how to open up port 1433 on the server or any other
solutions?Dave,
You should be able to use C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\svrnetcn.exe to configure which library the instance
listens on (like TCP/IP).
If you do a netstat -aon | find ":1433" is sql have the port open?
Hope that helps,
David Copeland
Microsoft Small Business Server Support
This posting is provided "AS IS" with no warranties, and confers no rights.
SBS Newsgroups:
SBS v4.x: microsoft.public.backoffice.smallbiz
SBS 2000: microsoft.public.backoffice.smallbiz2000
SBS 2003: microsoft.public.windows.server.sbs
"Dave" <Dave@.discussions.microsoft.com> wrote in message
news:AE297F27-ACB5-4C46-B652-9E29EE39DC0C@.microsoft.com...
> Hi Guys,
> I have a client who is running SBS2003. We are in the process of moving
an
> msde 2000 database from WIN2000 server to this server.
> We have installed MSDE 2000 and it is running on the new server. We can
> connect and access the DB locally. However, we cannot establish a
connection
> from any PCs on the network. There is no firewall between the PCs and the
> server. We have done a port scan on both servers and port 1433 is open on
> the old server and not the new one. The netstat command however says the
> port is open on the new server.
> Can anyone tell me how to open up port 1433 on the server or any other
> solutions?|||Dave,
Are you trying to get to the MSDE from the external side or internal side?
Do you have ISA installed? Is the SBS 2003 Std. Ed. or Premium Edition?
Hope that helps,
David Copeland
Microsoft Small Business Server Support
This posting is provided "AS IS" with no warranties, and confers no rights.
SBS Newsgroups:
SBS v4.x: microsoft.public.backoffice.smallbiz
SBS 2000: microsoft.public.backoffice.smallbiz2000
SBS 2003: microsoft.public.windows.server.sbs
"Dave" <Dave@.discussions.microsoft.com> wrote in message
news:AE297F27-ACB5-4C46-B652-9E29EE39DC0C@.microsoft.com...
> Hi Guys,
> I have a client who is running SBS2003. We are in the process of moving
an
> msde 2000 database from WIN2000 server to this server.
> We have installed MSDE 2000 and it is running on the new server. We can
> connect and access the DB locally. However, we cannot establish a
connection
> from any PCs on the network. There is no firewall between the PCs and the
> server. We have done a port scan on both servers and port 1433 is open on
> the old server and not the new one. The netstat command however says the
> port is open on the new server.
> Can anyone tell me how to open up port 1433 on the server or any other
> solutions?|||Hi Dave,
Use Client Network Utility from the client to configure for Network
Library(TCP/IP) and connection parameters (server name, 1433).
Ravi
"Dave" <Dave@.discussions.microsoft.com> wrote in message news:<AE297F27-ACB5-4C46-B652-9E29E
E39DC0C@.microsoft.com>...
> Hi Guys,
> I have a client who is running SBS2003. We are in the process of moving a
n
> msde 2000 database from WIN2000 server to this server.
> We have installed MSDE 2000 and it is running on the new server. We can
> connect and access the DB locally. However, we cannot establish a connect
ion
> from any PCs on the network. There is no firewall between the PCs and the
> server. We have done a port scan on both servers and port 1433 is open on
> the old server and not the new one. The netstat command however says the
> port is open on the new server.
> Can anyone tell me how to open up port 1433 on the server or any other
> solutions?|||> Are you trying to get to the MSDE from the external side or internal side?
> Do you have ISA installed? Is the SBS 2003 Std. Ed. or Premium Edition?
I am trying to access the MSDE from the internal network.
We are running SBS 2003 Std which does not include SQL server or ISA (It
sounds like it would have been a good idea to buy premium now doesn't it?)
I have run the svrnetcn.exe and TCP\IP is included. I have run the netstat
command you asked me to run and received the following information:
TCP 0.0.0.0:1433 0.0.0.0:0 Listening 5596|||Where will I find the Client Network Utility on MSDE2000? Will I need to
install MSDE onto my PC? I am using MSDE Plus 2.1 to try to establish a
connection. It works locally on the server.
I have tried creating an ODBC connection to the server, specifying port
1433, but this connection failed.
Is there a way to open port 1433 on SBS2003?
"Ravi" wrote:

> Hi Dave,
> Use Client Network Utility from the client to configure for Network
> Library(TCP/IP) and connection parameters (server name, 1433).
> Ravi
> "Dave" <Dave@.discussions.microsoft.com> wrote in message news:<AE297F27-AC
B5-4C46-B652-9E29EE39DC0C@.microsoft.com>...
>|||If you install the sql server client tools you will get this client
network utility.
"Dave" <Dave@.discussions.microsoft.com> wrote in message news:<F83A4647-58A5-4D55-8FAB-23D90
0D6070A@.microsoft.com>...[vbcol=seagreen]
> Where will I find the Client Network Utility on MSDE2000? Will I need to
> install MSDE onto my PC? I am using MSDE Plus 2.1 to try to establish a
> connection. It works locally on the server.
> I have tried creating an ODBC connection to the server, specifying port
> 1433, but this connection failed.
> Is there a way to open port 1433 on SBS2003?
> "Ravi" wrote:
>|||Dave,
At least on the server take a look at \%systemroom$\system32\cliconfg.exe.
If you run the tasklist /svc with the process id from the netstat -aon for
port 1433 does it show it as being owned by SQL? For example
netstat -aon | find ":1433"
TCP 0.0.0.0:1433 0.0.0.0:0 Listening 5596
tasklist /svc | find "5596"
You might also take a look in \program files\microsoft sql
server\instancename\log directory at the ERRORLOG files to verify that the
instance you are expecting on TCP Port 1433 is the one you expect.. since by
default SBS 2003 will install an SBSMonitoring (MSDE) and SharePoint (WMSDE)
instance (both of which are only configured to use Shared Memory)
Hope that helps,
David Copeland
Microsoft Small Business Server Support
This posting is provided "AS IS" with no warranties, and confers no rights.
SBS Newsgroups:
SBS v4.x: microsoft.public.backoffice.smallbiz
SBS 2000: microsoft.public.backoffice.smallbiz2000
SBS 2003: microsoft.public.windows.server.sbs
"Ravi" <sayravi@.yahoo.com> wrote in message
news:838d29e0.0410180905.f443d40@.posting.google.com...
> If you install the sql server client tools you will get this client
> network utility.
> "Dave" <Dave@.discussions.microsoft.com> wrote in message
news:<F83A4647-58A5-4D55-8FAB-23D900D6070A@.microsoft.com>...[vbcol=seagreen]
to[vbcol=seagreen]
news:<AE297F27-ACB5-4C46-B652-9E29EE39DC0C@.microsoft.com>...[vbcol=seagreen]
moving an[vbcol=seagreen]
can[vbcol=seagreen]
connection[vbcol=seagreen]
and the[vbcol=seagreen]
open on[vbcol=seagreen]
says the[vbcol=seagreen]
other[vbcol=seagreen]

Monday, March 19, 2012

MSDE NewBie

Dear all I did this.
I installed client version of SQL 2000 to connect to my server
(I can connect to my server and access the database there).
I installed MSDE2000RelA on my Win ME PC. Installation all
went smooth,(no errors). How do I use MSDE now. In the
enterprise manager I dont see any reference to MSDE. Am
I missing something. pls help
Joy -
Here is what you need to do.
First thing first , the network libraries are not enabled in MSDE by default
if it is a NAMED INSTANCE. In order to enable the libraries -
- Go to the Server Network Utilities of SQL Server from the Start Menu.
- Select the MSDE Instance from drop down list
- enable Named Pipes, TCP-IP and Shared Memory
- highlight TCP-IP and go to its Properties.
- if MSDE is a default instance then set the port number to 1433, but if it
is not a default instance then set the Port Number to 0. This will enable
dynamic port allocation.
- apply the above changes.
- close all client tools including Enterprise Manager and Query Analyser
- restart MSDE
- after restarting , Open Enterprise Manager
- right click on the SQL Server Group Icon, and select NEW SQL SERVER
REGISTRATION.
- give the details of the MSDE Instance.
You should be able to see the MSDE Instance in the EM . try connecting to
MSDE from Query Analyser.
This should help.
Regards
Pragya
"Joy H" wrote:

> Dear all I did this.
> I installed client version of SQL 2000 to connect to my server
> (I can connect to my server and access the database there).
> I installed MSDE2000RelA on my Win ME PC. Installation all
> went smooth,(no errors). How do I use MSDE now. In the
> enterprise manager I dont see any reference to MSDE. Am
> I missing something. pls help
|||Just to add to my previous posting, the MSDE by default does not get
registered in the Enterprise Manager. ...
"Joy H" wrote:

> Dear all I did this.
> I installed client version of SQL 2000 to connect to my server
> (I can connect to my server and access the database there).
> I installed MSDE2000RelA on my Win ME PC. Installation all
> went smooth,(no errors). How do I use MSDE now. In the
> enterprise manager I dont see any reference to MSDE. Am
> I missing something. pls help

Monday, March 12, 2012

MSDE issue

Can’t a client easily register an instance of MSDE using any third party GUI
or EM and get hold of our data structure? How can I over come this issue, if
I am installing MSDE on client computer?
thanx
hi,
"Job Lot" <JobLot@.discussions.microsoft.com> ha scritto nel messaggio
news:7002631C-B28D-4785-8C16-2EFE5D74BD50@.microsoft.com
> Can’t a client easily register an instance of MSDE using any third
> party GUI or EM and get hold of our data structure? How can I over
> come this issue, if I am installing MSDE on client computer?
> thanx
a MSDE instance can be easly registered as a linked server or in EM, from
remote (as long as the required network protocols are enabled) or local pc,
or using third party tools... as long as login privileges are set to the
logged user or a valid SQL Server login is known...
to access the databases, another issue must be granted (quite easy), that's
to say the logged user (login) is mapped to a valid database user...
if the login (both NT [trusted connections] or SQL Server [requiring "user"
and "pwd" credentials]) is member of WinNT administrators group (and thus)
or sysadmins server roles, he/she can actually do whatever he/she wants as
that membership grants illimitate privileges...
this design is part of the SQL Server security and can not be cut... so you
have to grant minimal privileges (server side) to logins in order to allow
only to specific logins the ability to access you databases..
a good article about security model is presented at
http://www.sql-server-performance.co...l_security.asp and
http://www.microsoft.com/technet/pro.../sp3sec03.mspx
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 Installation Failures

We have a custom client/server application that runs against MSDE. This
application is distributed to the field through a Setup CD. We used the
Installshield to create the setup program. Most of the times when the user
tries to install the application it fails after MSDE install saying that
"Your SQL Server is either corrupt or has been tampered with.". We try to
install a named instance. I haven't been able to find a solution to this
persistent and annoying problem. Most of my users use xp sp2 os.
Sometimes i have noticed that there is already a default instance of MSDE on
their laptops that came with some other application or the laptop itself. If
I remove that installation and then re-run our installation process it goes
smoothly.
Any help is appreciated.
Thanks
Maan
hi Maan,
Maan Thakur wrote:
> We have a custom client/server application that runs against MSDE.
> This application is distributed to the field through a Setup CD. We
> used the Installshield to create the setup program. Most of the times
> when the user tries to install the application it fails after MSDE
> install saying that "Your SQL Server is either corrupt or has been
> tampered with.". We try to install a named instance. I haven't been
> able to find a solution to this persistent and annoying problem. Most
> of my users use xp sp2 os.
> Sometimes i have noticed that there is already a default instance of
> MSDE on their laptops that came with some other application or the
> laptop itself. If I remove that installation and then re-run our
> installation process it goes smoothly.
> Any help is appreciated.
> Thanks
> Maan
you usually get this kind of exception when machine name has been changed,
like reported in
http://www.karaszi.com/sqlserver/inf...erver_name.asp
do you perform some "strange" operation at MSDE install time?
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
|||Nothing "Strange". We actually use the installation package provided by
microsoft and ship it with our CD and it is called from inside of the
installation program.
"Andrea Montanari" wrote:

> hi Maan,
> Maan Thakur wrote:
> you usually get this kind of exception when machine name has been changed,
> like reported in
> http://www.karaszi.com/sqlserver/inf...erver_name.asp
> do you perform some "strange" operation at MSDE install time?
> --
> 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 Installation failure in Windows XP

Dear all,
during an MSDE installation by a client on windows XP SP1, as well as SP2,
occurs the following error:
"InstallSQLAgentSecurity failed (IP45,LocalSystem,87)"
After this error message in the log file, one could see that the entire
installation is rolled back. The user doesn't get any message.
The server service is on.
On a windows XP SP1 by me the same installation process works fine. The
specified client has normally high security standards and it's the first time
that an MSDE is installed by them.
Any help would be highly appreciated!
Thanks in advance for the help,
Avi Joshua
CRM systems consultant
LOGO consult AG
Head office
Enzianstrasse 4a
82319 Starnberg am See
Germany
mailto:avi@.logo-consult.de
tel +49 (0700) 100 55 100
Hi Avi,
Check that Sharing is enabled on the system.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Avi Joshua" <Avi Joshua@.discussions.microsoft.com> wrote in message
news:CFA84BD4-18A8-4AC4-8AEE-B065ED28E77E@.microsoft.com...
> Dear all,
> during an MSDE installation by a client on windows XP SP1, as well as SP2,
> occurs the following error:
> "InstallSQLAgentSecurity failed (IP45,LocalSystem,87)"
> After this error message in the log file, one could see that the entire
> installation is rolled back. The user doesn't get any message.
> The server service is on.
> On a windows XP SP1 by me the same installation process works fine. The
> specified client has normally high security standards and it's the first
time
> that an MSDE is installed by them.
> Any help would be highly appreciated!
> Thanks in advance for the help,
> Avi Joshua
> CRM systems consultant
> LOGO consult AG
> Head office
> Enzianstrasse 4a
> 82319 Starnberg am See
> Germany
> mailto:avi@.logo-consult.de
> tel +49 (0700) 100 55 100
>
|||Thanks, Greg!
The file and printer sharing component was not installed on the computer.
Have a pleasant weekend,
Avi

Wednesday, March 7, 2012

MSDE Installation and usage on client PC. URGENT HELP!

Hi All,
Have developed Client/Server (VB.NET) application with SQL Server 2000
backend engine. It is working fine. This application can connect to
Database engine if user in our LAN or WAN.
Now, my users need to work on application while they are not in our
network. For instance from Hotel, travel etc.. To achieve this, I
thought to have MSDE installed on user's laptop and get copy of SQL 2k
DB on user machine. But. here I got stuck !. Woudl really appreciate if
you could help me !
MSDE engine, I hope that I can d/load from MS site. Belive that can be
installed easly like other MS application. Upon installation, how can I
get my SQL 2K DB attached or Sychronized ?
What about login id (like "sa") to connect to MSDE engine from my
applciation. I will modify my application user to choose DB engine LOCAL
or LAN. If LAN, I will use my existing connection string. But, LOCAL,
what would be the provider, password, user id etc..
Never user MSDE, so queries will be bit more.
Appreciate all your help to get this resolved.
Many thanks in advance..
Regards,
AJ
*** Sent via Developersdex http://www.developersdex.com ***You have to setup some replication, please refer to the BOL or ressources in
the internet for that, there are tons of examples out there.
HTH, Jens SUessmeyer.
--
http://www.sqlserver2005.de
--
"Ahmed Jewahar" <ahmed.jewahar@.dhl.com> schrieb im Newsbeitrag
news:%23klgAGhWFHA.3280@.TK2MSFTNGP09.phx.gbl...
> Hi All,
> Have developed Client/Server (VB.NET) application with SQL Server 2000
> backend engine. It is working fine. This application can connect to
> Database engine if user in our LAN or WAN.
> Now, my users need to work on application while they are not in our
> network. For instance from Hotel, travel etc.. To achieve this, I
> thought to have MSDE installed on user's laptop and get copy of SQL 2k
> DB on user machine. But. here I got stuck !. Woudl really appreciate if
> you could help me !
> MSDE engine, I hope that I can d/load from MS site. Belive that can be
> installed easly like other MS application. Upon installation, how can I
> get my SQL 2K DB attached or Sychronized ?
> What about login id (like "sa") to connect to MSDE engine from my
> applciation. I will modify my application user to choose DB engine LOCAL
> or LAN. If LAN, I will use my existing connection string. But, LOCAL,
> what would be the provider, password, user id etc..
> Never user MSDE, so queries will be bit more.
> Appreciate all your help to get this resolved.
> Many thanks in advance..
> Regards,
> AJ
>
>
> *** Sent via Developersdex http://www.developersdex.com ***

MSDE Installation and usage on client PC. URGENT HELP!

Hi All,
Have developed Client/Server (VB.NET) application with SQL Server 2000
backend engine. It is working fine. This application can connect to
Database engine if user in our LAN or WAN.
Now, my users need to work on application while they are not in our
network. For instance from Hotel, travel etc.. To achieve this, I
thought to have MSDE installed on user's laptop and get copy of SQL 2k
DB on user machine. But. here I got stuck !. Woudl really appreciate if
you could help me !
MSDE engine, I hope that I can d/load from MS site. Belive that can be
installed easly like other MS application. Upon installation, how can I
get my SQL 2K DB attached or Sychronized ?
What about login id (like "sa") to connect to MSDE engine from my
applciation. I will modify my application user to choose DB engine LOCAL
or LAN. If LAN, I will use my existing connection string. But, LOCAL,
what would be the provider, password, user id etc..
Never user MSDE, so queries will be bit more.
Appreciate all your help to get this resolved.
Many thanks in advance..
Regards,
AJ
*** Sent via Developersdex http://www.codecomments.com ***
You have to setup some replication, please refer to the BOL or ressources in
the internet for that, there are tons of examples out there.
HTH, Jens SUessmeyer.
http://www.sqlserver2005.de
"Ahmed Jewahar" <ahmed.jewahar@.dhl.com> schrieb im Newsbeitrag
news:%23klgAGhWFHA.3280@.TK2MSFTNGP09.phx.gbl...
> Hi All,
> Have developed Client/Server (VB.NET) application with SQL Server 2000
> backend engine. It is working fine. This application can connect to
> Database engine if user in our LAN or WAN.
> Now, my users need to work on application while they are not in our
> network. For instance from Hotel, travel etc.. To achieve this, I
> thought to have MSDE installed on user's laptop and get copy of SQL 2k
> DB on user machine. But. here I got stuck !. Woudl really appreciate if
> you could help me !
> MSDE engine, I hope that I can d/load from MS site. Belive that can be
> installed easly like other MS application. Upon installation, how can I
> get my SQL 2K DB attached or Sychronized ?
> What about login id (like "sa") to connect to MSDE engine from my
> applciation. I will modify my application user to choose DB engine LOCAL
> or LAN. If LAN, I will use my existing connection string. But, LOCAL,
> what would be the provider, password, user id etc..
> Never user MSDE, so queries will be bit more.
> Appreciate all your help to get this resolved.
> Many thanks in advance..
> Regards,
> AJ
>
>
> *** Sent via Developersdex http://www.codecomments.com ***

MSDE Installation and usage on client PC. URGENT HELP!

Hi All,
Have developed Client/Server (VB.NET) application with SQL Server 2000
backend engine. It is working fine. This application can connect to
Database engine if user in our LAN or WAN.
Now, my users need to work on application while they are not in our
network. For instance from Hotel, travel etc.. To achieve this, I
thought to have MSDE installed on user's laptop and get copy of SQL 2k
DB on user machine. But. here I got stuck !. Woudl really appreciate if
you could help me !
MSDE engine, I hope that I can d/load from MS site. Belive that can be
installed easly like other MS application. Upon installation, how can I
get my SQL 2K DB attached or Sychronized ?
What about login id (like "sa") to connect to MSDE engine from my
applciation. I will modify my application user to choose DB engine LOCAL
or LAN. If LAN, I will use my existing connection string. But, LOCAL,
what would be the provider, password, user id etc..
Never user MSDE, so queries will be bit more.
Appreciate all your help to get this resolved.
Many thanks in advance..
Regards,
AJ
*** Sent via Developersdex http://www.codecomments.com ***You have to setup some replication, please refer to the BOL or ressources in
the internet for that, there are tons of examples out there.
HTH, Jens SUessmeyer.
http://www.sqlserver2005.de
--
"Ahmed Jewahar" <ahmed.jewahar@.dhl.com> schrieb im Newsbeitrag
news:%23klgAGhWFHA.3280@.TK2MSFTNGP09.phx.gbl...
> Hi All,
> Have developed Client/Server (VB.NET) application with SQL Server 2000
> backend engine. It is working fine. This application can connect to
> Database engine if user in our LAN or WAN.
> Now, my users need to work on application while they are not in our
> network. For instance from Hotel, travel etc.. To achieve this, I
> thought to have MSDE installed on user's laptop and get copy of SQL 2k
> DB on user machine. But. here I got stuck !. Woudl really appreciate if
> you could help me !
> MSDE engine, I hope that I can d/load from MS site. Belive that can be
> installed easly like other MS application. Upon installation, how can I
> get my SQL 2K DB attached or Sychronized ?
> What about login id (like "sa") to connect to MSDE engine from my
> applciation. I will modify my application user to choose DB engine LOCAL
> or LAN. If LAN, I will use my existing connection string. But, LOCAL,
> what would be the provider, password, user id etc..
> Never user MSDE, so queries will be bit more.
> Appreciate all your help to get this resolved.
> Many thanks in advance..
> Regards,
> AJ
>
>
> *** Sent via Developersdex http://www.codecomments.com ***

Saturday, February 25, 2012

MSDE Install Failure - error code 6

During one of our client's install of MSDE 2000, they are getting this error message in thier install log:
Registering performance counters from sqlctr.ini
PerfmonLoad routine returned error code 6
Action ended 12:07:55: InstallFinalize. Return value 3.

MSI (s) (10:FC): Product: Microsoft SQL Server Desktop Engine -- Installation operation failed.

Does anyone have any idea on how to fix it?

thanks,

DanielWas there ever a reply or fix for this?

Thanks,
BD

Originally posted by DanielP
During one of our client's install of MSDE 2000, they are getting this error message in thier install log:
Registering performance counters from sqlctr.ini
PerfmonLoad routine returned error code 6
Action ended 12:07:55: InstallFinalize. Return value 3.

MSI (s) (10:FC): Product: Microsoft SQL Server Desktop Engine -- Installation operation failed.

Does anyone have any idea on how to fix it?

thanks,

Daniel