I previously posted a message on the above error message and I have
found a solution.
Essentially it seems that there was nothing wrong with the
configuration but it is a problem with SQL Server 2005. This makes
sense because everything else was working, including being able to
initialise a new client from scratch.
After days of searching I eventually found this article:
http://forums.microsoft.com/technet/showpost.aspx?postid=1742090&sitei...7&sb=0&
The article states "This issue is a bug that is fixed in MS SQL Server
2008" and also gives a workaround. Unfortunately for me upgrading to
2008 is not an option.
There is a lack of detailed information but the problem seems to be
when adding a stored procedure (possibly a udf as well). The
workaround is to also add a table as an article to the publication. I
have tried this and it works on the development server but I am a bit
reluctant to do it in production.
Does anyone know any more about this issue or can give any advice? I'd
really like to understand the nature of the problem and the workaround
better before implementing. Is there a fix in any service packs or
hotfixes and if so will it work on just the server or will the clients
need the fix?
(Publication/distributor SQL Server 2005 Standard, merge pull web
synchronisation with SQL Server 2005 Express clients)
Jeremy.
FAQ
Search
Profile
Private Messages
Log in
