We have a classic asp application that takes advantage of WDDX libraries on Windows 2003. We are trying to update to Windows 2008r2. We aren't updating to Windows 2012 for separate reasons.
We use this library on Windows 2003 http://www.finwin.com/Dev/wddxsdk/2__Software_Libraries/Installation.html#COM.
I installed this same library on Windows 2008. I was able to run command "regsvr32 wddx_com.dll" without errors. Yet, when we run the app we are receiving the error " ActiveX component can't create object" on the line "set objExtranetWDDX = server.createobject("WDDX.Recordset")".
It looks like this post might have the answer you are looking for
how-to-register-a-32-bit-dll-com-application-on-windows-2008-r2
Related
We have a classic asp site that is hosted on windows server 2003 (32 bit). It has an early version of SAP client installed and from within the asp pages we hook into SAP R4 with a standard call to Set Myobj = CreateObject("SAP.Functions"), this all works. We are now porting the app to Windows Server 2012 and we have had to install SAP client version 7(the earlier client wouldn't install), when the app hits the above line I receive the 'ActiveX cant create object' error message. can I just install the DLL's from the windows Server 2003 and use RegSVR32 to register them, if yes what dll's do I need to copy and is there an order to register them? or do I have to do something completely different.
try using:
CreateObject("SAP.Functions.Unicode")
source - https://blogs.sap.com/2015/09/18/how-to-use-named-references-of-sap-activex-libraries-in-vba-for-easy-programming/
I have a legacy classic ASP website that I need to do some maintenance work on. My development machine is running Windows 7 64 bit, Visual Studio 2012 and IIS Express 8.0.
The ASP app is backed by a Microsoft Access database.
The website runs fine until it tries to establish a connection to the database, where it fails with the following:
0x800a0e7a - ADODB.Connection: Provider cannot be found. It may not be
properly installed.
If the ASP process is running as 64-bit and it is trying to use the Jet database engine then that won't work because there is no 64-bit version of Jet. If that is the case then you can either
install the 64-bit version of the Access Database Engine (ACE), available here, and tweak the connection parameters as required, or
get the ASP process to run as 32-bit
I had the same problem you mention in a follow up comment.
I tried to install the 64 bit version, but I could not because I have
Office 2010 32 bit installed.
You can force the 64 bit version of the Access Database Engine (ACE) from here to install with the 'passive' switch:
AccessDatabaseEngine_x64.exe /passive
I have a website which will use OleDB.12.0 to read data from an Excel worksheet upon upload. It works fine on my local PC. But when hosted in my production server I get the following error.
microsoft.ace.oledb.12.0 is not registered on the local machine
How can I correct this?
My production server configuration:
MS Office 2007.
IIS 7
VS 2010
Windows 2008 R2
SQL Server2008
Does your production server have Access installed?
In any event, try installing/reinstalling Microsoft Access Database Engine 2010 Redistributable to the production server.
Update
Another point: is your production server running 32-bit or 64-bit Windows? Choose the download appropriately.
Update 2
From this link it appears that using the 64-bit version will cause trouble on a 32-bit system, but the 32-bit version will work.
I need help figuring out what programs I need to setup a development enviornemnt on my new Windows 7 laptop. I have a LAMP background and I have only used ASP.NET once. The first time using ASP.NET I installed all the nessassary software along with Visual Studio Express with one click from asp.net.
This time around I qualify for free software from Dream Spark. I'm not sure what programs I need to download in order to get eveything up and running correctly.
These are the programs I think I need and are available from Dream Spark:
Visual Studio 2010 Professional
Windows Server 2008R2 Standard
SQL Server 2008R2 Developer
I have a few questions:
Would this be correct?
Am I missing anything?
Should I use the Windows Server 2008R2 Standard in this way or should I save this key for use in a production enviornment?
PS: Main effort here is to get more aquainted with ASP.NET programming web applications but I would also like to dabble in Windows desktop application programming.
no, Windows Server 2008R2 Standard is not compulsory to install to use Visual Studio 2010 Professional & SQL Server 2008R2 Developer,
you can install both in any os ( windows 7 too ).
My machine has windows 7 and when I try to create a project from VS2003 IDE that is Dotnet v1.1 I'm getting the following error message:
Visual Studio has detected that the specified web server is not running asp.net v1.1. you will be unable to run asp.net web application or services
I have searched Google and found some links for the same problem but I am still not able to create asp.net project v1.1 from VS2003 IDE.
Have you tried the following article:
How to install ASP.NET 1.1 with IIS7 on Vista and Windows 2008
It says Windows Vista / Server 2008, however I am fairly certain that the same applied for Windows 7.
If you are having trouble understanding a specific part of the article then can you tell us which bit?
Visual Studio 2003's lifecycle ended in 2007,
http://support.microsoft.com/lifecycle/search/default.aspx?sort=PN&alpha=Visual+Studio&Filter=FilterNO
At that time, Windows 7 was not yet released, and such products should not be ever tested on Windows 7 internally.
So my guess is that you should continue using it on an older Windows platform (XP or Windows Server 2003).