Thanks for the reply, here is the current ownership:
Publisher - SQL 2k - sa is the owner
Distributor - SQL '05 - my NT account is the owner
Subscriber - SQL '05 - my NT account is the owner
I am not sure what the s1 service is that you are referring to - the first server (i.e. Publisher)? It is already owned by sa - are you recommending I make the other two Servers to be owned by sa as well?
Actually I was confused - the DB we were replicating from - had an NT account as owner - we changed it to sa and get the same error - I will take a look at the replication DB to see what the ownership is of that.
Thanks Satya - so do you recommend we install SP4 to fix this problem?
A little more info:
If I configure SQL 2k machine (publisher) to act as distributor I can create the publication without any problems, I can also create it when the Publisher is running SQL 2005 and uses a SQL 2005 server as its distributor.
The problem only exists when SQL 2k is the publisher and SQL 2005 is the distributor.
Job 'JOB-NAME' started successfully.
Server: Msg 15404, Level 16, State 10, Procedure sp_grant_publication_access, Line 136
Could not obtain information about Windows NT group/user 'a_user_name', error code 0xffff0002.
The statement has been terminated.
All DB's are owned by SQL Account: 'sa'
Development Server is running SQL 2K SP3 and was just hotfixed to version 818 (so it would be running the same version as the working desktop mentioned earlier)
ok this is REALLY REALLY strange - so I deleted the SQL Account it gave the error on - now it complains about another random SQL Account - I don't want to delete evey single SQL account to "fix" this problem - we certainly did not explicitly choose the accounts to authenticate against - did I miss a step somewhere?
What is really puzzling is how I am able to set this up just fine from a desktop running MSDE, it is only while trying to set this up on a Server installation do I get this error when trying to create the publication.