Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 305 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
CuteFTP and NAS
chrisdf
Member Posts: 82
Here are some tips on using CuteFTP and the Job Scheduler running under NAS.
First, there's a reasonably good explanation of how to use CuteFTP here:
http://www.revolution1210.com/article.asp?r0=3&r1=199
Next, I found that using this utility works absolutely fine when running from normal user credentials. I then tested running under as a job under NAS on my Vista laptop - created a service and all worked fine.
However, if you want to run an application that uses CuteFTP as an Automation object and then schedule it to run in the Job Queue under NAS on Windows Server OS then the application fails saying that it cannot create an instance of the Automation object etc. etc. (long string of GUID hexidecimal characters).
It seems that although you set up the service that runs NAS with a log on account (I was using adminstrative account), the TE object fails to inherit the permissions of the service that is running it.
[Note that if you create an instance of NAS in the DOS shell it will work fine - it is only when you install NAS as a service and run it from there]
The solution is to run DCOMCNFG and configure the TEConnection as per the instructions below. After that, all worked fine (but it cost me a lot of time finding this out - hope it helps someone else!)
To configure the TE under the DCOM configuration applet
1. On the Windows Start menu, click Run.
2. In the Run dialog box, type:
DCOMCNFG
3. Click OK. The Windows Component Services dialog box appears.
4. In the left pane, expand Component Services, expand Computers, expand My Computer, expand DCOM Config, then click TEConnection Class.
5. Right-click TEConnection Class, then click Properties. The TEConnection Class Properties dialog box appears.
6. Click the Identity tab.
7. Under Which user account do you want to use to run this application, click This user, then provide a valid user name and password. It must be the same user as established under your task scheduler's run as property (if applicable), so that the scheduler service can call the COM object as a user. This will enable the Transfer Engine to run with the user settings, and if necessary, access pre-established SSL certificates (for secure connections).
8. Click OK to save the changes, and close the Properties dialog box.
9. Close the Component Services dialog box.
First, there's a reasonably good explanation of how to use CuteFTP here:
http://www.revolution1210.com/article.asp?r0=3&r1=199
Next, I found that using this utility works absolutely fine when running from normal user credentials. I then tested running under as a job under NAS on my Vista laptop - created a service and all worked fine.
However, if you want to run an application that uses CuteFTP as an Automation object and then schedule it to run in the Job Queue under NAS on Windows Server OS then the application fails saying that it cannot create an instance of the Automation object etc. etc. (long string of GUID hexidecimal characters).
It seems that although you set up the service that runs NAS with a log on account (I was using adminstrative account), the TE object fails to inherit the permissions of the service that is running it.
[Note that if you create an instance of NAS in the DOS shell it will work fine - it is only when you install NAS as a service and run it from there]
The solution is to run DCOMCNFG and configure the TEConnection as per the instructions below. After that, all worked fine (but it cost me a lot of time finding this out - hope it helps someone else!)
To configure the TE under the DCOM configuration applet
1. On the Windows Start menu, click Run.
2. In the Run dialog box, type:
DCOMCNFG
3. Click OK. The Windows Component Services dialog box appears.
4. In the left pane, expand Component Services, expand Computers, expand My Computer, expand DCOM Config, then click TEConnection Class.
5. Right-click TEConnection Class, then click Properties. The TEConnection Class Properties dialog box appears.
6. Click the Identity tab.
7. Under Which user account do you want to use to run this application, click This user, then provide a valid user name and password. It must be the same user as established under your task scheduler's run as property (if applicable), so that the scheduler service can call the COM object as a user. This will enable the Transfer Engine to run with the user settings, and if necessary, access pre-established SSL certificates (for secure connections).
8. Click OK to save the changes, and close the Properties dialog box.
9. Close the Component Services dialog box.
0
Comments
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!