Thanks Nick
Thanks Nick
Hi Nick,
Sorry it took a while to respond, as the holidays intervened...
There aren't any changes to the desktop return codes for 15.1.3 - they're still "SUCCESS", "DECLINED", and "TIMEOUT". For "TIMEOUT", you need to have an nCCQuery method set up; there's a stub in the C# sample template. nCCQuery doesn't come into play for a SUCCESS transaction.
Does the second call to nCCAuthOnly_Custom fail with an Omnis error before any of the C# code is invoked? In the middle of the C# code? or on its return to desktop?
Henry
I am having a problem trying to register the DLL. I am using regasm.exe and get the message successfully registered, How ever, iMIS fails to find the file and displays the message "The Xtender component for Credit Card Authorization cannot be loaded. Please check your system setup."
I am using the following to register the DLL and the TLB. I am putting the files in ..\iMIS15\ActiveX.
%SystemRoot%\Microsoft.NET\Framework\v2.0.50727\regasm.exe CCAuthTemplateCSharp.dll
%SystemRoot%\Microsoft.NET\Framework\v2.0.50727\regasm.exe CCAuthTemplateCSharp.dll /tlb
Any suggesstions as to what I am doing wrong?
Tom
Hi Tom,
A couple of things Nick and I tried for this issue follow.
(1) Maybe there's an existing registration of the VB6 PayPflowPro .ocx that's conflicting. Try unregistering that .ocx with regsvr32 /u, and then search the registry for "PayFlowPro". If there are any additional registrations, delete them. Then re-register using regasm.
(2) In some cases, regasm alone doesn't completely register the component, but building the solution in VS does. That doesn't help with deployment, of course. The difference in the registry is a "CodeBase" entry, with a path to the dll. Maybe I just need to add it to the ComRegister function.
For a workaround, you can add two new REG_SZ values manually in regedit.
Go to HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{8C828D4E-FE28-4126-8BBB-007C6FFA785A}
(the key may differ by OS, I'm not sure - just search for 8C828D4E-FE28-4126-8BBB-007C6FFA785A)
under "InProcServer32", add a new key named CodeBase with value like this (your path will vary - note the forward slashes instead of backslashes in the path)
file:///C:/iMISpath/AX controls/CCAuthTemplateCSharpUserControl.dll
under InProcServer32\1.0.4048.18779, add the same CodeBase key
Keep me posted...
Henry
Custom OCX Deployment steps
The above should do it. I was going to send screenshots, but did not see a way to attach documents. If you need that send me an email at nsrdarev@hotmail.com and I will send the registry screenshots.
Hope it helps!!
Thanks Nick
Champagne for everyone! I was able to get it to work, yea!
My problem was I was creating a new GUID for the several different sets of test code. The sample code says:
// Be sure to get your own Guid via "select newid()", guidgen.exe, etc.
[Guid("8C828D4E-FE28-4126-8BBB-007C6FFA785A")]
//[Guid("0F9CF41E-51F7-4EF9-B1C5-13B50247E85A")]
So, I was never able to find the one you guys were telling me to look for. Once I figuried it out, I was able to delete all the bogus reg entries and then edit the correct entry. It still gave me an error until I ran rhe following command to create a new type library. Then it worked.
%SystemRoot%\Microsoft.NET\Framework\v2.0.50727\regasm.exe CCAuthTemplateCSharp.dll /tlb
Thank you both so very much for all of your help. It never would have happened without your guidance.
Thanks Tom
I am getting this message when entering a payment transaction.
Thanks Tom
---------------------------
Custom gateway not properly installed
---------------------------
The payment type entered for this transaction requires a Custom Gateway for credit card authorizations. The custom gateway is not properly installed on this workstation.
The authorization for this payment transaction will time out.
Please contact your system administrator or the developer of your custom gateway application before processing payments using the specified payment type.
(nCCAuthOnly_Custom)
---------------------------
OK
---------------------------
Hi - I will check my notes tomorrow and send any instructions I have for deployment - I installed on 3 user PCs and the custom DLL is working fine with 15.1.3
I am at a client today. I will retest and respond tonight.
Would it help to send you the project source to have a look at? 2nd set of eyes never hurts. Really basic with hard coded values for now - just want to get the calls going OK between iMIS and the DLL before doing detailed logic.
I used the sample template and presentation info from Innovations 2009 that was a big help. Thanks for that!
My code looks very similar and I am having exactly the same problem.
First transaction goes through fine but the second one immediately causes an omnis error.
I have been working with Henry on this and we just got it resolution the other day.
Henry provided a new template that fixes a problem with the sample from Innovations 2009. We tested and it works great. I used to call a CC provider web serviice.
Henry should be provding a new template soon to the community.
Let me know if you want to discuss,
I am really quite desperate to get this working.
If you could provide me with any information I would be eternally gratefull.
Is the template very different from the Innovations 2009 one. Would it be possible to obtain a copy?
http://www.imiscommunity.com/ccauthtemplatecsharp_updated
If you have questions or problems, please post them on this thread.
It looks like Henry has put out the new template - that should do the trick for you.
If you wanted to discuss, you can email me at nsrdarev@hotmail.com.
Custom iMIS 15.1.3 OCX
The problem actually seems to happen on any 2nd transaction - success or fail - so at least the problem is consistent, First transaction works and second transaction fails.