![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
#3
| |||
| |||
|
|
You could check the service pack level of all the subscribers. Assuming this is OK, then perhaps use DBCC INPUTBUFFER and sp_who2 on the subscriber to see if you can check exactly what the problem is. Possibly it involves some sort of blocking. Another option is to use profiler if the previous route doesn't sole the issue. Sorry these are generalist approaches but I haven't seen this error message before and can find no previous references. HTH, Paul Ibison |
#4
| |||
| |||
|
#5
| |||
| |||
|
|
I don't think you'll get a definitive answer to this for a specific technology combination as there are too many posibilities for the MS folks to keep track of. If you ring PSS though they will expect the Pub/Dist = Sub in terms of service pack level as a matter of course. Worth doing it and then posting back if the problem still exists.... Cheers, Paul |
![]() |
| Thread Tools | |
| Display Modes | |
| |