Saturday, February 25, 2012

RDA Concurrency Timeout Issue

Hi Everyone,

I'm currently trying to test our prototype application using RDA
festures for synchronization. It had come a long way since we started
off with merge repliacation and sync services.

We use SQLCE 3.1 for the client database, SQLServer2005 on the server.
The application will execute pull method to pull data from the server
to the client. Testing on few client is fine. Now, we are aiming to
test with concurrency pull from client. My setup to test this scenario
will be getting 2 notebooks. One with dial up connection, the other
with broadband connection and run the client apps on each notebook to
sync. Everything was good until i open up few more client on each
notebook, i.e. notebook with dial up connection running 3 client apps
at the same time; notebook with broadband connection running 8 client
apps at the same time. This is when some of the apps will prompt
error, the rest will continue to sync. I observe the server CPU usage
which is consider very low (2%-15%) and network activity graph with
low fluctuation shown but the mouse movement on the server are very
very lag/slow.

My question is:
1. I get error showing "unable to get RDA primary key" and "Timeout
Error" when i execute our application pulling data from the sql server
2005. What was the caused for this error? The situation are explain
above. Is this problem occur due to too many clients running on 1 single pc?

2. Is there anyway to test concurrency for RDA from SQLserver2005 to SQLce using pull method?


Thank you!

New update on the error.

Despite any number of client pc used, RDA application cannot exceed 10 execution of RDA at the same time. It will prompt:

Error Code: 80004005
Message : A secure Socket layer (SSL) connection is required to access this site
Minor Error: 28015
SQL server compact edition

I do have SSL setup, and the 10 application is synchronizing but more than 10 it will show this error. I even setup another virtual directory with sqlceagent without SSL (only http) to test it out, but still the same result.

The server is windows XP professinal. The notebook is win Xp too.

|||

Updates on caused of error:

Note For Windows XP Professional, the maximum number of other computers that are permitted to simultaneously connect over the network is ten.

http://support.microsoft.com/kb/314882

thx.

Still have one last error.

Same situation but within the 10 client limit. I use 3 client on 1 PC with dial up, 3 client in a pc with broadband and 2 client in 1 pc with LAN connection.

Occasionally, it will prompt out:

Error Code: 80004005

Message: Cannot read RDA primary key

minor error : (forget)

after confirming this error, another eception is thrown:

Timeout Error!

Is this due to high cpu usage on the server?

thx

|||

Updates on error

if my connection string is "Provider = SQLOLEDB; Data Source = MyInstance; initial catalog =MyDatabase; user id =userID;password=password"

I will get this error, occasionally (not always).

Error code: 80004005
Message: Internal Error: Failure getting RDA primary key columns
Minor Error: 29054
Source: SQL Server Compact Edition

I read about the connection pool, so i decide to disable it
my connection string will be "Provider = SQLOLEDB; Data Source = MyInstance;OLE DB Services= -2; initial catalog =MyDatabase; user id =userID;password=password"

i will get NEW error (not always)

Error code: 80004005
Message: Failure to open SQL Server with given connect string. [ connect string = Provider = SQLOLEDB; Data Source = 10.104.1.2; OLE DB Services = -2; initial catalog = CAMS; user id = sa; password = sapassword ]
Minor Error: 28627
Source: Microsoft SQL Server Compact Edition
Err. Par.: Provider = SQLOLEDB; Data Source = MyInstance; OLE DB Services = -2; initial catalog = MyDatabase; user id = userID; password = password

after either one of these error pop out, it will followed by another 80004005 errror,

Error code: 80004005
Message: Timeout Expired
Minor Error: 0
Source: Microsoft OLEDB Provider for SQL Server

I cant seem to googled anything on this issue.

Please Advise

Thx

No comments:

Post a Comment