SQLserver connect ????

[mikeb]

I have Intermec 750 scanners and 3 different sql server databases on 3
different PCs. The scanner can connect to 2 pc's databases, but not
another (the 'other' is a laptop with a wireless connection). Its
intermittent - we have been able to get it to connect once today - but no
more.

This same scanner will connect to other pc's easily. Enterprise manager
from other PCs can connect to the laptop's database. Other scanners with
the same program can connect to the other sql server, but not the laptop's.

I have the firewall and antivirus open to accept sqlserver.exe and the ports
are open. I'm ready to uninstall antivirus (Norton AV 2005) - but I
question why we were able to connect once today - a firewall, if its not
goign to allow it, should never allow it - right??

This is a common problem with our customer base - some of these units we can
resolve others we just cannot. And the one's we do get working for the
customers, we are pretty much surprised when it actually does work as
nothing we did was outside our typical installs......

Another PC can access this server, but the scanners cannot. Any ideas why
that would be?? what is going on behind the scenes in WM2003 when a sql
server conneciton is attempted??

 

[Paul G. Tobey [eMVP]]

Mike,

I see below that you're asking about contacting MS about this and it's
certainly possible that that might help, but it sounds to me as though the
answer is out there, but perhaps shielded by some fog.

Here are the things that I think might be significant for us to know that
you've not told us:

1. You have 750 devices. Are *all* of these devices trying successfully to
reach 2 of the 3 databases, and unsuccessfully trying to reach 1 of the 3?
If so, this is extremely good news.

2. Tell us what version of SQL Server is running on which server devices.
Tell us what operating systems are running on those SQL Server devices?
What about the WM devices? Are they *all* running the same OS and version
of the OS?

3. What is the network topology that we're talking about? All WM devices
are using 802.11b? What about this 'other PC' that can access the problem
server? What about the other server PCs? Are they connected wirelessly?
Are all of these devices connected on the same Ethernet subnet? Are they
all assigned static IP addresses? All assigned via DHCP, instead of static?

There are other things that I can think of, but we can start progressing in
the direction of the solution if we can get true answers to these questions,
I think.

Paul T.

 

[mikeb]

Thanks Paul ... I'll try to answer inline... THANKS!

Mike,

I see below that you're asking about contacting MS about this and it's
certainly possible that that might help, but it sounds to me as though the
answer is out there, but perhaps shielded by some fog.

Here are the things that I think might be significant for us to know that
you've not told us:

1. You have 750 devices. Are *all* of these devices trying successfully
to reach 2 of the 3 databases, and unsuccessfully trying to reach 1 of the
3? If so, this is extremely good news.

No, unfortunatley, thats not the case. Its appearing to be sort of
random... (bad explanation I know). We have 3 pc's. 2 of the 3 are
running SQL Server and all 3 of them have an MSDE database on them. At the
moment we're trying to connect to the MSDEs - but the SQLservers are showing
the same it seems.

