Solved

Windows CE 5.0 connecting to MSSQL 2005 64 bit

Posted on 2009-04-14
2
287 Views
Last Modified: 2012-05-06
Hi all.

We have a client that installed a MS SQL 2005 64bit DB on a server. We traditionally use only the 32 bit version so this is a new field for us. But first, a quick walkthrough.

We have proprietary software which various devices connect to. It's simply a production database running behind it, the interface and backend is all Microsoft based. That is, MSSQL DB, Windows server etc.
We have scanners which can be either CE or Windows mobile. On the scanners, we install a program which handles the communication with the SQL server (sending the barcode string to correct  receiver).

When testing this 64 bit server I haven't come across any problems except with the scanner. When I select the program it gives me the standard generic SQL Connection error. Unfortunately I do not have a screenshot or a test that I can post, I hope that will not be a problem. But basically it is "

Now, my question is, do I need to have my connection string reprogrammed/redone whatever by the programmers or is this something more sinister, like there not being a DLL that handles communication of this type? Sorry for this maybe a stupid question, but I haven't been able to find anything relevant by googling.

Thanks.
0
Comment
Question by:rattati
2 Comments
 
LVL 30

Expert Comment

by:nmcdermaid
Comment Utility
Named Pipes and TCP/IP is over TCP/IP (network), which doesn't care about 32 or 64 bit. So it should not have anything to do with the server being 64 bit.
I definitely have 32 bit SQL Server drivers connecting to a 64 bit SQL Server.
There's two things you can try:
1. Run SQL Server Profiler on the SQL Server and seee if you can see the device trying to connect.
2. Try and get more info from the device - can you ping the server, get through the firewalll etc. Are any log files created by this software?
0
 

Accepted Solution

by:
rattati earned 0 total points
Comment Utility
Hi all.
I did find the solution and it has nothing to do with the connection string itself, as I feared. The connection was good - 32 to 64 bit was no problem at all. The problem was in the application itself (on the server) so when I focused on that particular bit I found the application configuration error and fixed that.
Thanks everyone, especially nmcdermaid and sorry for wasting your time.
Cheers all.
0

Featured Post

What Should I Do With This Threat Intelligence?

Are you wondering if you actually need threat intelligence? The answer is yes. We explain the basics for creating useful threat intelligence.

Join & Write a Comment

This article will describe one method to parse a delimited string into a table of data.   Why would I do that you ask?  Let's say that you need to pass multiple parameters into a stored procedure to search for.  For our sake, we'll say that we wa…
Introduction: When running hybrid database environments, you often need to query some data from a remote db of any type, while being connected to your MS SQL Server database. Problems start when you try to combine that with some "user input" pass…
Excel styles will make formatting consistent and let you apply and change formatting faster. In this tutorial, you'll learn how to use Excel's built-in styles, how to modify styles, and how to create your own. You'll also learn how to use your custo…
Polish reports in Access so they look terrific. Take yourself to another level. Equations, Back Color, Alternate Back Color. Write easy VBA Code. Tighten space to use less pages. Launch report from a menu, considering criteria only when it is filled…

771 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now