We are now moving our classic ASP application on the new server window 2012 R2. We are using Paypal for online transactions. Can you please help us to install correct paypal software ?
Related
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.
On my development machine Lync 2013 client and Skype for Business both applications are installed. When attempting to call LyncClient.GetClient() compiled using the Lync 2013 SDK against Skype for Business the following exception is raised.
Generic COM Exception. Code is 0x80080005.
If I uninstalled the Lync 2013 client then it works perfectly.
For the Lync 2013 client development I have also used Lync 2013 SDK at that time I didn't get any exception.
Can anyone tell me that why this exception is raised when both applications are installed?
What do you mean by "Skype for Business"?
AFAIK the clients can't be installed at the same time (which is most likely the reason for problems I think). So you can only have one client installed at any one time.
Also the clients are confusing as well.
There are:
Lync Basic Client (with windows updated to Skype for Business 2015 UI)
Lync (full) Client as part of Office Professional Plus 2013 (with windows updated to Skype for Business 2015 UI)
Skype for Business Standalone (Office 2016 post install)
Does anybody know how to get export to XLSX support for SQL Server 2008 R2 Reporting Services without upgrading to SQL Server 2012 or using any 3rd party tools?
Apart from developing your own render? Nope. I haven't been able to find ANY information on that by the way.
Apart from going to SQL Server 2012 (a 3rd party renderer may be more cost effective) you could develop your own ASP.Net app while using EPPlus that would link from the report. This stackoverflow post may help start you off with the code.
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
Can both clients be installed and used at the same time ?
The purpose of using both is based needs to develop for Lync 2010 while still using Communicator 2007 in a corporate environment. Or would a developer be forced to have two different machines/VMs/boot environments ?
No - you can't run both side-by-side. Installing Lync will uninstall Communicator.
However, you can use a registry hack (unsupported, unfortunately) to enable your copy of Lync to run against your OCS infrastructure. This works for R2, not 100% sure about R1.
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Communicator]"DisableServerCheck"=dword:00000001
If you're serious about Lync development, the best solution is to build a server environment specifically for developing against.