This release contains the following changes:

[BUGFIX] Server: Fixed SQL output settings for ODBC/OLEDB
[BUGFIX] API: Fixed various problems with Remove methods

---

I downloaded this version and here are my 1st impressions:

1. Clear button for the SQL string is working. Nice!
2. You need to acknowledge the deletion of a custom variable. Was this already in place? Ik like it though!
3. The timeout on the change registry state trigger isn't working, this is also in the current stable version.
4. a Warning message when pressing on the stop server button in the menu bar would be nice.
5. I did some API calls on the connections. A few versions before I got Null references, but not anymore. Nice!

So I found only one issue that is not working (nr 3).

---

I did found something else:

I have several VC servers. One is our test/beta VisualCron server.
I added in the manage server list an other VisualCron server. I have now two servers in the list.
When I connect to this server it tells me the version is older and I should upgrade the server to a new version. That's true.
Now I press the manage server button on the login page. I remove my just added (older version) server.
When I come back at the login screen the right server is automaticly selected (only one left in the list), but when I now press connect, the message will still come that the server I connect to is older than the client, but that isn't true anymore.

---

Are you sure the selected server is not an old server? It sounds very strange.

---

And how do you mean the Trigger timeout does not work. What timeout do you use and what to you see in the log?

---

And how do you mean the Trigger timeout does not work. What timeout do you use and what to you see in the log?

When I use a event trigger for a service state change, there is a tab called timeout. Here I can set that is the trigger is not fired in x seconds/minutes/hours the trigger should be fired. This isn't working.
The trigger itself is working, that's fine, just the timeout isn't. I will look for the log.

---

We tested this on the Registry trigger and it worked fine. We will test this on the service trigger as well.

---

Are you sure the selected server is not an old server? It sounds very strange.

1. I installed 4.9.10
2. I logged in with admin
3. Via managa-Manage Servers I added an other server with version 4.9.3
4. I closed the client.
5. I start the client again and select the 4.9.3 server.
6. After login I get the message that the server is older, and that it true, it's 4.9.3, not 4.9.10
7. At the login screen I click on the Manage server button and I remove the 4.9.3 server and closed the manage servers window.
8. In the loginscreen my 4.9.10 server is the only server in the list and is automaticly selected.
9. I press the connect button to connect to my 4.9.10 server
10. I get the same message from step 6....
11. If I open the dropdownlist and select the server again (only one in the list) and login again it's fine.

---

I have found on more thing that is not right:

I can not make a network drive anymore. It is telling me: Could not map drive, error: The specific drive name is invalid.
I thought, it might have something to do with vlans and stuff.
I reinstalled 4.9.3 and here I can make the connection whitout any troubles.
Now I upgraded this version back to 4.9.10 and I see a red cross in my network connection, so the connection is there but not working anymore.
If I click on reconnect it doesn't work: Could not map drive, error: The specific drive name is invalid.
I also can't unmap the drive mapping anymore. Could not unmap drive, error: This network connection does not exist. I'm stuck with an entry which is not working...
I have to install 4.9.3 to remove this drive mapping.

---

I am really surprised as we have not touched this functionality at all. We will investigate.

---

1. remove the network drive in 4.9.3
2. upgrade to 4.9.10
3. add it in 4.9.10

---

1. remove the network drive in 4.9.3
2. upgrade to 4.9.10
3. add it in 4.9.10

Then I get the errors mentioned before: Could not map drive, error: The specific drive name is invalid.

---

Reason for the steps is that you should have no network drives active when installing 4.9.10. I assume you had an old network drive when you upgraded before.

---

Reason for the steps is that you should have no network drives active when installing 4.9.10. I assume you had an old network drive when you upgraded before.

No, on this server I did not have any network maps at all. I just wanted to try it in this version.
Before the 4.9.10, I had 4.9.9 installed and before that an other beta.
This is the 1st time I test a network map on this server an I tested it 1st with 4.9.10.

When I figured out this was not working, I installed 4.9.3 just to be sure it is working on this machine. In this version 4.9.3 it was working.
After that I upgraded back to 4.9.10 and I saw a red cross in the drive mapping. I also could not delete the mapping.

I uninstalled 4.9.10 and reinstalled 4.9.3. In here the red cross is gone and the mapping is fine. I removed the mapping in this version and upgraded again to 4.9.10.
Not I'm not able to add the mapping. The error is back.

---

We found and corrected the Timeout issue on Service Trigger. Thanks.

---

We found and corrected the Timeout issue on Service Trigger. Thanks.

\:d/

---

For the drive mapping problem I have this in my logs:



and



1st I didn't have credentials setup, the 2nd try I did.

---

Seems like the network mapping error was related to a build error. We are rebuilding for version 4.9.11.

---

I know why the login problem mentioned before happened.

If a server is removed from the list (step 7) this item is removed from the dropdown list.
If this item was selected an other item will be selected (step 😎.
The fields: Server / Port / Username / Password stay unchanged. So these fields still contains the server settings you just deleted.
If you reselect an item from the dropdown list (step 11) these fields are updated and the login will be fine.

So that's why..

---

Thanks, I suspected that too. But we are about to change the whole login process so will probably not spend any time on it.

---