It appears that with 6.0.7 or 6.0.8 something has changed that is causing us a problem. Up to 6.0.6, my scripts would detect the user specified in the Credentials for the task. Suddenly, regardless of the user specified, my script detects SYSTEM as the user.

Well, it seems to be on only one machine (so far.)

Edit the Credential and check:

- local login
- load profile

That should probably do the trick.

---

1. I don't have those boxes checked on other machines, and it's working fine.
2. Is this something that changed?
3. What does it mean Local Login?

That does fix it, but again, not necessary on every machine.

Well, I am mistaken. Somehow, only that server had those boxes unchecked. Nobody has touched that, so it appears the setting changed on it's own or some updated of VC caused the issue. Strange.

These are new. Previously those were set on Execute Task but they belonged more to the Credential so we moved them. These settings control how the login should be performed. We have some coverage of this in the documentation.

---

Problem: This setting is not saving on machine restart. I restarted 4 servers last night (2 physical and 2 VM's, Windows 7, Server 2003, and Server 2008), and all 4 lost the Local Login and Load Profile settings for the Credentials.

Problem: This setting is not saving on machine restart. I restarted 4 servers last night (2 physical and 2 VM's, Windows 7, Server 2003, and Server 2008), and all 4 lost the Local Login and Load Profile settings for the Credentials.

So, you are saying that you do the following:

1. edit a Credential and check Local login and Load profile
2. restart computer
3. now, these are unchecked when opening the Client again?

---

We tried to reproduce this but couldn't. Please note that server restart procedure withing VisualCron is the same as stopping the VisualCron service and then start it again. So you should be able to reproduce this quickly if there is a problem.

Please check the following:

1. try creating a new folder "settings2" in VisualCron folder
2. change server settings folder in server settings to that folder
3. add a new fake credential with local logon and load profile checked
4. write down a credential that has these checked as well
5. stop service
6. start service
7. restart client and connect
8. double check that new and old settings are there

If not, there might be something with storing the settings folder and we will proceed to that test.

---

Just tried a service restart did not duplicate the problem. I know this happened once, because jobs ran fine for several days and then failed after the restart. However, does not seem to be a recurring issue.

---

Followed your steps as well, and had another problem:

Connection failed to 'localhost'. Connection failed with error 'Failed to connect to an IPC Port: The system cannot find the file specified."

Restart server. Able to connect. Credential settings saved.

---

Conclusion: Fluke. If it happens again, I'll report it. I've got several servers that I have no restarted since that same change of settings, so we'll see.