Is it possible to bypass DAO group/user security of old access database? - security

I'm trying to build new DB manager compatible with Windows 7 for old software which i don't have the code to. I am using 64bit Windows 7, and therefore cannot install the necessary DAO driver that was used to connect to the database.
Unfortunately, the database is protected using the DAO user/workgroup privileges. is there any way to extract the information from the database or bypass the security measures on that file?

You don’t mention what version of Access you have to work with.
If you have access 2010, or 2013, you can open the database using the workgroup security file with a shortcut.
2010
"C:\Program Files (x86)\Microsoft Office\Office14\MSACCESS.EXE"
"c:\RidesDev\SkiRides\RidesXP\RidesXP.mdb"
/wrkgrp "c:\RidesDev\SkiRides\RidesXP\Rides.mdw"
2013
"C:\Program Files (x86)\Microsoft Office\Office15\MSACCESS.EXE"
"c:\RidesDev\SkiRides\RidesXP\RidesXP.mdb"
/wrkgrp "c:\RidesDev\SkiRides\RidesXP\Rides.mdw"
The above shortcuts are of course one line and each part being separated by a space.
Once you opened the database with the above shortcut then this specifies the workgroup security file. You will be prompted for user and password. Once you done this, then can from the Access file menu close the database. (Do NOT exit Access). At this point you can create a blank new 2010 accDB database. And then import all objects from the old mdb database.
Note the above works by you NOT exiting Access – this means you will remain attached to the security group. Since you remain attached to the security workgroup you are able to import all objects from the older mdb to the new accDB you just created. At this point I would then exit Access and then launch the newly created database.
The new database will thus be free of all security, and your exit + re-enter of Access and launching Access without the security group shortcut means you are opening the new database without workgroup security.
Above assumes you have the correct user + password logon with full rights to the database. If the database has startup code and forms that you can't by-pass, then you can create a blank database and again specify the above workgroup security file for the new database and that also would allow you to import the objects into your new blank database. The result should be an accDB file without any security.

Related

MS-Access 2013 unable to remove .laccdb locking file

This is a long shot, but does any one know how to remove the lock file created by access 2013 file type ".laccdb".
I have an excel sheet which is connected to the access database via power query. The access database is on a shared drive. However even when this file is closed the locking file for the access database is not deleted.
When trying to remove the lock file it just says that unable to close as another program is using.
I've closed down the machine, removed all temp files, checked nothing is running and also checked in computer management within the administration tools. and checked for any open files.
I know the database should be split to stop this happening. however this is not my database, and the user refuses to split.
Any help will be grateful.
You can open and read the lock file with a text editor (I use Notepad++); within the file you should find the computer name (or some similar identifier) of the one(s) who have it open. You could then take that name/number/whatever to IT and see if they can identify who the user is. You should be able to close it from their computer. Hope this helps.

Move documents to SharePoint 2013 using SSIS WebDav

I have an SSIS package that calls a .jar that exports a file from one system to a specified file path. For my filepath I use \sharepointserver\davwwwroot\library. The problem is I have to have an RDP session open and maintain my file server connection in order for this to work. It will fail without the RDP session and even the davwwwroot connection times out, requiring me to logoff, back on and browse again.
How can I get this process to work without the RDP session?

UAC Manifest file in VS2005 not working

