You’re offline. This is a read only version of the page.
175
Hi,
We've installed Solomon 6.5 on a server on our network and we'd like to give certain people client access to use it. The problem is, nobody here knows enough about it. It doesn't seem like theres a solomon client, so I assume we install solomon on the client, and point it to the server. Can someone please explain what we need to do and how to do it? Thank you.
PS: the database is already configured, and usernames already created. We just need client access.
*This post is locked for comments
Your workstation must be a Windows 7 workstation. Solomon 6.5 thinks, on Windows 7 that even a mapped drive is a UNC drive. So, copy the WRKSTN folder from the server to the workstation's local drive C. Execute the setup.exe from that copy. You will get an error about MDAC and that the install will run but may not work. You can ignore that warning. You will have to specify the server location of Solomon in one of the install steps since the setup.exe is not running from the server location. Also, when you launch setup.exe, right click it and indicate you want to run it as Administrator or some of the DLLs may not register.
I've mapped a drive to the C:\Program Files directory above the Solomon directory and now when I go to the workstation and double click on Setup.exe I get a quick window that opens for a brief second and closes and the install does nothing. I've got all the security and share permissions set accordingly and it worked in my test environment, however in the production environment it is giving me fits. Anybody got any suggestions? TIA
I've found the answer finally. I figured I'd post it here for anyone with the same issue. Solomon Client could only be installed under our domain Administrator account, that was the first problem. I assume this has to do with how it was installed/configured on the server. Once installed, any user on the workstation can use it. Secondly, the mapped drive had to be pointed to the directory above the solomon directory. Not the Solomon directory itself. So on my server solomon is installed to "C:\Program Files\Solomon", so the mapped drive needed to be pointed at "C:\Program Files". Otherwise you'd get an error about missing files during installation.
Thanks
Thanks for your quick reply Dwight. Unfortunitely after I tried mapping my drive to the root folder ("C:\Program Files\Solomon" on the server) and tried running the client setup from there I got the same message:
"Microsoft Business Solutions Solomon clients cannot be setup from a UNC directory.
Please exit Setup and restart it from a local drive or mapped network drive."
I don't understand why I'm getting this if I am using a mapped drive. Just to clarify, these are the steps I took to map the drive and run the client installer: I deleted the original mapped drive of "wrkstn". I went on the server and shared solomon's root directory (c:/program files/solomon). Next, I clicked "map a network drive" on my workstation, selected "Z:", and entered the path to the network share which in my case is "\\bsssolomon\solomon". I clicked finish. Then I opened the mapped drive Z:, navigated to the "wrkstn" folder, and ran "setup.exe". I recieved the error message I mentioned above (again) right after the setup began.
Is there anything I'm missing or doing wrong?
Map your drive to the Root folder. It will use the mapped drive to access all the executables and reports.
Thank you Dwight. Now I have another issue. When tried to install solomon client on my machine I got this error message:
"Microsoft Business Solutions Solomon clients cannot be setup from a UNC directory.
Please exit Setup and restart it from a local drive or mapped network drive."
I mapped a network drive to "wrkstn" and tried installing from there and I got the same error. I thought that was odd, but then I copied and pasted all of the files and folders in "wrkstn" to a folder on my desktop and tried installing it from there. After that I got got this error:
"Setup was unable to run the data access setup.
Verify that .\MDAC\sqlredis.exe exists.
Setup may complete, but this client installation may not run properly."
Whats going on here? Where is that file supposed to be, and why didn't running it from a mapped network drive work if thats what its suggested? My OS is Windows 7, could that be the issue?
From the root install folder on the server there is a folder WRKSTN this is where the client install is located.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,240
Super User 2024 Season 2
#2
Martin Dráb
230,149
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (