Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Windows CE 5.0 connecting to MSSQL 2005 64 bit

Posted on 2009-04-14
2
Medium Priority
?
312 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
ID: 24154369
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
ID: 24199085
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

NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Use this article to create a batch file to backup a Microsoft SQL Server database to a Windows folder.  The folder can be on the local hard drive or on a network share.  This batch file will query the SQL server to get the current date & time and wi…
In this article we will get to know that how can we recover deleted data if it happens accidently. We really can recover deleted rows if we know the time when data is deleted by using the transaction log.
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an anti-spam), the admin…
In response to a need for security and privacy, and to continue fostering an environment members can turn to for support, solutions, and education, Experts Exchange has created anonymous question capabilities. This new feature is available to our Pr…

971 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