Changes so far:

[FEATURE] Server: Notifications->Can now access in-loop Variables
[FEATURE] Server: Export settings->Added Deselect all button
[FEATURE] Server: SQL Task->Now including SqlException data in error output
[BUGFIX] Server: Logon->Fixed a problem which could cause some old AD groups not to convert to new logon type
[BUGFIX] Server: General file search->Handled problems with abnormal dates in files
[BUGFIX] Server: FTP Task->Copy/Move->Fixed a problem overwriting files
[BUGFIX] Server: FTP Task->Fixed another convert old settings problems (from version 6 to 7)
[BUGFIX] Client: Variables->Fixed unwanted User Variable window when clicking on scrollbar
[BUGFIX] Server: PowerShell Task->Handling error "Mixed mode assembly is built against version 'v2.0.50727' of the runtime and cannot be loaded in the 4.0 runtime without additional configuration information."

---

Hi Henrik,

Cool addition for Export, been doing this for a while manually, so this will be nice for small exports.

Can you just have a quick look at the Deselect All button please.

It Deselects the Parent Check Boxes, but the Children are still selected, and an Export Still includes all the detail.

See Attached.

Thanks

Kevin

New build, changes:

[BUGFIX] Server: Logon->Fixed a problem which could cause some old AD groups not to convert to new logon type
+ Deselect fix. Thanks KJDavie

---

New build, changes:

[BUGFIX] Server: General file search->Handled problems with abnormal dates in files

---

New build, changes:

[BUGFIX] Server: FTP Task->Copy/Move->Fixed a problem overwriting files

---

New build, changes:

[BUGFIX] Server: FTP Task->Fixed another convert old settings problems (from version 6 to 7)

---

Hi Henrik,

This post is regarding my earlier post: upgrading from 6.2.2 to 7.5.0 

Tried to import the 6.2.2 settings in the current beta 7.5.1 and received the message, as in my previous post mentioned:

Error ocurred when importing settings, err: There is an error in XML document (1,2).

When I ignore this message and import the settings, clearing the current, after a while the import is done.
It gives me privileges errors clicking on jobs. I was logged in as a AD user. Changing the groups needs me to be logged in as admin.
When I disconnect and want to connect again with the local admin user, I get the message:

Login failed, no such user exists on Server.

I end up in a situation reinstalling VC to get the software running again. I don't think the issue is solved.

Regards
Erik

---

Hi Henrik,

This post is regarding my earlier post: upgrading from 6.2.2 to 7.5.0 

Tried to import the 6.2.2 settings in the current beta 7.5.1 and received the message, as in my previous post mentioned:

Error ocurred when importing settings, err: There is an error in XML document (1,2).

When I ignore this message and import the settings, clearing the current, after a while the import is done.
It gives me privileges errors clicking on jobs. I was logged in as a AD user. Changing the groups needs me to be logged in as admin.
When I disconnect and want to connect again with the local admin user, I get the message:

Login failed, no such user exists on Server.

I end up in a situation reinstalling VC to get the software running again. I don't think the issue is solved.

Regards
Erik

There are some minor differences between importing and upgrading. Upgrading should be fine. Unfortunately we could not test import as your file was encrypted.

---

New build, changes:

[BUGFIX] Client: Variables->Fixed unwanted User Variable window when clicking on scrollbar
[BUGFIX] Server: PowerShell Task->Handling error "Mixed mode assembly is built against version 'v2.0.50727' of the runtime and cannot be loaded in the 4.0 runtime without additional configuration information."

---

There are some minor differences between importing and upgrading. Upgrading should be fine. Unfortunately we could not test import as your file was encrypted.

I did send you the password in the inbox of this forum. If you did not receive it, I can send it again.

Regards
Erik

---

There are some minor differences between importing and upgrading. Upgrading should be fine. Unfortunately we could not test import as your file was encrypted.

I did send you the password in the inbox of this forum. If you did not receive it, I can send it again.

Regards
Erik

The problem was that it was not a pure export but rather a zip. Something like that which hurt the file system when importing. If you could export again to a file rather than zipping we could try again.

---

This version was released today. Thank you for your testing!

---