Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

The process could not create file - Snapshot Agent fails

1,089 views
Skip to first unread message

ragav

unread,
Jun 15, 2003, 10:37:10 AM6/15/03
to

Help needed on
"The process could not create file <filepath> OS Error: 1326 Logon
failure: unknown user name or bad password."

M/c A.W2k Prof SP3 with SQL2K Dev edition SP3
M/c B.W2k Prof SP3 with SQL DeskTop2K edition SP3
A as publisher and Distributor, B as Subscriber did the transactional
Queued Updatable replication setup. Both are in the same workgroup
and trusted
From the publisher m/c, When I Try to run the Snapshot Agent through
Snapshot Active-X control, it runs and generates the script

From the Subscriber m/c When I Try to run the Snapshot Agent through
Code using Snapshot Active-X control, it fails with the following error:
The process could not create file <'\\ServerName\C$\Program
Files\Microsoft SQL Server\MSSQL$ServerInstance\repldata\unc'> OS Error:
1326 Logon failure: unknown user name or bad password.

IF I run the snapshot Agent through the Enterprise manager, it very much
runs w/o any prob in the Subscriber itself.

What could be the cause and how to rectify this.
Thanks in advance,
Ragav

--
Posted via http://dbforums.com

hkvat...@yahoo.com

unread,
Jun 16, 2003, 4:51:10 AM6/16/03
to
Hi Ragav,

If you cannot start Snapshot Agent, and receive an "Access Denied"
message, run Dcomcnfg.exe. Click the Default Security tab, and then
make sure the Windows NT account that SQL Server Agent runs under is
enabled to have default access and launch permissions.

If the replication agents cannot access the snapshot folder on the
Distributor, make sure that the folder is shared correctly. On a
Distributor server running Windows NT, the snapshot folder defaults to
using the <drive>$ share and a path of
\\<computer>\<drive>$\Mssql7\Repldata.

On a Distributor server running the Microsoft Windows 95 or Windows 98
operating systems, the snapshot folder defaults to using the <drive>
without a share and a path of <drive>:\Mssql7\Repldata. If your
application requires the ability to create pull subscriptions on a
server running the Windows 95 or Windows 98 operating systems, you
must change the snapshot folder to a network path accessible by
replication agents running at the Publisher and Subscribers.

You can change the local path to a network path by sharing the folder
manually.

Regards
Hari Sharma, India

ragav <membe...@dbforums.com> wrote in message news:<3004616.1...@dbforums.com>...

PCK

unread,
Jun 16, 2003, 5:11:11 PM6/16/03
to
My guess is that you have not set up the publisher correctly. The
\\ServerName\C$ share is an administrative share. The subscriber
probably does not have permission to that share on the publisher.
Generally the snapshot folder should be set up as
\\ServerName\SharedFolder.

In Enterprise Manager go to Tools -> Replication -> Configure
Publishing, Subscribers, and Distribution. On the publisher tab click
on the "..." after your server name and make sure that the snapshot
points to a non administrative folder that the subscriber has
permissions to.

Patrick

ragav

unread,
Jun 18, 2003, 5:04:19 PM6/18/03
to

Thanks Hari Sharma and Patrik.

SQL Server 2000 Developer Edition with SP3 as Publisher and Distributor
SQL Server 2000 DeskTop Engine (MSDE 2000) with SP3 as Subscriber

The Publication and subscriptions are configured and its able to
generate the Snapshot through the SQL Enterprise manager(in Subscriber
server) by 'Start' of Snapshot agent.

When I run the snapshot agent through, an application (written using SQL
Active X controls), and connected to the publisher as 'sa' user, I get
the above mentioned error.

\\ServerName\c$\path -> are seems to be ok, as by this set up, SQL
Enterprise manager(in subscriber server, registered and connected as
'sa' user) runs the Snapshot agent without any prob.

It looks like that authentication fails, And as the error says,
username/password are not known to publisher/distributor server. What
could be prob when generating snapshot through application written using
Replication ActiveX Snapshot control?

Thanks

Message has been deleted
Message has been deleted
Message has been deleted
Message has been deleted

sivamss...@gmail.com

unread,
Mar 11, 2015, 4:12:14 PM3/11/15
to
Hi

It is very simple

Step1:
youneed to check this stored procedure on your subscriber master database
sp_helpserver

Step2:
Run this stored procedure on Subscriber Master Database..
Syntax:
sp_link_publication @publisher = 'publisher', @publisher_db = 'publication database', @publication = 'publication name', @security_mode = 0, @login = 'sa', @password = 'yoursapassword' @distributor = 'distributor'


----For example
In My system I'm faceing this Here
My publisher = 'VINAYAKA\SERVER2008R2'
My subscriber ='VINAYAKA\SERVER2'
mydistributor = 'VINAYAKA\SERVER1'
publisher_db = 'siva'
publication = 'sivaTp'
login = 'sa'--> Login is your creating your subscriber asking one login that login you use
password = '1122'



sp_link_publication @publisher = 'VINAYAKA\SERVER2008R2', @publisher_db = 'siva', @publication = 'sivaTp', @security_mode = 0, @login = 'sa', @password = '1122', @distributor = 'VINAYAKA\SERVER1'
0 new messages