Share
ReportToday I had an odd situation with a new user to an existing SL 2011 system that I thought I would share. When this new user first launches SL 2011 they have to go through the find database process (as usual). However, that screen was looping and not returning to the main log in screen. It found the SQL instance and could see the application and system databases just fine but it refused to go back to the main log in screen and issued no error to indicate what was going on.
After fighting this for a while I looked at the user's roaming folder to see if the Solomon.ini file had been created and it had not. I then manually created a very basic Solomon.ini file just defining the SQL name and the system database name using NotePad and saved the ini file in the correct folder under roaming. When we launched SL, it opened the main log in screen and we were able to select a company and enter user credentials and SL came up just fine. When I looked back at the Solomon.ini file it had been properly updated with additional information that is stored after a successful log in.
So, my take on this is that there something not happening after specifying the find database values such that this screen never got to the point of writing out the solomon.ini file. It was not an access rights to the user's roaming folder but, without any sort of error message, I was unable to determine the cause of the problem and the manual creation of the solomon.ini file was just a workaround to the problem.
If anyone has encountered such an issue and knows the actual cause, it would be great to share that with this post.
*This post is locked for comments
All responses (
Answers (
4,710
