It turns out the problem is, in fact, with the client-side, but this script worked like a charm to get the SQL version and service pack, so I appreciate your participation.
Main Topics
Browse All TopicsHello all,
First day on my new job and I'm hitting an error message that has been happening for the last few weeks and no one else has been able to come up with a solution. I hope you can help.
SQL Server 2000 is throwing the error message:
System.Data.SqlClient.SqlE
Here is what I have done:
I have increased the size of the datafile, from 2 gig to 3 gig. Stopped and started the SQL service. That allowed the client to perform its task (data synchronization) once. All subsequent attempts failed.
I rebooted the server. Client (different client) performed synchronization once, all subsequent attempts failed.
I added another datafile to 'Primary' datagroup. Stopped and started the service. One success, all subsequent attempts failed.
Stopped and started the service again. No difference - no success.
Between the two data files there is over 5 gigs of space and only 3 gigs have been used in the last eight months so I don't think it's a problem with the db not 'growing' fast enough. There is still over 110 gigs available on the drive. There is a total of 19+gigs cumulative in databases on the server so I don't believe it's a licensing issue (but it anyone knows how to confirm that I'd appreciate it). I've checked the log size and it is only about 1 meg of the 7 allocated (after a backup) and it is set to autogrow along with the datafiles.
Event Viewer on the server shows no errors during these attempts but the client displays the errors referenced above. The server does show:
Event Type: Information
Event Source: MappingReplication
Event Category: None
Event ID: 0
Date: 6/30/2008
Time: 10:48:44 AM
User: N/A
Computer: TRC_DELL2800N
Description:
Exception in ReplicationConn process:
MsgCode= AK
MappingLogic.MappingExcept
at MappingLogic.ReplicationMs
at ReplicationService.Replica
For more information, see Help and Support Center at http://go.microsoft.com/fw
If that is unrelated, don't worry about it. I'll come back to that one at a later time.
Now that I've typed all that out, I'm thinking the problem may be with the clients and that - perhaps - they have the MSDE with a two gig limit as part of the client app. Still, if anyone has other ideas please share them.
Thanks,
bvinson
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: dtoddPosted on 2008-06-30 at 16:42:40ID: 21903893
Hi bvinson,
I'd suggest that the MSDE 2 GB limit sounds the most likely given the work you've done above.
You can use the following code snippet to confirm the version and edition details.
Cheers
David
Select allOpen in new window