I have an add-in in Excel that needs to store some data in the HKEY_LOCAL_MACHINE registry. because of the UAC control in Windows Vista and earlier versions, I added a manifest file. But it is just not working. I even added the manifests in each of the projects of my solution. I have 5 projects in my solution (3 VB projects, 1 c++ and 1 deployment).
I am using VS2005. I added the manifest file to the project (with the requestedExecutionLevel set to "requireAdministrator" and embedded the manifest using mt.exe in a post-build command.
Even with that, I am still getting an access denied to the HKEY_LOCAL_MACHINE. The only thing that is working is when I start Excel as "Run as administrator".
Any clue what the problem might be? Thanks.
Manifests in DLL do not affect the execution level of the application, in this case it's excel.exe.
Here are the options you have:
to run Excel as administrator;
to modify the add-on to write to HKCU rather than HKLM.
If you need to store data available to other users, consider using ProgramData folder (CSIDL_COMMON_APPDATA or FOLDERID_ProgramData). Then your add-on creates a subdirectory inside ProgramData and modifies its permission so that this new directory is writable by anyone (by default, only the user account that created the folder has write permissions, other users can only read).
There are some other options:
You can write a service that your add-on will communicate to write data into HKLM but it's not.
You can create an elevated COM object which will write the data into HKLM.
Although users don't expect Excel to require elevation when run, therefore consider changing your logic so that your add-on does not require elevation at all.

How to connect to SQL database from Visual Studio/ open .mdf file

If I copy an .mdf file created by SQL server management studio and put it in the app_data folder I get this error:
"This database file is not compatible with the current instance of SQL Server.
To resolve this issue, you must upgrade the database file by creating a new data connection, or you must modify the existing connection to this database file.
For more information, see http://go.microsoft.com/fwlink/?LinkId=235986"
And if I attempt to Add connection using the visual studio wizard, choosing the Microsoft SQL server database file and select the file I get this error:
"
Unable to open physical file "path" {access is denied) an attempt to attach an auto named for file "path" a database with the same name exists, or specified file cannot be opened, or it is located on UNC share"
And if I attempt to add a connection choosing the "Microsoft SQL server" option in the choose data source window:
"a network related or instance specific error occurred while establishing a connection to SQL server. the server was not found or was not accessible. Verify the the instance name is correct and that the SQL is configured to allow remote connections..."
The only reason I want to connect visual studio to the database is because VS doesn't allow me to import text files. I have imported a text file into a DB from SQL server management studio and I want to connect it to VS. I've turned off UAC in windows 7 and I have file permissions to the mdf file.
Old question, but just to provide an answer for visitors from Google, the problem is not related to file system access (although Administrator accounts should have full privileges to the folder containing the mdf and log files). The solution is that SQL Management Studio needs to be opened using "Run As Administrator". The elevated permissions will allow SQL Server (or SQLExpress) to attach the older mdf file and update it. Once the db is attached, you can access it in Visual Studio by adding a database connection through the Add New Item->Data->ADO.NET Entity Data Model wizard.

Error while running VSTO application from Network path CannotCreateCustomizationDomainException

Environment: VS2008 .NET 3.5 - VSTO runtime 3.0 - Excel 2007
We have published the VSTO Excel document level customization to network path. All our users are able to copy the .xltm file from the network location to desktop(all the assemblies are still in networkpath) and able the run the customizations when the file is opened. When file is opened, it asks for install and user installs and proceed. It works fine. But, all these users are administrators to their machine. But, there is one special case. One of the user is using server machine to use these customizations and he is not an administrator on that machine. When he tries to open the .xltm file, he is getting error
Microsoft.VisualStudio.Tools.Applications.Runtime.CannotCreateCustomizationDomainException:
This document contains custom code that cannot be loaded because the
location is not in your trusted locations list: XXXX.XLTM. If you
trust this document you can save and open it from a location on your
computer. For more information, see
http://go.microsoft.com/fwlink/?LinkId=99104. at
Microsoft.VisualStudio.Tools.Office.Runtime.RuntimeUtilities.VerifyDocumentIsTrusted(String
documentFullLocation, String documentName, OfficeVersion
officeVersion) at
Microsoft.VisualStudio.Tools.Office.Runtime.DomainCreator.CreateCustomizationDomainInternal(String
solutionLocation, String manifestName, String documentName, Boolean
showUIDuri
We added the \networkpath and subfolders to Excel trusted locations, enabled all macros. But, still he is getting the error. I also added the file://networkpath to trusted sites in IE. Still no luck. Still he is getting the error.

Resources