Can't create a subcription for SQL Server 2005 Mobile

I have been trying for almost 2 days now to create a subscription to a
SQL Server 2005 database but I haven't had any success. After reading
all of the documentation and installing everything, the problem seems
to have something to do with permissions. Here is what works:

* Created the a merge publication and checked to see that the
Replication Monitor shows that it works.
* Checked the directory where the snapshot files are located and they
exist.
* Can access the snapshot files from a browser, so I know security is
setup
* Tried setting the account for IIS 6.0 on the virtual directory to my
Windows account which has full admin permissions. Even tried
anonymous.
* Set the permission on all of the files and directories where the
snapshot files are stored.
* Added my Windows account to the PAL in the publication.
* Added my Windows account to the SQL Server login accounts

I then created an empty SQL Server 2005 mobile database locally on my
PC. Then I accessed it in SQL Server Management Studio.

Finally, I selected the New Subscription Wizard on the node of my
mobile database and tried using all kinds of login accounts.

Where it hangs is when I get to the last screen where it attempts to
create the subscription. After hanging several seconds on the part
that says "Synchronizing Data", it comes back with an error message
that either tells me that the SQL Server does not exist and/or the
user account does not exist. If I try screwing around with the various
types of login accounts, it can sometimes come back and say the IIS
account is not in SQL Server. There are a lot of accounts to setup
everywhere - publiccations, distributor, IIS, the database. Man, this
is getting to be one ugly headache. Can someone please give me some
solid steps on how to create a subscription.

Much appreciated,
Johann

.

Relevant Pages

  • RE: Problems with WebParts
    ... to a database called aspnetdb. ... > The connection string specifies a local SQL Server Express instance using a ... > server account must have read and write access to the applications directory. ... > This is necessary because the web server account will automatically create ...
    (microsoft.public.dotnet.framework.aspnet)
  • RE: DTS Package fails when Scheduled
    ... Apparently I was unable to pass on the database password when runninig the ... Make sure SQL Server Agent account has the correct rights/permissions. ... scheduled job under this context, I still received the error, even though I ...
    (microsoft.public.sqlserver.dts)
  • Problems with WebParts
    ... The connection string specifies a local SQL Server Express instance using a ... database location within the applications App_Data directory. ... server account must have read and write access to the applications directory. ... logged-in user needs the dbcreator privilege in the appropriate SQL Server ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Replication for non-trusted domains through VPN can only allow push subscription.
    ... >> Publisher, Distributor, and Subscriber talk to each other using RPC ... > the repldata share on the publisher because the SQL Server Agent account ... > What are the steps to setup and verify the pull subscription that I must ... >> the repldata share on the publisher because the SQL Server Agent account ...
    (microsoft.public.sqlserver.replication)
  • Re: Replication for non-trusted domains through VPN can only allow push subscription.
    ... >> Publisher, Distributor, and Subscriber talk to each other using RPC ... > the repldata share on the publisher because the SQL Server Agent account ... > What are the steps to setup and verify the pull subscription that I must ... >> the repldata share on the publisher because the SQL Server Agent account ...
    (microsoft.public.sqlserver.connect)