Fatal Error

Question

hi-

I recently got this message when trying to view adv parameters for a user
what does it mean?

"index and count must refer to a location within the buffer.parameter name: bytes"

Comments

Hello,

Can you post here or send us a screenshot of the error? And what do you mean by 'adv parameters', by the way?

---

email sent.
adv parameters takes me the dialin, sessions, etc tab of an account.

Answer 1

Hello,

The issue is related to the solution provided in Remote Access option. The thing is that the script provided in the solution sets the Remote Desktop Settings (userParameters) property of a user account to a value that is not recognized by Adaxes.

We are going to fix the issue in one of the nearest releases. For now, you can disable the Edit User Advanced Parameters operation for the Web interface in order to avoid the error. To do this:

1. On the computer, where your Web Interface is installed, start the Web Interface Customization tool.
2. In the Interface type drop-down list, select the Web Interface you want to configure.
3. Activate the AD Management tab and click Customize Operations.
   
4. Uncheck the Edit User Advanced Parameters operation in the Operations list.
   
5. Click OK.

Comments

thanks.
this error seems to happen with one user thus far. I can't remove that b/c sometimes the HD needs to put info in terminal service field.
I have the terminal service profile tab shown when editing a user, but when I compare that to the terminal service profile via adv parameters, it isn't identical.

---

Hello,

this error seems to happen with one user thus far. I can't remove that b/c sometimes the HD needs to put info in terminal service field.

The error will reoccur with every user who have remote access enabled using the instructions provided in Remote Access option.

I have the terminal service profile tab shown when editing a user, but when I compare that to the terminal service profile via adv parameters, it isn't identical.

Can you post here or send us screenshots of both so that we could compare?

---

If I will get that error then this solution will not work for our environment.
we need to be able to modify terminal services tab via adv parameters. When I try to disallow/allow dial via AD and then try to view in Adaxes, I still get the fatal error message. So how will I be able to view/edit terminal service tab if I can't revert back?

Email sent.

---

Hello,

Issue with the remote access option:
Our script guys have found a small error in the script from the Remote Access option. We've fixed the script provided in the post. Replace the script that you currently have with the one from the post. If Remote Access is provided with the corrected script, the Advanced Parameters page should not give an error. However, for now, if you try to edit anything using the Advanced Parameters page, the user will probably not be able to obtain remote access.

we need to be able to modify terminal services tab via adv parameters

Currently, this will not be possible. By the next version to be available by the end of January, we are going to improve handling of the Remote Desktop Services Settings property, and it will be possible.

So how will I be able to view/edit terminal service tab if I can't revert back?

Try running the Custom Command with the modified script on the user that you mare experiencing issues with. This should correct the issue.

Differences between Advanced parameters and the form for editing users:
The thing is that there exists two Profile Paths that you've probably confused.

By default, if you want to specify a specific path to load a user's profile from, you can set it via the Profile Path property of the user's account (the LDAP name for the property is profilePath).

However, if you want Windows to use an alternative path for a user's profile when the user establishes a remote session, you can set it via the TerminalServicesProfilePath parameter stored in the Remote Desktop Services Settings (userParameters) property. In the Web interface, the parameter is also displayed as Profile Path on the Advanced Parameters page.

So, the Profile Path that you see on the page for editing users displays the value of the Profile Path (profilePath) property, however the Profile Path that you see on the Advanced Parameters page displays the value of the TerminalServicesProfilePath parameter stored in the Remote Desktop Services Settings property.

---

OK thanks.