Running an Executable from another Box
I have a exe that contains a backend db (SQL). I've tried just about everything to get this application to run from another machine. I also made sure that my client machine and user have full "SA" access to the database to. I mean I've completely opened everything up with no luck!
Attempt 1:
Shared out entire folder that contains all of the application files associated with this program, including the database.bak file. Created a shortcut from user's desktop to the shared folder on the server machine.
Attempt 2:
Shared out the executable itself and also added it to Roles > Management and added it to Remote apps, hoping that pusing out an .RDP package to the client machine would work. No go. I also created an installer package with no luck.
Attempt 3:
Copied entire folder down to client machine and re-pathed the config file to point to the server. No go.
The latest error I'm getting from the client machine when trying to do "Attempt 1" (See attached)
Capture.JPG
Attempt 1:
Shared out entire folder that contains all of the application files associated with this program, including the database.bak file. Created a shortcut from user's desktop to the shared folder on the server machine.
Attempt 2:
Shared out the executable itself and also added it to Roles > Management and added it to Remote apps, hoping that pusing out an .RDP package to the client machine would work. No go. I also created an installer package with no luck.
Attempt 3:
Copied entire folder down to client machine and re-pathed the config file to point to the server. No go.
The latest error I'm getting from the client machine when trying to do "Attempt 1" (See attached)
Capture.JPG
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I was able to enable SQL authentication and created two new test accounts and was able to authenticate fine. Unfortunately, after sharing out the appliation folder that contains the .exe file of the app on the remote computer to see if it would launch, it wouldn't and produced the same error dialog as initially attached.
ASKER
may have figured it out...just doing some additional testing...
Standard procedure is to create a separate account accessible thru TCP/IP and only give them limited permissions on the database they are supposed to use.
ASKER
Yep, each of my users basically have two accounts. For example "domain\user1" and set access to Master table which is setup via windows authentication, i then went in and created another account for these users using sql authentication "user1" then set it's access to the actual name of my database that the appliation is using. I then drilled down to the .exe and shared it out and had them point right to the exe rather than the parent share that the exe resides in (Doesn't matter, however it seems to work better when sharing right to the exe). 2 of my test users are now able to see the database. I have one user though that is having issues still. I think we got it though. Thank you for everyones input on this.
ASKER
I was able to successfully, turn on TCP/IP connectioning via SQL Server Configuration Manager, however I'm not sure how to convert it's authenticating method. Right now, it's set to authenticate via Windows Authentication, how would one go about changing it to SQL Authentication?