I deployed an MDE file on the terminal server and when I double clicked the MDE i have the following error. " There isn't enough memory to perform this operation. Close unneeded programs and try again.
I never had any issues on local machine.
I tried de-compiling and compacting and again compiling. I can open other forms but only SwitchBoard is the issue. Any thoughts? Hardly there are 9 links from the MainMenu.
If you're in the console session on the terminal server (at a KVM?), or if you enable "Install Mode" (after you remote desktop, running "CHANGE USER /INSTALL"), does the problem still occur? I don't know of any specific issues with MDE applications over terminal services, but trying those two things will let you know if it's related to the TS configuration, or if it's a problem running that MDE on the server itself.
Can you update the question with the version of both Windows Server and Access you're using? This Microsoft KB article suggests a problem when you have Windows Server 2003 and Access 2000, so some more detail would be helpful here.
Related
I have a Desktop: MS Office Pro Plus 2016 & Win10 Pro 64bit v1909, and also a Laptop: identical setup but different Office keys all fully activated. MS-Access has started throwing an error (exactly same on both machines) since the latest Windows update. This error is happening with a standard "Desktop Database" stand alone / not shared etc.
Whenever I try to Compact & Repair or File / Save As, MS-Access errors with-
"Could not use 'path\file.accdb'; file already in use".
This did not occur (on either machine) before the latest Windows updates. It occurs for both new DBs and existing DBs. I have tried: Permissions in the folder: I'm using an Admin Account and can read/write/update/delete etc-so no issues. I've also disabled all Firewalls, Anti Malware to see if that was the problem - same error. As the same thing has occured on 2 independent machines after the same Windows update, it makes me suspicious of that - has anyone experienced the same error or have any idea how to solve this?
Many thanks for your help in advance.
Kind regards,
Bob
We've got some MS Access 2007 apps here. I'm responsible for one. Normally, it never gives any problems. I haven't heard from the users of this app for over a year, until today. It was written years ago by someone (I don't know who) that is long gone, with little documentation. We're in the process of replacing all of our Windows 7 machines with Windows 10 machines. At first I thought that was the issue. However, one of my colleagues, who is responsible for a number of Access 2007 apps, said that his users are able to use their Access apps with no problem.
Looking back at the user's error, it says simply, "ODBC - call failed". No error number; just that. So, my next thought was maybe there was a missing DSN on the new Windows 10 machine. However, I asked the PC tech to check one of the working Windows 7 machines. He told me there were no DSN's in them. I'm not an Access developer, so I asked my colleague, who does do Access development, what he could discover. He found that the tables are all linked tables from a SQL Server database. Looking at what he was referring to (now that I know where to look) I saw what he meant. The connection to each of those tables uses trusted connections. They're all pointing to the correct SQL database server. That server is there. When I got into SSMS I could easily see data in the tables.
So, what could be causing that error to occur, especially since it doesn't look like it needs a DSN to make a connection to the SQL db?
I presume your Windows 10 is 64-bit.
And probably your Access is 32-bit.
Its important to know!
If my assumptions are correct, you need to use the 32-bit version of ODBC admin to setup the DSN.
The 32-bit version is 'C:\Windows\SysWOW64\odbc32.exe'
The 64-bit version is 'C:\Windows\System32\odbc32.exe'
32-bit Access will look for a DSN setup using the 32-bit version of ODBC admin, even on a 64-bit OS. If you setup the DSN with the 64-bit version of ODBC admin, then a 32-bit Access will not see it!
Go back on the Windows 7 PC, and check exactly how the DSN is setup.
Is it a System, User, or File DSN?
Which drivers are installed for SQL Server?
(There are various different ODBC clients available for SQL Server.)
Replicate this DSN configuration when you create the DSN on Windows 10.
It sounds like you using the 'SQL Server Native Client' on Windows 7,
so make sure to install that on Windows 10.
See: Installing SQL Server Native Client
I'm on Windows 7 32 bit. When I open my access program, I get an error message as follows:
[Program Name] couldn't find file 'C:\Program Files\Microsoft Office\Office12\'. This files is required for startup.
The above listed directory however, is available - I can find it in Explorer, and I don't see why Access wouldn't be able to.
Note that the program I'm running was originally built in 2007, so it's old, but it was also built with compatibility with Access 2007 (supposedly).
I'm thinking maybe an Access profile issue, but I don't know where to start really.
Have you checked permissions for the folder? Perhaps your app is running as a non-privileged user. One thing to try is to run your app as Administrator.
I feel that the title pretty much speaks for itself. I keep getting a server 500 error when i try to access a page on my site that is using the Access DB.
I created an ODBC (32 bit) Data Source using the driver Driver do Microsoft Access (*.mdb).
I am sure i am using the wrong drivers/IIS configurations. This used to be hosted on an old server and we are trying to move everything over.
Would anyone be able to point me in the right direction? Thanks!
EDIT
I was able to get errors printed to my page. Below is the following error:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC Driver Manager] Data source name not found
and no default driver specified
When I enable 32-bit Applications I get the following error:
HTTP Error 404.17 - Not Found
The requested content appears to be script and will
not be served by the static file handler.
This issue is related to running 32bit applications on a 64bit server. Furthermore, if you have installed something else on it (for example, Outlook Web Access, or OWA for short) it can disrupt the IIS with adding it's 64bit modules to load globally, and that would effectively cause errors on 32bit pools.
The following debugging is assuming you have a requirement to run 32bit ASP application on a 64bit IIS server.
You have to set your application pool to run as 32bit
If the 32bit pool stops right after you make a request for an ASP page, it means that most probably there are 64bit modules failing to load. You need to see which dll is creating the issues by viewing the Windows Event log (eventvwr). Then, one by one, you edit the applicationHost.config file and add preCondition="bitness64" to each module that you see in the eventvwr until you get rid of all the errors in the log.
When finished with step #2, your pool should be working, but your app might not - it will most probably report 404.17, even if there is an ISAPI handler for ASP. When you open IIS, on the left side choose the server and on the right open the ISAPI and CGI restrictions. You will see that there's an ASP entry there (if not - you need to install it as a feature on the server). The ASP might point to something like %windir%\system32\asp.dll, but you need to make another entry. Your appPool is running as 32bit on a 64bit machine (that's shortened as WOW64 = 32bit Windows application running on Windows 64bit - Windows on Windows64), and you need to add an asp from %windir%\SYSWOW64\asp.dll. Also, add the corresponding handler (navigate to handlers, and practically repeat the entry for asp but use the SYSWOW64 folder instead of system32)
This should (finally) get it working.
Every time I try to run a Wizard in Access 2007 a dialog box pops up saying the following:
The database cannot be opened because the VBA project contained in it cannot be read. The database can be opened only if the VBA project is first deleted. Deleting the VBA project removes all code from modules, forms and reports. You should back up your database before attempting to open the database and dlete the VBA project.
To create a backup copy, click Cancel and then make a backup copy of your database. To open the database and delete the VBA project without creating a backup copy, click OK.
[OK] [Cancel] [Help]
(Yes, it's probably overkill to write out the entire message, but there it is.)
When I click [OK] Another dialog box pops up saying:
This feature isn't installed, or has been disabled.
...
However, I have installed every Access 2007 feature, including the wizards. In fact, earlier this Spring I used the wizards in another project and I haven't made any changes to my Office setup since then.
I have searched stackoverflow and the rest of the web but haven't come up with any solution to this problem. Does anybody have any ideas?
Thanks a lot.
--Knute
P.S. This also happens when I go to "Office Button"->"Access Options"->"Add-ins" and then try to select "Access Add-ins" in the "Manage:" combobox.
Update:
The problem happens with more than one Access database. I don't think it has anything to do with the actual Access database I'm working on because, as I added in my P.S. above, I see the same message when I try to manage my Access Add-ins through the Options panels (a feature that's not linked to any particular database). Does that make sense?
I uninstalled & reinstalled Access 2007 but did not uninstall & reinstall all of Office. I still have the problem. Any other ideas?
Does this happen with only one Access database file or multiple?
If multiple try re-installing Office/Access 2007.
If just one then check your references to see if there's anything wierd in there. Also try importing into a new MDB/ACCDB and/or a decompile. Decompile or how to reduce Microsoft Access MDB/MDE size and decrease start-up times
I finally found the solution to this. A poster on this www.utteraccess.com thread helped me figure it out. I had installed & uninstalled the 2010 Technical Preview awhile back and it apparently left an incompatible version of C:\Program Files\Common Files\Microsoft Shared\VBA\VBA6 on my machine. By deleting this folder, then restarting Access, I forced Office to run a repair installation. After the repair, my wizards started working again. Thanks for your suggestions, Tony.
I too was having this issue complete with the history of having uninstallaed Office 2010 Technical Preview. I am running a Lenovo X61 Tablet PC running Windows 7 64-bit mode. I found the broken VBA files here:
C:\Program Files (x86)\Common Files\Microsoft Shared\VBA\VBA6
Same solution: Delete the VBA6 directory.
The next time I ran Access 2007 it automatically went into its setup routine (a couple of minutes) and when it was done everything was working correctly.
Note: Uninstalling and re-installing Access 2007 did not solve the problem. I had to remove the bad directory as noted in bold above.