I've managed to break Access on my laptop. I had Office 2010 installed, then decided to upgrade to Office 2013 after going to an MS presentation. This wasn't the best move for me.
I realised after installation that Access 2013 doesn't support ADP's. So ran the installer and removed Access and reinstalled it from Office 2010. At this point all is well.
This morning I decided to uninstall Office 2013 entirely and reinstall Office 2010. Most of the office apps are working fine, but when I try and run my ADP in Access 2010, it seems to be appending a 1 to the end of all of my database objects, then errors out saying it cannot find the object.
I'm getting the following error trying to type into a combo box on the opening form of the database. " cannot find the object 'Company1'".
The correct name for the table object it cannot find is Company, not Company1. It seems to be adding the one on for other objects as well.
I have checked the connection property for the database and it is testing okay. I can open up the table in design view, and it shows me all of the columns etc, but I cannot open it in datasheet view to see the rows. I get the same error as above.
I don't believe that the ADP file itself is corrupt, because I can open it fine from another PC.
I have tried uninstalling Office 2010 and reinstalling from scratch, but I can't seem to solve the issue.
Is there a registry setting or something that is playing with the object names?
I'm at my wits end, so any help is appreciated.
Thanks,
Mike.
I found your question when having a similar problem with my PC; in my case, I added Access 2010 to a PC with Access 2003 - when I did that, it caused problems when I tried to filter on forms. The solution was to downgrade a DLL
C:\Program Files\Common Files\Microsoft Shared\MSClientDataMgr\MSCDM.DLL
Version 14.0.4731.1000 had to be downgraded to 11.0.8204.0. Suddenly filtering worked again!
So last night I was testing one of my ADPs in Access 2010 (they want us to upgrade!) and I got the same problem you had - it was appending "1" to tables, views, stored procedures, etc. So on a whim, I changed back to the newer DLL. It did the trick and I have my tables/objects back! It appears that different versions of the DLL have problems with different versions of MS Access.
Although you may have uninstalled Access 2013, it wouldn't have changed all your DLLs to the old one. I'd suggest that you rename the MSCDM.DLL (right-click it and get the version number first) and see if you can get Version 14 installed in its place. It shouldn't require a registration or a reboot - mine worked when I replaced the DLL and opened my ADP again.
Good luck!
Kevin
Related
I cannot get VS 2015 to create my EDMX file for an Oracle Connection.
I am using Visual Studio 2015 Update 3
I have installed the Oracle Developer Tools 12.1.0.2.4
I have installed Oracle Data Access and the following DLLs exist under \ client[user]\product\12.1.0\client\odp.net\bin
2.x\Oracle.DataAccess.dll version: 2.121.2.0 ODAC Release 4
4\Oracle.DataAccess.dll version: 4.121.2.0 ODAC Release 4
I am using the following assemblies
Oracle.ManagedDataAccess Version: 4.122.1.0
Oracle.ManagedDataAccess.EntityFramework Version: 6.122.1.0
* I believe both of these are version 12.2.1100 based on the folders in which they reside in the packages folder.
There are no connections defined in the Server Explorer
My steps are as follows:
Within the Solutions Explorer, Right click on project and select "Add" | "New Item..."
Select Data | ADO.NET Entity Data Model | Add
Select EF Designer from Database | Press Next
In the Entity Data Model Wizard:
Press New Connection... (I get an warning "Failed to find the default tnsnames.ora file." I ignore and press "OK"
With the Datasource as "Oracle Database (ODP.NET, Managed Driver)" I enter the credentials and specify the the other
connection parameters and press "Test Connection" which SUCCEEDS.
I press OK and am taken to the next page in the Entity Data Model Wizard
I include sensitive data in connection string and Press Next....
WIZARD SHUTS DOWN (crashes) - NO EDMX CREATED
Any assistance in helping me troubleshoot this would be greatly appreciated.
TIA - Xavier
Thanks to #Hong-vit pointing me in the right direction. I found the answer.
When you visit the download page for ODAC you're given a selection of version numbers.
In my case the top two were:
ODAC 12.2c Release 1 and Oracle Developer Tools for Visual Studio (12.2.0.1.0)
ODAC 12c Release 4 and Oracle Developer Tools for Visual Studio (12.1.0.2.4)
For me the top one wouldn't install. It would cut out during the installation process (thanks Oracle!) so I settled with the second one (12.1.0.2.4).
This meant that when I installed Oracle.ManagedDataAccess and Oracle.ManagedDataAccess.EntityFramework I had to select the correct version.
Not for me:
The one I needed
As you can see the version numbers (almost!) match up:
ODAC 12.2.0.1.0 = Oracle.ManagedDataAccess 12.2.1100
ODAC 12.1.0.2.4 = Oracle.ManagedDataAccess 12.1.24160719 (yay!)
I believe this is a failing on oracles behalf as it's not made clear despite their inclusion on a page long readme on which this doesn't feature. In additon the version numbers not quite being the same...but that's a rant for the blog.
I have the same bug. I fixed it successfully by follow this step:
On your project Right click -> Select Manage NuGet packages on Browse tab input oracle. You will see Oracle.ManagedDataAccess.EntityFramework. Select version of oracle you have installed. This should be 12.1.2400. Install it, you are done
I had the same issue - I hope I can help fellow Googlers having the unfortunate task of connecting Oracle and Visual Studio.
I followed the steps and still got crashes - because I was using VS2017 (I understand that the questions is tagged VS2015). You'll need to install the VS2017 ODAC Client. Thankfully, this one actually does something when you begin the installation. The installer in the link on the accepted answer will only work for VS2015.
The most recent version (as of this time of writing) of ODP.NET is 18.3, which can be installed through NuGet (Oracle.ManagedDataAccess.EntityFramework). Follow these steps on Oracle's website and you'll be setup.
...Or so you think. I got the same error as in this stack overflow question, where it won't go past the Entity Data Model Wizard.
I applied every configuration in the selected answer, but it still wouldn't work. When I downgraded my Oracle.ManagedDataAccess.EntityFramework from 18.3.0 to 12.2.1100, I could finally create my models!
I have had the same problem when I was trying to connect Oracle Entity Framework with Visual Studio 2017.
After install and unistall several times differents version. The build that better works for me is:
Oracle Developer Tools for Visual Studio 2017 (ODTv2017) v12.2.1200
Oracle.ManagedDataAccess v12.2.1100
Oracle.ManagedDataAccess.EntityFramework v12.2.20190115
EntityFramework .NET v6.3.0
I think that having similar versions in Oracle packages is very important for good performance.
It looks like someone here had similar issue: He add to change implementation somehow.
[in this ]case a View (valid and worked) caused the crashes. After changing the implementation without using that view it worked (more or less).
What I advise is you proceed step by step, only importing one object for the first time you test the wizard, then only simple table, then add procedures, views...
Just recently uninstalled VS2017 RC and installed VS2017 RTM.
We have a Windows Service solution which includes a Setup project.
When I build this in Visual Studio 2017, somehow it's triggering something in the installer for Visual Studio 2013 (which we're still using), as I get this popup appearing:
It's fairly reproducible, but I have no idea where to start with this one.
Any ideas how to stop it happening?
It didn't happen before with the release candidate.
EDIT:
So, several VS2017 updates later, this problem had got a lot worse, as it was stopping me building the setup project completely. Previously I was able to click cancel as in my first screenshot, but at VS2017 v15.3.3, it wouldn't cancel, and if I let it run, it hung at:
So this forced my hand somewhat. I've accepted #PhilDW's answer as he led me straight to the main clue, but I'll also add an answer of my own with more detail.
As in PhilDW's answer, I checked the event log, and found this:
Detection of product '{9C593464-7F2F-37B3-89F8-7E894E3B09EA}', feature
'Visual_Studio_Professional_x86_enu', component
'{E3FF99AA-78B9-4A06-8A74-869E9F65E1FE}' failed. The resource
'C:\Windows\Microsoft.NET\Framework\URTInstallPath_GAC\' does not
exist.
A little Googling, and I found this MSDN blog entry:
Workaround
We are consistently seeing this issue caused by a missing directory,
C:\Windows\Microsoft.NET\Framework\URTInstall_GAC (or
%SystemRoot%\Microsoft.NET\Framework\URTInstall_GAC).
To work around this issue,
Open an elevated command prompt.
Type: mkdir %SystemRoot%\Microsoft.NET\Framework\URTInstall_GAC
Note that the folder name isn't the same as in my case. I didn't notice this initially, and creating the folder didn't cure the problem.
However when I created the actuall folder referenced by the event log message, the problem went away, and I can now build my setup project without messages about VS2013.
It's a repair of Visual Studio 2013 because Windows thinks the install is broken (registry entries or files not as in the original VS 2013 install). If you look in the Windows Event log, Application, there should be some MsiInstaller log entries that tell you the product (by ProductCode guid) and the broken component (by component guid and file or registry name). This might help identify what's going on, but not necessarily have a clue to a fix. If it's a setup project it might be a conflict with mergemodule Dlls or prerequisites, some of which come from the current SDK.
You don't say if you're letting the repair complete, in the case that it's just an isolated occurrence.
I was developing a website using the ASP.NET platform on Visual Studio 2015 Community with Updates 1. But I tried using design mode and the IDE was so slow!
I could not do anything else. I've tried to repair, but after 15 hours, nothing happened. So, I've prefered the uninstall, but it wasn't had progress. Is there anything that I can do about this?
You could try the Revo Uninstaller Software, this looks for registry entries of the Program and removes them to.
Havent used it since a long time, but removing some toolbars without proper uninstallers it did its job just fine.
Another Tip:
Visual Studio creates a System Recovery Point before you install/uninstall/repair it. Try to restore your PC to that should be the easiest method.
I recently installed CU9 to BizTalk 2010. Microsoft site (https://support.microsoft.com/en-us/kb/3136004) claims that all previously CU are included in latest CU.
BizTalk Server uses a cumulative update (CU) model for providing fixes and updates. Each cumulative update includes new updates in addition to all the updates that were included in previous cumulative updates
Now I have problem with deployment ("Error saving map. Stored procedure returned non-zero result." error message when you deploy the BizTalk Server 2010 applications in BizTalk Server 2010 Administration Console") supposed to be fixed in CU4.(https://support.microsoft.com/en-us/kb/2667310)
So do I need to install all CUs from 1 - latest (for BizTalk 2010) to be fully upgraded?
You do not need to install all of them, the latest is just fine. They are cumulative as is stated.
That being said: have you tried uninstalling the latest CU (CU9) and installing CU4 instead? I assume you had no CU's installed before?
Unfortunately, lately Microsofts track records in relation to BizTalk CU's is not something to be proud of... There were quite a few issues with CU's already. It is not unthinkable that some CU after CU4 reintroduced the issue.
Also: the specific issue you are mentioning is something that was supposedly being fixed in CU4. However, this is just one particular case that was solved. There are still other remaining cases which have not been fixed yet.
Problem solved. It turned out that this App is using resources from another app that was not fully upgraded and one schema was missing in it. After deploying/upgrading that shared application everything went well.
Does any else have a problem where when using VS2005 or VS2008, it suddenly 'forgets' to color code and format the text for you? All of a sudden it acts like its a plain old notepad editor. Sometimes if I save and re-open the file, or else re-start Visual studio altogether, it suddenly 'remembers'. I thought maybe this was because of a bad install on my machine, but recently upgraded to a new one, brand new fresh install with all service packs - and we are right back to the erratic behaviour....
Is this a known problem? Is there a workaround (i.e. a key combo I can hit to tell it to do its thing?)
PS: This happens for me when doing asp.net with VB code - not sure if it affects other flavors of the tool...
EDIT: This is a clean install of VS2008 on Vista, but also have had it on XP. No addins on either setup, problem happens routinely.
Sometimes something similar to this happens to me in VB.Net. In my case it has alway been the backgroundcompiler service that has stopped working for one reason or another. Haven't found anything that helps besides restarting visual studio.
I got this often when working on large web projects (> 1K pages and 4K total files) and most often on ashx files.
At the same time, I would lose intellisense, This was happening because the files I was adding were not getting marked as "Compile" in the file properties -> build option.
I never found the cause (assumed it was overburdening the solution) but I found that it would stay fixed for longer if I deleted the SUO file periodically (it was getting into the 1MB range).
Since coming to a new company, new PC, etc, I have not had this problem but then again I'm not working on as large of a web project.
I use C# in VS2008, and haven't had any problems. Maybe this is VB.NET related?
I used to see the problem with "Web Sites". I have since changed most of my projects to "Web Applications" and haven't seen the issue in a while.
I had a similar issue with VS 2003. I use VS 2008 right now and this doesn't happen anymore.