I want to open the FE of my application in exclusive mode so that I do not open again the same application in the same machine but I need to open the BE in shared mode which is located in a server.
How do I set the whole thing? I want to the FE to open by itself in exclusive mode always and in case the user tries to open it a 2nd time to display an error that the DB is being used by the same user.
Related
I am trying to schedule the delivery of a report to a shared folder in a workgroup(without domain). But I keep getting the error message of
Failure writing file: A logon error occurred when attempting to access the file share. The user account or password is not valid.
I have tried several combinations of acounts with or without ComputerName:
ShareAccount
Share\ShareAccount
Server\ServerAdmin
Server\ShareAccount
And I have created an identical account with same password on both side.
Also, have tried set and unset unattended execution account with server administrator account.
I am sure the shared folder can be accessed with the same UNC path and account in windows explorer. Not sure what else I can try.
Is there anybody successfully do the file share delivery without domain? Or any other way I can schedule to export a report?
This feature works fine in SSRS so it is your settings which are wrong.
You will also want to have the subscription run as a specified user.
Create a local user on the computer to where you wish to save your report. Call it ReportUser.
For the purposes of this answer, we will call the the computer where you wish to save the report FileServer.
ReportUser needs write access to the share you are trying to use.
Try your report - if it still doesn't work then:
Launch Windows Explorer but Run As your new ReportUser - you will need to enter the password you have just created.
Navigate to the share by typing \\computername\fileshare - this proves your share is setup correctly.
Right click in the folder and create a new text document. this proves you have write permission to the folder.
Successfully completing those steps will mean that SSRS will be able to write to the share.
Within SSRS you need to be writing to:
\\computername\fileshare
The username will be \FileServer\ReportUser with a password that you have just created.
One more thing - run the schedule straight after your test - to prove something isn't happening to the network, e.g. overnight maintenance etc.
Environment: All machines are Windows Server. SSRS SQL Server 2016 version on one machine (SSRS service is the sole process running there). SSRS catalog on another machine that hosts SQL Server 2016. File delivery to a third machine.
On the SSRS machine (the one hosting the Reporting Services service), create a local account.
On the receiving machine (the one where the file will be delivered), create a local account with the same name and password as above. Also on the receiving machine, share a directory and grant read/write permissions to the local account just created.
On the Subscription tab of the Report Manager interface (or whatever is used to create a subscription), for the "Credentials used to access the file share" setting, select "Use the following Windows user credentials". Enter the name of the account created above, but do not prefix it with anything ("FILESERVER\ShareDeliveryUser" bad; "ShareDeliveryUser" good). Enter the password.
I tried numerous combinations, including attempting to use the "file share account," but this was the only way that worked.
Strangely, on the Report Manager interface, the "Result" of the last run always shows "Failure writing file...", although the file is indeed delivered.
Attributing original answer to post by user ExoStatic here https://social.msdn.microsoft.com/Forums/en-US/bdc5b51c-444b-442d-9657-3cf5495e79d0/file-share-delivery-failing#7725882e-d7c6-4b3d-88f6-2620409c3d48. Edited for clarity.
Environment: Windows 7, ACCESS 10, SQL Server.
Have an ACCESS app that resides in a single location on a server. I want to allow three users to use this app at the same time. The app is read only to SQL Server, but currently only one user can use the app at a time. If one is open the others will not open till the open one is closed. Looked all over the web, and went through options in ACCESS. How do I set it up so all can use it at the same time.
Thanks
jpl
The easy and recommended workaround is to distribute a copy of the Access file to each workstation so each user has an independent copy.
I've written an application in Access 2013 (64-bit) that I'd like to split into front-end and back-end databases, storing the back-end on a file server where multiple machines can access the data via local instances of the front-end. None of the computers have Access installed, so I'm using Access Runtime 2013 on them.
The application runs fine when it is not split, on a single computer. As soon as I split the app into front-end/back-end files, the program opens and immediately closes on startup, with no error messages. I'm assuming that this is due to invalid links to the external data file on the first startup of the app (i.e. existing links are to folder locations on my development machine).
Has anyone experienced this problem? If so, is it due to invalid links? And, what can I do to allow the program to stay open, allowing the user to navigate to a form that I've provided in the main menu form for setting the path to the back-end file for re-linking tables?
In the load event for the menu form check if you can access the data by trying to open a recordset. If you can't, close the menu form and open your form for setting the database location. Make that there's nothing on you location setting form that is bound to the database.
We have an MS Access front-end application that connects with Access tables on a network share. The application is installed on three terminal servers and several desktops. It works fine on the desktops and two of the terminal servers. On the third terminal server, we have the following problem.
If one user (no particular user) starts the application more than about 15 minutes prior to the others, the others all get the message "The database has been placed in a state by user 'Admin' that prevents it from being opened or locked".
If all users start the application within an approximate 15 minute window, they all work fine, until they close the application. At this point, no one can get back in until the first person to have started the application closes it. Once that person is out, everyone can get back in.
There are no obvious differences between the terminal servers. We are using the Microsoft Access 2010 Runtime to run the application. The setup is the same across all systems.
I have an Access front-end database connected to various back-ends (Access, mySQL, dBase) which runs as a separate instance on each users computer. All users have Access 2007, and there are a total of 5 users for this system. Each user runs the database from their local hard-drive.
On one computer I am unable to open any of the linked tables and receive error message 'Unexpected error from external database driver (8458)'. Also, I notice that the Linked Table Manager is disabled (grayed out) when right-clicking on the table link definitions.
Oddly, if I create a blank Access database on this computer, I can create and open linked tables with no problem.
Please try the following "fix" from Microsoft if you have not yet.
Start Windows Explorer, and then browse to the Borland folder.
If you cannot locate the folder, follow these steps. NOTE: Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.
Click Start, and then click Search.
Click All files and folders.
In the All or part of the file name box, type Borland.
In the Look in list, click My Computer.
Click Search.
Rename the Borland folder as BorlandOld. (For example, rename C:\Borland as C:\BorlandOld.)