I have read so many questions on the internet about the 'microsoft.ace.oledb.12.0 provider is not registered' error and thought someone here might just help us out?
Suggested solutions so far include:
1. compile the solution to target 'x86 cpu'. this or leaving it as 'any cpu' will have the solution install in the win 7 OS but the error will not disapper. i tried enough times. If you change the target to x64, however, the solution does not install.
2. install 'AccessDatabaseEngine'. I downloaded and installed and nothing changed.
3. install 'AccessRuntime'. This too did not change the error message.
Basically, the error is the application runs but cannot connect or interract with the access 2007 database in win 7, but works perfectly in win xp.
I have learnt that x64 machines (vista, win 7) do not have drivers to run x86 applications (Access 2007). win 7 smartly creates a separate x86 Programs folder to install the applications, but still cant work with access 2007 database in the application.
Does anyone have a solution that can be packaged and distributed with the vb 2005 application to have the data side work?
a few suggestions that i also found include long winding procedures with iis7 which also only work in certain circumstances and arent really what you would instruct users to go through. I'll really appreciate a solutions that, say suggest a kind of dll to develop or download and distribute with the application to go round the x64 problem
I understood from earlier discussions here the Access adapter/connector does not exist for x64, so there is nothing you can do about it so you must build your EXE for x86, not for "any CPU".
Assuming that is correct,If that doesn't suit you, your best bet probably would be a switch to SQL Server (possibly the Express version). And if you were to need existing data, either a backup or a copy/convert operation on an x86 system would be required.
I have learnt that x64 machines (vista, win 7) do not have drivers to run x86 applications (Access 2007).
Wrong way to say it. It's not a case of having drivers to run an application. It's that the application doesn't supply any 64-bit drivers. Drivers (.DLL's really) are loaded into the same process that calls them, i.e.: your application. You cannot mix 32 and 64-bit code in the same process, so you cannot have a 64-bit app interact with an Access (Jet) database.
You have to recompile your app as x86 only. There are no 64-bit drivers for Access, so you're database code won't work if you leave your app compiled as AnyCPU. AnyCPU will result in your application being JIT'd as a 64-bit app when run on 64-bit Windows and 32-bit when run on 32-bit Windows.
Your other option is what Luc said. Drop using Access and switch to SQL Server Express. SQL Server has drivers for both 32-bit and 64-bit Windows.
There is a windows service created and I am trying to start the service from service manager. I am getting an error stating that the service stopped unexpectedly after start. This is happening in Win Server 2008.Prior to that service worked fine in Server 2003.
Do you have error/exception logging implemented in your service? If yes check the logs.
I would also suggest you to check the event log for related entry. In most cases, the error will be logged here.
You can navigate to event log in Win 2008 Server by clicking Start->Programs->Administrative Tools->Event Viewer. Check entries in Windows Application Log.
If you still don't find the problem, the last option will be debugging the service which won't be required if you have proper exception/error logging in your service.
false, SslProtocols.Tls, true);
An unhandled exception of type 'System.NotSupportedException' occurred in System.dll
Additional information: The server mode SSL must use a certificate with the associated private key.
I dont know what's wrong in certificate.I also provide the privateKey file in certificate
Some one tell me the reason ...
OK, can someone here confirm for me that MS screwed up here?
VS2008 allows you to use Debug.WriteLine to send data to debug stream where I can pick it up via a tool like DebugView.
VS2010 DOES NOT seem to allow this at all. I can see the debug data in the immediate window in the IDE but nothing appears to make it out past there...
If I run the EXE file I created in VS2010 as an administrator (right click and use the run as admin option) I can see the output written to the DebugView window but can't obviously catch any errors in the IDE and use that like normal.
VS2008 allows me to see the data in both areas without having to run as an admin at all.
If I start the process outside of VS2010 and see the debug in the debugview window then attach to the process using the IDE, the IDE horns in on the debug stream and stops it from going to debugview also.
I really don't get this 'progress'.
BTW - I put this post here because I was really NOT sure where to put it... this is not a C# vs. VB thing.... Maybe an IDE thing but we don't have an area just for that
Yes, I know how to use the statements themselves. I have been using them for years now.
The oddness seems to be specific to VS2010 and how it allows, or rather does NOT allow the output from these statements to leave the VS environment.
In previous versions of VS I used to be able to fire up a unified debug collection tool like windebug and gather all my debug statements in one log file This was helpful when trying to gather coordinated debug between several different processes together in one area.
Now it appears as if the IDE gets in the way and blocks that ability. You can see the output from Debug.WriteLine in the IDE area but it never makes it out into the standard debug stream like it used to so collecting it together from several instances of VS at once is not possible.
This also means that now I have to write my debug statements to provide a date and time component in them where collecting them in the windebug tool used to do that for me, and once again, used to do it from several instances at once.
So does anyone have any tutorials or white papers on how to begin with a registry cleaner, I am working on an all in one utility that wields a service controller and process controller to help with a friends pc repair shop, I know how to manipulate the registry to an extent I just dont understand how it compares version numbers or seeks old information in th registry with the programs that are installed and spews out what the errors are.
I am using asp.net3.5. I want to create CMS development project and I got one CMS model project in demo version but don't understand that. How do I learn that concepts and work flows? If you know guide me.
i developed one application using Visual studio 2008 (5.1.6 connector) and another in VS 2008 (6.1.3 connector) and MYsql database used. But i am using one server. I want run both the application in one system so that i should not use another server.
We need to install both the connectors and particular applicationn should use particular connector. How to do this. So that i can run in one IIS.