Notes on User-creation and Validation Process of Virtual Quest Software

1. When VQ software is properly installed with all requirements (.NET, TapATL etc) and when running it for the first time and it asks for the username to create, some unique ID is generated by the VQ software and sent to the virtualquest.in server application. And the given username is then registered on the server.

2. The server accepts the info and based on this, a config.eee file is sent back to the client machine. (which goes into \Program Files\office\Virtual Quest folder. After validating, another file, validate.eee is also sent to the client machine.)

3. If in the above process, there is a break or some speed problem in the Internet connection, a .NET error is flashed at the client end. This error can also occur if the load on the server is more and/or it can’t maintain the speed for uploading the file to the client. This file upload/download speed is not related to the website display on the client side (for e.g.: google.co.in may be displayed quickly but still the error keeps flashing).

4. If this connection problem occurs a few times and the user creation is done more than once, then even though different names are given, the server keeps the same type of machine info in each of them.

So, if there is more than one file created for one client machine (due to connection of any similar problem), there will be an error flashed at the client end even when user creation and validation are successful. This is because the server gets confused as to which file to use since there are two or more same files as per the client machine info/ID is concerned.

5. So, whenever such a problem occurs, get the extra usernames removed from the server before trying anything else. It is also useless to validate a username in such a case as the software would not work.