|
|
 |
Joined: 7/7/2010
Posts: 11
|
|
|
I've gone through all of the steps as shown in the manual, but I can't figure out how to join our QBMS account (that I applied and was approved for last week) to the one I create at Intuit Business Services (where I got the AppID/Login/Connection Ticket). I also tried to put through a transaction using the info from Intuit Business Services and got the following error:
We couldn't complete your payment.
Status : -1
Auth Code : *****
Message :
So, I'm more than a little confused at this point - can you please offer some assistance?
|
|
|
|
 | |
|
|
|
Joined: 7/12/2010
Posts: 6
|
|
|
I had the exact same error. This is what worked for me.
- We were using the app name instead of the app login. The app login is appname+domain. Like this. myapp.mydomain.com
- I used this url to create my connection ticket. Which is different than the one in the manual and in QB support forum.
https://merchantaccount.quickbooks.com/j/sdkconnection?appid=sessionEnabled=false
We specifically had trouble with the account being a developer account and not a live one. This was because there was a ptc following the merchantaccount part of the url. ptc and live accounts are not connected to each other at all.
|
|
|
|
| |
|
|
|
Joined: 7/7/2010
Posts: 11
|
|
|
Thanks for the reply. What about the initial step - appreg.intuit.com - should I use a different URL there as well to generate the AppID/Login?
Thanks!
|
|
|
|
| |
|
|
|
Joined: 7/7/2010
Posts: 11
|
|
|
I can see that the latter part of the process, receiving the connection ticket, can be achieved by going to the real versus developer Quickbooks Merchant Services site (Smith should update their manual to reflect what the real vs. test setup process is, btw).
I think the same issue may be at fault in the initial setup step, where I acquire the AppID and AppLogin from appreg.intuit.com. I was originally doing this by clicking on the link in the manual, which has a developer.intuit.com address embedded under the appreg.intuit.com text. I tried to connect the appID and AppLogin that I created at developer.intuit to the account I have at the real QBMS site and it didn't recognize the AppID. I've been trying to connect to appreg.intuit.com to see if that address has yet another "real" system that I should be using to generate AppId/Login, but the site has been down since 3pm yesterday.
Can you confirm whether my assumption here is the case regarding AppID/Login acquisition?
|
|
|
|
| |
|
|
|
Joined: 7/7/2010
Posts: 11
|
|
|
UPDATE: Ok, I did confirm what I assumed in my last post. All of the problems I've had so far are related to setting up development vs. production account information.
The latest breakthrough is that in addition to removing the "ptc" from the URL (note to info@connection.., there's also an "&" that needs to be dropped in after the AppId in the URL you gave me.), You should also check off "Production" instead of IDNbeta (PTC) in step 5 of the instructions. I spent 2 days figuring that one out (doh!). The manual really (*really*) needs to be updated to make it clear that the QBMS instructions are for setting up a test environment, not production, for which you'll need totally different instructions.
Anyway, after that change, my real merchant account was finally able to recognize the App ID that was generated from the "production-enabled" App registration and gave me a real connection ticket. So, the two pieces are linked now, but I'm still getting the error I first reported when I try to process the payment, so in a way I'm back where I started.
Any ideas?
Many thanks for your help!
|
|
|
|
| |
|
|
|
Joined: 7/7/2010
Posts: 11
|
|
|
Another UPDATE:
I've tried two methods to create the connection ticket and receive 2 different responses when trying to put through transactions on them.
1. Use the URL that info@thechicoproject gave me (with correction mentioned previously).
2. Use that same URL but change SessionEnabled to True
In the first case I get an application error on the DNN side.
In the second case I get the very first error that I reported, where the transaction couldn't be completed (in REd above in my first post).
Any help would be much appreciated. Thanks!
|
|
|
|
| |
|
|
|
Joined: 7/7/2010
Posts: 11
|
|
|
BTW, this is the application error on the DNN side that I was talking about getting when using ChicoProject's suggested URL:
Server Error in '/' Application.
Input string was not in a correct format.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.FormatException: Input string was not in a correct format.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. |
Stack Trace:
[FormatException: Input string was not in a correct format.]
System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal) +7469351
System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info) +119
System.Convert.ToInt32(String value) +63
DotNetNuke.HttpModules.Membership.MembershipModule.OnAuthenticateRequest(Object s, EventArgs e) +3564
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +68
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75
|
|
|
|
|
| |
|
|
|
Joined: 7/12/2010
Posts: 6
|
|
|
It sounds like you got the process right at this point.
We got this error too, when we started processing test transactions. The transactions were showing up in the QBMS for us even though we were seeing this error.
For us this error showed up on the confirmstatus control. You can tell which control you are in by looking at the url, you will see ctl/[something], that [something] is the actual file that is throwing the error. We fixed this by updating to the latest version of the store. However if I remember correctly I had to do an uninstall, then remove all references from the DB then do a fresh install of the module, before the error went away. The working version that we have at this point is 2.97.
|
|
|
|
| |
|
|
|
Joined: 7/7/2010
Posts: 11
|
|
|
We tried the uninstall/reinstall with the latest version and are still getting the error. We tried looking around in the database for other references to the module but i'm not sure if we're looking in the right places. Any chance you can remember what db references you had to remove after completing the uninstall? thanks again.
|
|
|
|
| |
|
|
 |
 |
Joined: 3/11/2010
Posts: 1979
|
|
|
I think he was referring doing a clean install of the module.
Clean Install Instructions
-------------------------------
- From the dnn->host menu uninstall all 3 Smith modules. Make sure you check the delete files box when you uninstall
- Confirm that all stored procs and tables with a prefix of smith in your database are deleted
- Confirm that all files in /desktopmodules/smithregistration are deleted and the folder is removed
- Install the latest module v3.24
- Configure the module setting and test
Scott Kelly
Project Manager
|
|
|
|
| |
|
|
|
Joined: 7/7/2010
Posts: 11
|
|
|
We've done this a few times and the error is still occurring. Note that the purchases are going through on the QBMS side, and if you refresh the page after getting the error message, you see the confirmation information. The only piece of information missing is an "Invoice Number" and we have a very slight suspicion that the error is happening due to that piece of info, but could be a red herring.
|
|
|
|
| |
|
|
|
Joined: 7/12/2010
Posts: 6
|
|
|
When I uninstalled the module it left tables and stored procedures in the db. I manually removed them by dropping all the tables and sps from the db. I did this by running a script to identify all tables and stored procedures with "smith" in the name, then dropping them. After that I reinstalled the latest version (2.97 at the time), and it started working. For me the problem was specifically in the confirmstatus.ascx and confirm.ascx files and their corresponding dll files. Which version are you installing? Have you checked the hotfixes, and upgrades that are available?
|
|
|
|
| |
|
|
|
Joined: 7/12/2010
Posts: 6
|
|
|
I didn't see this post until after my last reply. I am almost competely certain that this is a bug in the store module and not due to an error in configuration. I contacted the developer to help me solve my issue, and it seems to me that that would be your best course of action. It is possible that the code that fixed this problem for me is not included in what you have, and no amount of fiddling on your end will change that, unless you have the source that is. They were able to get me updated and running fairly quickly, and have been very helpful.
|
|
|
|