October 2, 2008 at 4:09 pm
Hi,
i have this problem
i have to connect to remote server which is not in my company domain using dns username and password.
after conncting i have to read each file and move that to a "completed" folder on their side
i have 2 senarios here:
first senario:
when i map the drive to that server with username and password and map the ssis package to that mapped folder and run the package from utility ,package runs fine and loads all the files in the folder and moves the files to "completed" folder
but when package is executed through scheduled job that user wont be able to read and write on that mapped folder
second senario
if i try to connect to server through utility or job
giving //ip address/folder_name
it fails.
please respond.
October 3, 2008 at 12:15 pm
Hi,
The solution is:
1. Create local Windows accounts with the same user name /password on both servers if they are not in the same or trusting domains.
2. In your SQL Server on Server1 for example start SQL Server Agent on this local account that you created in step 1
3. In your job specify fully qualified path to the remote folder as \\Server2\MyShare
4. Give the Server 2 user that you created in step 1 permissions to the folder on Server 2
It should work. This is how they did it in the workgroups.
Let me know if you need more help
Regards,Yelena Varsha
October 3, 2008 at 2:23 pm
thanks for the reply but when you say specify the path in the job
when do i need to do that
October 3, 2008 at 2:57 pm
It is where you say you map an SSIS package to the folder. Just map it not as X:\MyShare but as \\Server2\MyShare
Regards,Yelena Varsha
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply