Hi Ariston,
Please review the following SQL Server 2005 Books Online topic for the privilege level required to run the snapshot agent:
http://msdn2.microsoft.com/en-us/library/ms151868(SQL.90).aspx
If you are still having problems running the snapshot agent after granting the necessary privileges to the toshiba\snapshot_agent account as prescribed by the article above, please run the snapshot agent from the command line with -OutputVerboseLevel 2 to get extended error information on the operation that the snapshot agent is failing on.
-Raymond
Ok, that resolve the problem. The resolve are first I change the snapshot folder (by default SQL Server put the snapshot on "Repl" forlder at SQL Server folder), but I put on difference folder. Second it seem that my snapshot agent user have not permission to write on the snapshot folder. For example I have custom snapshot folder on "C:\snapshot" so I must set permission for snapshot agent to be able write on that folder. But came new problem that the snapshot agent still can not write on that folder so create snapshot became failed.
I change the member of for snapshot agent from users into administrators, and now I can create subscription. But I don't want the snapshot agent become administrators because maybe later it will make problem for me because this user have administrator priviledge.
I hope this clear. How to make the snapshot agent have permission to write into a folder
Thanks.
I am probably missing something here but all you really need to do is to grant R\W access of the snapshot folder to snapshot agent account (which I asssume is toshiba\snapshot_agent) I would suggest that you use runas to make sure that the toshiba\snapshot_agent account indeed has access to the snapshot folder. If you are still having trouble, post the error obfuscated message here so we can have a closer look.
-Raymond
I think I have resolve my problem by my self, but anyway thanks for reply, I hope this help to other person. My resolve is that change the snapshot_agent member of became member of SQL Server 2005 SQL Agent Users, and it works. But I don't know it safe or not to set a user to member of SQL Server 2005 SQL Agent Users
Thanks.