I am transferring my website from Windows 2003 to Windows 2008 IIS7.5 and i have installed the Payflow_dotnet_2 (renamed to payflow_dotnet.dll) in the SysWOW64 folder. Also did the regsam and gacutil. But when i go to run the example code which is
Set client = Server.CreateObject("PayPal.Payments.Communication.PayflowNETAPI")
I get the error
ActiveX component can't create object
Not sure what is wrong. Cannot figure it out. Any help will be appreciated.
Thanks
Shawn
Related
I get a error with our database when I run it on a client PC
Our database contains a missing or borken reference to the file "MSOUTL.OLB" version 9.5
I developped a DB using Microsoft Outlook 15.0 Object library (I have Office 2013 on my development PC). I need this reference to send email with Outlook.
I wonder it is possible to compile the DB in order to run it a PC where Outlook 2007 is install ? It is an headhache to have the same environment on the development and the client PCs. Do you have any workaround or do I have to install Outlook 2013 on the client computer workstation ?
Thanks for your support
I finally find the problem. Some reports used DoCmd.SendObject to send the PDF report by email. This call returns the error. I replace it by a late bindint send email function (with Outlook.Application) and it works well on all the computers.
We have a classic ASP application we just migrated from Windows 2008 R2 to Windows 2012 R2 Core.
Apparently Core versions of windows don't include cdosys or cdonts and thus our application can no longer send email.
Most of the advice I can find suggests using system.net.mail for sending email which of course is a .NET technology and we're using classic ASP.
We do have .NET on our system but I'm not sure if classic ASP could talk to a .NET page for sending email?
Besides using a 3rd party COM utility like Persits ASPEmail are there any native ways of working around this?
We do NOT want to convert the server core instance to the full version of windows. That's killing an ant with a bazooka. This is only impacting two places in our code and everything else works just fine on core.
Unfortunately, CDONTS was superseded by CDOSYS some time ago. When migrating from Windows Server 2008 to Windows Server 2012 I had this exact same issue, but managed to find a fix.
It involves taking a copy of the cdonts.dll file from the Windows Server 2008 Server and adding it to the Windows Server 2012 server then registering it with the relevant COM subsystem without any need to change code or install a 3rd Party library.
Hopefully the same method will work with Core but I haven't tested it.
I am using Crystal Reports for Visual Studio 2013. The reports work fine on my local computer and in Visual Studio on the production server.
When I deploy them in IIS 7.5 I am getting the following error:
Failed to open the connection. ReportName
3400_4400_{A861BA52-167D-4EAF-AAAF-32B2FB34FFAA}.rpt
Operating System: Windows Server 2008 R2 Enterprise;
System Type: 64-bit Operating System;
Database: MySQL;
I copied the aspnet_clients folder in the wwwroot folder and in the application folder.
Any help would be appreciated.
Thank you.
There is 2 things which may cause this issue,
Are you installed the Crystal report runtime? if no, then here is
link1, link2. You can choose 64 bit option.
If you installed CR-runtime, then crystal report does not have connect to sqlserver. So for this, if you able to check your local crystal report with prod sqlconnection, check that and still you have issue, means you are not give sql server credential to crystal report at run-time. Check this link.
Crystal Report throws 'Failed to open the connection.' only on postback
http://www.codeproject.com/Questions/667950/crystal-reports-connection-to-sql-server-database
http://aspalliance.com/532_Understanding_the_Login_Failed_Error_in_Crystal_Reports.3
I have some updates!!! I can't believe this was the issue....so frustrating!!!...
On my production server I only created a User DNS...which worked fine with Visual Studio...but not with IIS. After I created a System DNS the report worked fine in IIS as well...
I have tried using Set-Culture, but I found that this module is not available in powershell. I have have tried upgrading powershell, but this module is still not available.
Can anyone help me find another solution without using Set-Culture?
I am trying to upgrade my current Express edition to Express with Advanced Services for supporting full-text search.
The current system setup is:
OS version: Windows server 2008 R2 web server 64 bit
SQL Server 2008 R2 Express, SP1, v10.50.2500.0
I have downloaded the SQL Server with Advanced Services. I am unable to upgrade the edition. The installation step goes without any issues and even getting Edition upgrade completed page. But once I click the close this page, an error will pop up.
SQL Server Setup has encountered the following error: Invoke or
BeginInvoke cannot be called on a control until the window handle has
been created.
Can some please assist me here to the right direction?
I could see that the version of SQL Server Express with Advanced Services is 10.50.1600.1. Is this the cause? So should I downgrade the sp1 to normal Express r2 edition before upgrading?
Downloaded link for the Express with advanced services http://www.microsoft.com/download/en/details.aspx?id=25174
I got it working finally!!
I was getting the below error previously. It is a bug and is related to UI. So i have upgraded using the command line that too in QUIET mode to prevent any UI intervention.
"SQL Server Setup has encountered the following error:
Invoke or BeginInvoke cannot be called on a control until the window handle has been created."
Following are the steps i used:-
Downloaded the latest sp1 for SQL Server 2008 r2 with Advanced Services (SQLEXPRADV_x64_ENU.exe) from http://www.microsoft.com/download/en/details.aspx?id=26729
Extracted the SQLEXPRADV_x64_ENU.exe to D:\SQL2008
Open command prompt as "Administrator"
Executed the following commands
D:\sql2008\setup.exe /ACTION=editionupgrade /INSTANCENAME=MyInstance /IACCEPTSQLSERVERLICENSETERMS /FEATURES=SQL,RS /INDICATEPROGRESS /Q
*MyInstance is your sql server instance name
*/INDICATEPROGRESS will show the setup progress to command prompt(For a confirmation :) )
You can follow this doc for more setup parameters
http://msdn.microsoft.com/en-us/library/ms144259(v=sql.105).aspx
Verified the upgrade has been successful.
Unfortunately FULL-TEXT Search feature was not enabled.
So Run the setup.exe as normall(double click) and added "FULL-TEXT Search" feature to the existing instance.
Everything works fine now. Thank you all.
I can verify that this bug and the same resolution also apply to SQL Server 2008 R2 Express SP2 v10.50.4000.0