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/
Related
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
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.
For this project I needed to install and run VS 2003 on Windows 7 using IIS 6.0 with Framework 1.1 on my sever because there was old VS2003 C# code on a remote server that needed updating and did not have VS 2003 installed only the DLL, PDB, aspx, and aspx.cs files. After porting the code over and making the needed changes on my local server, I discovered that while I could browse the page, I could not run the page with debugger and got this error: "... Unable to start debugging on the web server. There is no managed code running in the process. In order to attach to a process with the .NET debugger, managed code must be running in the process before attaching." I then started the application without Debugger and selected the w3wp.exe process for CLR in order to attach the process but I noticed that the process session was set to 0 and I still got that error again.
The following is done in IIS6 :
Application created.
DefaultAppPool (.NET framework 1.1 Integrated)(ApplicationPoolIdentity) is used
Browsing the web page works OK.
Authentication has Integrated Windows and ASP.NET Impersonation enabled.
I have runned aspnet_regiis from all the .net version in order
Set debug="true" in the web.config.
Thanks much for your help
Resolution:
Right click the ASP.Net project > Properties
select Configuration Properties > Debugging
Enable the below mentioned entries in 'Debuggers' frame.
ASP.Net Debugging
Unmanaged code debugging.
I had the same problem.
I fixed it.
Delete the virtual directory in IIS
Create the new virtual directory with different name other than the old one and configure the new virtual directory name in your visual studio solution.
I'm trying to deploy an ASP.Net application I developed to a Windows Server 2003 System but I get a error message when running the Site.
The first thing is that I get a Null Reference exception when I want to access my custom configuration section. So I figured that maybe the System.Configuration Assembly might not be installed. However I removed the reference and included the database directly into code to see if it works without.
But now I'm getting another error that a third party server control is not recognized.
Error Message: Server label
"trirand:JQGrid" unknown.
The same application runs just fine on my XP machine with IIS 6 installed so I wonder if I'm missing some installation. This is the first ASP.Net Application on that machine as before there were only ASP tools. I think that the .Net Framework 3.5 SP1 is installed but I'm not sure. Another question is if the ASP.Net is integrated into the .Net Framework of if I need a different install package.
Update:
I experienced a weird behaviour: I added the obviously wrong element <asdf> to the web.config file. On my development machine that gave me the expected error, but on the server nothing happened at all. So it seems like it some does not recognize my web.config file.
You need to check if the windows server system is loaded with the software your application required.
The folder v3.5 should be there in the following location.
C:\WINDOWS\Microsoft.NET\Framework\v3.5
Also you need to check if asp.net is installed on the system, if you are not sure then do install it, installing it if it is already there have no side effects.
To install asp.net type the following commands in DOS prompt.
cd C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
// then
aspnet_regiis.exe -i
Then also, confirm in IIS that correct version of asp.net is selected for your website.
To check; go to your website properties in IIS
then select ASP.NET tab then check ASP.NET version it should be 2.0.50727 for websites below .net version 4.0
Good Luck!