Hello.

I upgraded to version 6.2.0 from 6.1.9.

After upgrading I experienced problems accessing files on a certain server.
I could access the files before upgrading.

The problem only appeared on this certain server and the difference between this server compared to others, I have, is that the user trying to access the files does not have rights to the root directory but it has rights further down in the file tree and it has rights to the file.

I backed to 6.1.9 and now it is working again.

Has there bin a change in how files are accessed between the versions?

Regards

/Jesse

Hi Jesse,

sorry for the late reply. The most normal reason is that maybe you had the VisualCron running as another user than the default SYSTEM account which may have different accecss. Could that be the case?

---

Hi Jesse,

sorry for the late reply. The most normal reason is that maybe you had the VisualCron running as another user than the default SYSTEM account which may have different accecss. Could that be the case?

That is the first thing I was thinking but the more I think about it I'm guessing this isn't the case, since the OP would've had to uninstall and reinstall 6.1.9 to get back to the older version.... which would also have defaulted to running as SYSTEM, and its working now.

Maybe a credential didn't get carried over properly during the upgrade to 6.2.0? I only say this due to another post I saw that mentioned some of the 'On Error' settings per task didn't carry over during a multi-step/version upgrade from 6.1.4 to another in-between version.... to 6.2.1. (Might be wrong about 6.1.4, i just know it was older)

In any case, now that 6.2.1 is out, I'd suggest trying it again to be sure.

Brian

Hi.

Visualcron was running under the SYSTEM account before and after the upgrade so that should not be the problem.
I tried changing the credentials in different ways before I downgraded to 6.1.9 again, but I had no sucess with those changes.

I'm starting to suspect that it was just a weird error that happens sometime. I will try to install 6.2.0 again and see what happens after that I'll upgrade to 6.2.1.

I will keep you posted.

Hi all, we have same issues in accessing files over network share, which was working before properly.

We run our cron service with a different domain account, but this account has full permissions to network drives.

Since upgrading to 6.2 we need to put dedicated credentials to every task to get access to our files (writing, accessing, attaching to mails, ...) .

So our Question would be same - did something change?

Thanks and regards, Sebastian

Hi all, we have same issues in accessing files over network share, which was working before properly.

We run our cron service with a different domain account, but this account has full permissions to network drives.

Since upgrading to 6.2 we need to put dedicated credentials to every task to get access to our files (writing, accessing, attaching to mails, ...) .

So our Question would be same - did something change?

Thanks and regards, Sebastian

Can you confirm by looking at Services that VisualCron is still running as that domain account?

---

Hi Henrik, thanks for you quick reply.

You were right, in this case it was running again as local system, which could explain issues we had last days. Somehow i was sure we restarted it as other domain account.

we upgraded in this step to v.6.2.2 now and test if tasks without credentials are running well again.

We keep you informed...

Will VC run per default as local system - if we do a version upgrade installation?

Regards, Sebastian

Hi Henrik, thanks for you quick reply.

You were right, in this case it was running again as local system, which could explain issues we had last days. Somehow i was sure we restarted it as other domain account.

we upgraded in this step to v.6.2.2 now and test if tasks without credentials are running well again.

We keep you informed...

Will VC run per default as local system - if we do a version upgrade installation?

Regards, Sebastian

What we are doing in latest is to work harder to prevent any previous installation of a service. This can cause any previous setting one the service (like run as a certain user) will reset at each time you install.

---

Hello again.

I installed ver 6.2.2 yesterday and now everything works just fine.

In my case I suspect that something odd happened during installation of ver 6.2.0.

Well, I'm happy, everything works fine again.

Regards.

/Jesse

Hello again.

I installed ver 6.2.2 yesterday and now everything works just fine.

In my case I suspect that something odd happened during installation of ver 6.2.0.

Well, I'm happy, everything works fine again.

Regards.

/Jesse

Great, thanks for the update!

---