(as you can tell by my explanations, things are happening so random that
we're having a hard time explaining it)

On PC1 (Dell WinXP sp2 laptop) - none of our PPC devices can seem to connect
to the MSDE or SQLserver database - but just recently (now, during testing
for this message) one of them started to give a successful connection to the
sqlserver database, but still not the msde.

For PC2 (W2k3Server), all devices can connect to its sql server and msde
database.

For PC3 (WinXP sp2 desktop), very random connections - some devices can
connect, others cannot - and at different times.

In the past, it seemed that changing the PCname to an IP Address in the conn
string helped get connections to connect, but not today.

2. Tell us what version of SQL Server is running on which server devices.
Tell us what operating systems are running on those SQL Server devices?
What about the WM devices? Are they *all* running the same OS and version
of the OS?

PC1
- WinXP sp2
- SqlServer2k v8.00.760
- MSDE2000 v8.00.2039 (was 8.00.760 until today, but tried to resolve wth
sp4 upgr - no go)
- Norton Antivirus 2005 (firewall is open for sqlserver and msde)
Also uninstalled NAV, rebooted, and still no connection

PC2
- Win2K3server SP1 (however SP1 was seriously flawed on install and MS is
working to fix it)
- SqlServer2k v8.00.760
- MSDE2000 v8.00.760
- Tiny Firewall Pro (open for sqlserver and msde)
- ClamWin AV

PC3
- WinXP sp2
- SqlServer2k v8.00.760
- MSDE2000 v8.00.760
- Norton Antivirus 2005 (firewall is open for sqlserver and msde)


PPCs are all currently the same (in my office anyway)
- Build v4.41 Premium
- PSM Build v3.65

3. What is the network topology that we're talking about? All WM devices
are using 802.11b?

We've tried each device on 802.11b/g and wired - same crud.

What about this 'other PC' that can access the problem server?

What I meant by that, was that each PC can access each other's
sqlserver/msde using EnterpriseMgr and QueryAnalyzer - with no issue.

What about the other server PCs? Are they connected wirelessly?

All are wired PCs. The laptop (PC1) is wireless, but we've tested by
disabling the wirelss conn and hardwiring it. Same issue.

Are all of these devices connected on the same Ethernet subnet? YES

Are they all assigned static IP addresses? All assigned via DHCP, instead
of static?

DHCP with exception of server that is static. I can't force my users to
change to static tho...

There are other things that I can think of, but we can start progressing
in the direction of the solution if we can get true answers to these
questions, I think.

I'm installing at another site on Monday - plane ride across the country....
I thought we were done and tested... But this is cropping up on similar
apps that we have installed across Asia now too. I personally think this is
an issue that someone somewhere (ms) knows about.

Paul T.

Thanks Paul

 

[Paul G. Tobey [eMVP]]

Mike,

1. I would *definitely* use IP addresses, not names. Especially since it
doesn't seem to me that you're going to be able to resolve those names
reliably. You have to think about *who*, if anyone, is going to know that
SQLServerPC1 is actually 172.16.0.47. If you can't statically assign the IP
for the servers, maybe you can figure out a way to use the registry/hosts
list to do the translation and update it occasionally or whatever, via other
means.

2. Good. Everything is pretty consistent.

3. OK. This all sounds fine. It would be worthwhile, in the case of WM
device A which is unable to connect to the server, to check whether it can
do *any* network I/O (if you open the network connection applet, does it
have an IP address, can it ping anyone on the network, etc.) DHCP, over the
years, has had far more problems than static IP addressing, because there's
more for the stack to do. You have to keep track of a lease, request a
renewal when the lease is running down, handle the case where the lease
can't be renewed immediately, etc.

Can we assume that this is not a client access license problem with SQL
Server or something like that? Are the Windows XP devices XP Pro?

Paul T.

 

[Ilya Tumanov [MS]]

Do you have WINS or DNS servers? If yes, is DHCP properly configured to
include this information?
If you can't connect, can you ping the server by name/IP (free vxUtil will
help checking this out).
Can you reach connections limit for OS/MSDE?

Best regards,

Ilya

This posting is provided "AS IS" with no warranties, and confers no rights.

*** Want to find answers instantly? Here's how... ***

1. Go to
http://groups-beta.google.com/group/microsoft.public.dotnet.framework.compactframework?hl=en
2. Type your question in the text box near "Search this group" button.
3. Hit "Search this group" button.
4. Read answer(s).

 

[mikeb]

1. Yes, on IP addressing, I keep forgetting this is a server pc (sql
server) - in my office, they''re simply dev pc's - I got sidetracked.
You're right, they'll be static in the field. And we are recommending
static ip's for the pc's hosting our msde servers.

2.

3. I should have mentioned that - but yes, we're able to ping the devices
from all computers and ping the computers from all the devices. That was an
important piece of info that I left out.

Client Access Licensing
Hmmm. Good thinking. I'm doubtful on that though. We are a very small
shop and our app only connects and then disconnects. I'm not sure if EM or
QA use up a license, but I suspect they do, still doubtful that its
overaging our license. Would SQLserver give a different message than
'specified sql server not found' if its a licnese issue??

Good point tho.

-Mike

 

[mikeb]

Do you have WINS or DNS servers? If yes, is DHCP properly configured to
include this information?
If you can't connect, can you ping the server by name/IP (free vxUtil will
help checking this out).

I can ping each device from each pc - and can ping each pc from each device.
Doesn't seem to be a networking issue, as far as addressing anyway.

Can you reach connections limit for OS/MSDE?

You and Paul bring up a good point here - but I"m not sure. Is there any
way to tell if some connections are lingering? Thats the only way I can see
this being so. What is the connection limit of MSDE? Seems like it was
pretty large. I'm only trying to connect 4 devices to 3 msde databases
here.

The Win2k3 server (only a file server) has a 5 user license, but none of the
devices are attaching to that particular server - as users when we're
testing the sql server connection anyway.

Maybe I'm green on this tho - please do tell me if I'm missing something.

-m

 

[mikeb]

Well, we uninstalled the MSDE instance, and cold booted each device and
reinstalled the software - they can now connect to the servers...........

As much as this sounds like a happy occasion - I'm still not satisfied and
still very concerned as to the Why it happened.

Further thoughts? We still have a lot of devices installed that experience
this on occasion. Supporting it is confusing - and I can't just have them
uninstall their data filled msde databases to remedy the problem.

Yikes. But definitely, thanks for the helpful ideas!

-m