Is there a MSDE available for Pocket PCs like SQL Server CE?
"William Gower" <w_gower@.hotmail.com> wrote in message
news:%23AikcBIhEHA.712@.TK2MSFTNGP09.phx.gbl...
> Is there a MSDE available for Pocket PCs like SQL Server CE?
>
Not to my knowledge, you'd need to used the SQL Server CE for the Pocket pc
platform... of course you could always develop on a desktop OS with MSDE and
port your db's over to CE.
Steve
|||William,
Pretty much SqlCe *is* the MSDE of PocketPCs. Admittedly it's not as
functional as MSDE, but the PocketPC is also a lot smaller than a desktop
machine. Future versions of SqlCe will be installed in ROM on future Windows
Mobile devices, so that's definitely the standard.
Ginny Caughey
..Net Compact Framework MVP
"William Gower" <w_gower@.hotmail.com> wrote in message
news:%23AikcBIhEHA.712@.TK2MSFTNGP09.phx.gbl...
> Is there a MSDE available for Pocket PCs like SQL Server CE?
>
Showing posts with label pcs. Show all posts
Showing posts with label pcs. Show all posts
Wednesday, March 21, 2012
MSDE ODBC connection fails
I have 3 PCs on a LAN.
PC 1 has MSDE installed
PC 2 has MSDE installed
PC 3 doesn't have MSDE installed
I can set-up an ODBC connection through TCP/IP port and named pipes from PC
1 to PC 2 and vice versa.
The same TCP/IP ODBC details are used on PC 3 to connect to MSDE on PC 1 and
2 but the connection always fails. The named pipe connection works.
Originally PC 2 did not have MSDE installed and a TCP/IP ODBC connection
could not be made to PC 1 either. Once MSDE was installed the TCP/IP ODBC
connection worked.
Any ideas what the problem is here?
I know that by default MSDE is not set-up to allow access from a client
across the network but when I installed MSDE I used these switch commands to
allow it:
cd c:\MSDERelA
setup SAPWD="whatever" INSTANCENAME="PC1MSDE" TARGETDIR="C:\MSDE"
SECURITYMODE=SQL DISABLENETWORKPROTOCOLS=0 /L*v C:/MSDELog.log
At first I thought perhaps MSDE was listening on a different port to what it
was reporting but the MSDE log that is generated when the service starts and
svrnetcn.exe both indicate the same socket is being used. I have tried using
a different port.
I notice that when MSDE is installed, there is an extra option in the ODBC
TCP/IP dialog window 'dynamically determine port' and wondered if this had
anything to do with the problem? However, it doesn't seem to make a
difference because PC 1 and PC 2 can connect to each other with or without
this option enabled.
I found this article http://support.microsoft.com/kb/306865 which explains
how SQL Server 2000 may not be listening on TCP/IP sockets but the registry
keys again indicate that the correct port is being used.
FYI, I am using MSDE 2000. PC2 has been upgraded to MSDE2000 SP4 but that
hasn't resolved the issue. All 3 PCs are W2K Pro so no firewall issues.
I'm a bit stuck as to what else to try.
Ha, ha, ha - sorted it!
I installed the latest MDAC from
http://www.microsoft.com/downloads/d...DisplayLang=en
on PC 3 which didn't have MSDE installed and I can now make an ODBC
connection to any MSDE on the network.
The Microsoft Access Data Components include an updated SQL Server ODBC
driver.
Good way to end a Friday afternoon.
"Swaffs" wrote:
> I have 3 PCs on a LAN.
> PC 1 has MSDE installed
> PC 2 has MSDE installed
> PC 3 doesn't have MSDE installed
> I can set-up an ODBC connection through TCP/IP port and named pipes from PC
> 1 to PC 2 and vice versa.
> The same TCP/IP ODBC details are used on PC 3 to connect to MSDE on PC 1 and
> 2 but the connection always fails. The named pipe connection works.
> Originally PC 2 did not have MSDE installed and a TCP/IP ODBC connection
> could not be made to PC 1 either. Once MSDE was installed the TCP/IP ODBC
> connection worked.
> Any ideas what the problem is here?
> I know that by default MSDE is not set-up to allow access from a client
> across the network but when I installed MSDE I used these switch commands to
> allow it:
> cd c:\MSDERelA
> setup SAPWD="whatever" INSTANCENAME="PC1MSDE" TARGETDIR="C:\MSDE"
> SECURITYMODE=SQL DISABLENETWORKPROTOCOLS=0 /L*v C:/MSDELog.log
>
> At first I thought perhaps MSDE was listening on a different port to what it
> was reporting but the MSDE log that is generated when the service starts and
> svrnetcn.exe both indicate the same socket is being used. I have tried using
> a different port.
> I notice that when MSDE is installed, there is an extra option in the ODBC
> TCP/IP dialog window 'dynamically determine port' and wondered if this had
> anything to do with the problem? However, it doesn't seem to make a
> difference because PC 1 and PC 2 can connect to each other with or without
> this option enabled.
> I found this article http://support.microsoft.com/kb/306865 which explains
> how SQL Server 2000 may not be listening on TCP/IP sockets but the registry
> keys again indicate that the correct port is being used.
> FYI, I am using MSDE 2000. PC2 has been upgraded to MSDE2000 SP4 but that
> hasn't resolved the issue. All 3 PCs are W2K Pro so no firewall issues.
> I'm a bit stuck as to what else to try.
>
PC 1 has MSDE installed
PC 2 has MSDE installed
PC 3 doesn't have MSDE installed
I can set-up an ODBC connection through TCP/IP port and named pipes from PC
1 to PC 2 and vice versa.
The same TCP/IP ODBC details are used on PC 3 to connect to MSDE on PC 1 and
2 but the connection always fails. The named pipe connection works.
Originally PC 2 did not have MSDE installed and a TCP/IP ODBC connection
could not be made to PC 1 either. Once MSDE was installed the TCP/IP ODBC
connection worked.
Any ideas what the problem is here?
I know that by default MSDE is not set-up to allow access from a client
across the network but when I installed MSDE I used these switch commands to
allow it:
cd c:\MSDERelA
setup SAPWD="whatever" INSTANCENAME="PC1MSDE" TARGETDIR="C:\MSDE"
SECURITYMODE=SQL DISABLENETWORKPROTOCOLS=0 /L*v C:/MSDELog.log
At first I thought perhaps MSDE was listening on a different port to what it
was reporting but the MSDE log that is generated when the service starts and
svrnetcn.exe both indicate the same socket is being used. I have tried using
a different port.
I notice that when MSDE is installed, there is an extra option in the ODBC
TCP/IP dialog window 'dynamically determine port' and wondered if this had
anything to do with the problem? However, it doesn't seem to make a
difference because PC 1 and PC 2 can connect to each other with or without
this option enabled.
I found this article http://support.microsoft.com/kb/306865 which explains
how SQL Server 2000 may not be listening on TCP/IP sockets but the registry
keys again indicate that the correct port is being used.
FYI, I am using MSDE 2000. PC2 has been upgraded to MSDE2000 SP4 but that
hasn't resolved the issue. All 3 PCs are W2K Pro so no firewall issues.
I'm a bit stuck as to what else to try.
Ha, ha, ha - sorted it!
I installed the latest MDAC from
http://www.microsoft.com/downloads/d...DisplayLang=en
on PC 3 which didn't have MSDE installed and I can now make an ODBC
connection to any MSDE on the network.
The Microsoft Access Data Components include an updated SQL Server ODBC
driver.
Good way to end a Friday afternoon.
"Swaffs" wrote:
> I have 3 PCs on a LAN.
> PC 1 has MSDE installed
> PC 2 has MSDE installed
> PC 3 doesn't have MSDE installed
> I can set-up an ODBC connection through TCP/IP port and named pipes from PC
> 1 to PC 2 and vice versa.
> The same TCP/IP ODBC details are used on PC 3 to connect to MSDE on PC 1 and
> 2 but the connection always fails. The named pipe connection works.
> Originally PC 2 did not have MSDE installed and a TCP/IP ODBC connection
> could not be made to PC 1 either. Once MSDE was installed the TCP/IP ODBC
> connection worked.
> Any ideas what the problem is here?
> I know that by default MSDE is not set-up to allow access from a client
> across the network but when I installed MSDE I used these switch commands to
> allow it:
> cd c:\MSDERelA
> setup SAPWD="whatever" INSTANCENAME="PC1MSDE" TARGETDIR="C:\MSDE"
> SECURITYMODE=SQL DISABLENETWORKPROTOCOLS=0 /L*v C:/MSDELog.log
>
> At first I thought perhaps MSDE was listening on a different port to what it
> was reporting but the MSDE log that is generated when the service starts and
> svrnetcn.exe both indicate the same socket is being used. I have tried using
> a different port.
> I notice that when MSDE is installed, there is an extra option in the ODBC
> TCP/IP dialog window 'dynamically determine port' and wondered if this had
> anything to do with the problem? However, it doesn't seem to make a
> difference because PC 1 and PC 2 can connect to each other with or without
> this option enabled.
> I found this article http://support.microsoft.com/kb/306865 which explains
> how SQL Server 2000 may not be listening on TCP/IP sockets but the registry
> keys again indicate that the correct port is being used.
> FYI, I am using MSDE 2000. PC2 has been upgraded to MSDE2000 SP4 but that
> hasn't resolved the issue. All 3 PCs are W2K Pro so no firewall issues.
> I'm a bit stuck as to what else to try.
>
Monday, March 19, 2012
MSDE Maximum Connections
Quick question on MSDE maximum connections. If you use MSDE on several and
the MSDE on each computers is pointing to one PCs MSDE, does that mean they
are always connected regardless if the software you are using is requesting
data or not? Meaning if you have 5 PCs pointing to one PC's MSDE, does that
mean there are 5 constant concurrent connections?
Also, if this is the case, whats the max connections you can have?
Thanks,
Matt
There is no limitation in connections; but in MSDE the performance will slow
down if you have more than 5 concurrent batch (connections) running.
After the 5th batch the Query Governer will stop working and will degrade
performance.
If 5 machines are connected using an application to MSDE, yes there will be
5 connections.
Thanks
Hari
"medentmatt" <mattd@.medent(dot)com.(donotspam)> wrote in message
news:CDDC7137-2D58-436B-967B-CF1A6111FD1E@.microsoft.com...
> Quick question on MSDE maximum connections. If you use MSDE on several and
> the MSDE on each computers is pointing to one PCs MSDE, does that mean
> they
> are always connected regardless if the software you are using is
> requesting
> data or not? Meaning if you have 5 PCs pointing to one PC's MSDE, does
> that
> mean there are 5 constant concurrent connections?
> Also, if this is the case, whats the max connections you can have?
> --
> Thanks,
> Matt
|||"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:ep%23Obh4SHHA.5016@.TK2MSFTNGP05.phx.gbl...
> There is no limitation in connections; but in MSDE the performance will
> slow down if you have more than 5 concurrent batch (connections) running.
> After the 5th batch the Query Governer will stop working and will degrade
> performance.
> If 5 machines are connected using an application to MSDE, yes there will
> be 5 connections.
It also depends on how the application that access MSDE is designed. If it
is designed in a ideal way, that is, connect to database server only needed
and close the connection as soon as the access is done. Then even with
MSDE's 5 concurrent work load limitation, an MSDE can well serve a lot more
users who need to access data from time to time 20, 50 or even hundreds,
really depends how the the data is accessed.
the MSDE on each computers is pointing to one PCs MSDE, does that mean they
are always connected regardless if the software you are using is requesting
data or not? Meaning if you have 5 PCs pointing to one PC's MSDE, does that
mean there are 5 constant concurrent connections?
Also, if this is the case, whats the max connections you can have?
Thanks,
Matt
There is no limitation in connections; but in MSDE the performance will slow
down if you have more than 5 concurrent batch (connections) running.
After the 5th batch the Query Governer will stop working and will degrade
performance.
If 5 machines are connected using an application to MSDE, yes there will be
5 connections.
Thanks
Hari
"medentmatt" <mattd@.medent(dot)com.(donotspam)> wrote in message
news:CDDC7137-2D58-436B-967B-CF1A6111FD1E@.microsoft.com...
> Quick question on MSDE maximum connections. If you use MSDE on several and
> the MSDE on each computers is pointing to one PCs MSDE, does that mean
> they
> are always connected regardless if the software you are using is
> requesting
> data or not? Meaning if you have 5 PCs pointing to one PC's MSDE, does
> that
> mean there are 5 constant concurrent connections?
> Also, if this is the case, whats the max connections you can have?
> --
> Thanks,
> Matt
|||"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:ep%23Obh4SHHA.5016@.TK2MSFTNGP05.phx.gbl...
> There is no limitation in connections; but in MSDE the performance will
> slow down if you have more than 5 concurrent batch (connections) running.
> After the 5th batch the Query Governer will stop working and will degrade
> performance.
> If 5 machines are connected using an application to MSDE, yes there will
> be 5 connections.
It also depends on how the application that access MSDE is designed. If it
is designed in a ideal way, that is, connect to database server only needed
and close the connection as soon as the access is done. Then even with
MSDE's 5 concurrent work load limitation, an MSDE can well serve a lot more
users who need to access data from time to time 20, 50 or even hundreds,
really depends how the the data is accessed.
Saturday, February 25, 2012
MSDE HELP
Hi,
I have 2 PCs that aren't in any domain.
One of PCs, have installed on MSDE. I change the authentication
mode from windows to mixed mode.
Created users inside MSDE.
In the PC with MSDE I can enter with all users, but in the other PC I could
not connect to the server.
I tried to register in Enterprise Manager that MSDE instalation and I get
the following error
SQL Server Enterprise Manager
SQL Server registration failed because of the connection failure displayed
below. Do you wish to Register anyway?
SQL Server does not exist or access denied.
ConnectionOpen (Connect())
Yes No
I already add the TCP 1433 and UDP 1434 ports to windows firewal, I tried to
with the firewall disconected and i get always the same error.
So I think the problem could be in permissions, but how can I set permisons
in one computer to a user from another computer. Don't forget that the pcs
aren't in any domain.
Or how can I put on PC connecting to the MSDE in the other PC?
thanks
Mestre
hi Mestre,
Mestre wrote:
> Hi,
> I have 2 PCs that aren't in any domain.
> One of PCs, have installed on MSDE. I change the authentication
> mode from windows to mixed mode.
> Created users inside MSDE.
> In the PC with MSDE I can enter with all users, but in the other PC I
> could not connect to the server.
> I tried to register in Enterprise Manager that MSDE instalation and I
> get the following error
> --
> SQL Server Enterprise Manager
> --
> SQL Server registration failed because of the connection failure
> displayed below. Do you wish to Register anyway?
> SQL Server does not exist or access denied.
> ConnectionOpen (Connect())
> --
> Yes No
> --
>
> I already add the TCP 1433 and UDP 1434 ports to windows firewal, I
> tried to with the firewall disconected and i get always the same
> error.
> So I think the problem could be in permissions, but how can I set
> permisons in one computer to a user from another computer. Don't
> forget that the pcs aren't in any domain.
> Or how can I put on PC connecting to the MSDE in the other PC?
please have a look at
http://support.microsoft.com/default...06&Product=sql
for the most common causes of this exception.. and of course please verify
that remote access to the instance is enabled with the Server Network
Utility (svrnetcn.exe) as MSDE installs by default disabling all network
protocols...
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,
you're right. I discover that, but I ony have time to update the posts
today.
Thanks,
Mestre
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:4271egF1hrbv5U1@.individual.net...
> hi Mestre,
> Mestre wrote:
> please have a look at
> http://support.microsoft.com/default...06&Product=sql
> for the most common causes of this exception.. and of course please verify
> that remote access to the instance is enabled with the Server Network
> Utility (svrnetcn.exe) as MSDE installs by default disabling all network
> protocols...
> --
> 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
>
I have 2 PCs that aren't in any domain.
One of PCs, have installed on MSDE. I change the authentication
mode from windows to mixed mode.
Created users inside MSDE.
In the PC with MSDE I can enter with all users, but in the other PC I could
not connect to the server.
I tried to register in Enterprise Manager that MSDE instalation and I get
the following error
SQL Server Enterprise Manager
SQL Server registration failed because of the connection failure displayed
below. Do you wish to Register anyway?
SQL Server does not exist or access denied.
ConnectionOpen (Connect())
Yes No
I already add the TCP 1433 and UDP 1434 ports to windows firewal, I tried to
with the firewall disconected and i get always the same error.
So I think the problem could be in permissions, but how can I set permisons
in one computer to a user from another computer. Don't forget that the pcs
aren't in any domain.
Or how can I put on PC connecting to the MSDE in the other PC?
thanks
Mestre
hi Mestre,
Mestre wrote:
> Hi,
> I have 2 PCs that aren't in any domain.
> One of PCs, have installed on MSDE. I change the authentication
> mode from windows to mixed mode.
> Created users inside MSDE.
> In the PC with MSDE I can enter with all users, but in the other PC I
> could not connect to the server.
> I tried to register in Enterprise Manager that MSDE instalation and I
> get the following error
> --
> SQL Server Enterprise Manager
> --
> SQL Server registration failed because of the connection failure
> displayed below. Do you wish to Register anyway?
> SQL Server does not exist or access denied.
> ConnectionOpen (Connect())
> --
> Yes No
> --
>
> I already add the TCP 1433 and UDP 1434 ports to windows firewal, I
> tried to with the firewall disconected and i get always the same
> error.
> So I think the problem could be in permissions, but how can I set
> permisons in one computer to a user from another computer. Don't
> forget that the pcs aren't in any domain.
> Or how can I put on PC connecting to the MSDE in the other PC?
please have a look at
http://support.microsoft.com/default...06&Product=sql
for the most common causes of this exception.. and of course please verify
that remote access to the instance is enabled with the Server Network
Utility (svrnetcn.exe) as MSDE installs by default disabling all network
protocols...
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,
you're right. I discover that, but I ony have time to update the posts
today.
Thanks,
Mestre
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:4271egF1hrbv5U1@.individual.net...
> hi Mestre,
> Mestre wrote:
> please have a look at
> http://support.microsoft.com/default...06&Product=sql
> for the most common causes of this exception.. and of course please verify
> that remote access to the instance is enabled with the Server Network
> Utility (svrnetcn.exe) as MSDE installs by default disabling all network
> protocols...
> --
> 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
>
Subscribe to:
Posts (Atom)