.NET does not work in 9.1.5 - VisualCron - Forum

Community forum

Jon Tofte-Hansen
2020-04-06T12:13:58Z
I cannot get our .NET tasks to work after upgrade. I get this error when I open a task or try to create a new one:

An error occured:Could not find a part of the path 'C:\Users\<user>\AppData\Local\Temp\12\q5smexg3.tmp'.

I get to the task window but the Method and parameters section is empty and I cannot compile or refresh methods.

I am on Windows 2019.
Support
2020-04-06T12:27:38Z
Originally Posted by: Jon Tofte-Hansen 

I cannot get our .NET tasks to work after upgrade. I get this error when I open a task or try to create a new one:

An error occured:Could not find a part of the path 'C:\Users\<user>\AppData\Local\Temp\12\q5smexg3.tmp'.

I get to the task window but the Method and parameters section is empty and I cannot compile or refresh methods.

I am on Windows 2019.



I can't reproduce this. Do you have access to other servers/machines where you can reproduce this on as well?
What version did you upgrade from?

You can mail screenshots to support@visualcron.com
Michael
Support
http://www.visualcron.com 

Please like  VisualCron on facebook!
Jon Tofte-Hansen
2020-04-06T13:56:20Z
Thank you for the answer.

Well technically I moved a job from a 8.5.5 server (on Win 2008R2) to a 9.5.1 (on Win2019), so it was actually an export/import from a former version.

It seems to work now but I am not entirely sure why.

I used the client on the server and after I logged off and on the problem somewhat went away. Somewhat because the problem got back if I opened the task in question (!).

I logged off and on again and created a new job with a .NET task and copied the script directly from the old installation. This worked and now I could open the problematic task without problems (?!) and that works as well now (?!!).

VisualCron is the only program running on the new host and I have made no changes in VC or the OS when working with this.

But it seems to work so thats good for now. Thank you.
Support
2020-04-07T14:02:16Z
Originally Posted by: Jon Tofte-Hansen 

Thank you for the answer.

Well technically I moved a job from a 8.5.5 server (on Win 2008R2) to a 9.5.1 (on Win2019), so it was actually an export/import from a former version.

It seems to work now but I am not entirely sure why.

I used the client on the server and after I logged off and on the problem somewhat went away. Somewhat because the problem got back if I opened the task in question (!).

I logged off and on again and created a new job with a .NET task and copied the script directly from the old installation. This worked and now I could open the problematic task without problems (?!) and that works as well now (?!!).

VisualCron is the only program running on the new host and I have made no changes in VC or the OS when working with this.

But it seems to work so thats good for now. Thank you.



Thanks for updating us. Let us know if the issue starts occurring again and we'll take a look at it.


Michael
Support
http://www.visualcron.com 

Please like  VisualCron on facebook!
Scroll to Top