New kind of merge repl error floating point exception?

Got a weird one. Hope someone has seen it before. Need some smarts.
Rolled out 150 new laptops, all imaged the same for users with a local msde
sp3a. All installed with subscriptionDB.
Previously, all were synching well on the same Sql 2000 pub/distr, on the
same publications for 18 months.
50% now work just fine, the other half get the message below. I tried
reinits, reinstall and sp4 upgrade (per several bug doc, found 3 close).
Varied results, some success but not consistant. Temporary success with
failures occationally but never clean.
Dies on sp_MSenumchanges....
The process could not enumerate changes at the 'Subscriber'.
(Source: Merge Replication Provider (Agent); Error number: -2147200999)
------
A floating point exception occurred in the user process. Current transaction
is canceled.
(Source: Servername_removed (Data source); Error number: 3628)
------
The process was successfully stopped.
Any experiences with this, ideas of causes are appreciated.
Mike
If data falls in the woods and nobody is there to see it ...... ?
You could try running service pack 3a again on the subscribers although
it doesn't make logical sense why anything should be different. I know
of a similiar error if the clients are use Windows 95/98/ME. Try
running dbcc checkdb just in case there is some corruption in any of
the tables.
|||Thanks for the suggestions. Good ideas.
I tried reinstalling sp3 and a new subscriptionDB too.
Dumped the subscription and recreated it with the wizard too.
dbcc checkdb ran clean but I haven't caught one with a failure in action
yet. Will keep at it.
The randomness makes me wonder if the subscription proc timesout somehow
before the server can return info. The subs history shows it processes
uploads to some random article and then fails.
Mike
If data falls in the woods and nobody is there to see it ...... ?
"seanbell68@.gmail.com" wrote:

> You could try running service pack 3a again on the subscribers although
> it doesn't make logical sense why anything should be different. I know
> of a similiar error if the clients are use Windows 95/98/ME. Try
> running dbcc checkdb just in case there is some corruption in any of
> the tables.
>
|||any commonalities on the machines that do not work? also take in
consideration isp/routers/vpn/encryption etc?
"Tigermikefl" <Tigermikefl@.discussions.microsoft.com> wrote in message
news:0900566A-3A1B-44F4-8118-4427B4FBAD3B@.microsoft.com...[vbcol=seagreen]
> Thanks for the suggestions. Good ideas.
> I tried reinstalling sp3 and a new subscriptionDB too.
> Dumped the subscription and recreated it with the wizard too.
> dbcc checkdb ran clean but I haven't caught one with a failure in action
> yet. Will keep at it.
> The randomness makes me wonder if the subscription proc timesout somehow
> before the server can return info. The subs history shows it processes
> uploads to some random article and then fails.
> --
> Mike
> If data falls in the woods and nobody is there to see it ...... ?
>
> "seanbell68@.gmail.com" wrote:
|||Unfortunately no commonalities any found yet. All laptops in the same
shipment, imaged with the same WinXP. All received a new vpn client but half
are synching fine. Soho offices mostly, isp's vary.
I will poll the challenged as to ISP/Wireless/Routers etc to see if
something jumps out.
We are leaning towards a connection problem but can't figure how they all
get the same error and doesn't go into the retry mode via sql agent.
Mike
If data falls in the woods and nobody is there to see it ...... ?
"S c o t t K r a m e r" wrote:

> any commonalities on the machines that do not work? also take in
> consideration isp/routers/vpn/encryption etc?
>
> "Tigermikefl" <Tigermikefl@.discussions.microsoft.com> wrote in message
> news:0900566A-3A1B-44F4-8118-4427B4FBAD3B@.microsoft.com...
>
>
|||Turned out to be a problem with the newer cisco vpn client 4.6. Runs
errorless with earier client. Checking networking but no longer a repl issue.
Thanks for the input anywho.
Mike
If data falls in the woods and nobody is there to see it ...... ?
"Tigermikefl" wrote:
[vbcol=seagreen]
> Unfortunately no commonalities any found yet. All laptops in the same
> shipment, imaged with the same WinXP. All received a new vpn client but half
> are synching fine. Soho offices mostly, isp's vary.
> I will poll the challenged as to ISP/Wireless/Routers etc to see if
> something jumps out.
> We are leaning towards a connection problem but can't figure how they all
> get the same error and doesn't go into the retry mode via sql agent.
>
> --
> Mike
> If data falls in the woods and nobody is there to see it ...... ?
>
> "S c o t t K r a m e r" wrote: