We received another order last night through Google Checkout that was successfully charged that did not get processed through the cart.

I'm posting all of the error codes below from this morning back through Aug 30 from my integration console. Can a tech PLEASE have a look and see what these issues are. Obviously there was a problem as the order is in my google account and not my store.

I've left other posts of similar issues, where someone said they were looking into it but did not get another response.

If you need ANY other information I would gladly give it to you. Please just get this sorted out.

I also have the same issue where orders are showing up in Google Checkout but are not coming back to Netsol to subtract the inventory an to show that an order has been placed.

« Back to Integration Center

Integration Issue Detail
Related order: 800821315214831
Time of occurrence: Sep 9, 2009 2:02:31 AM EDT
Error: We encountered an error trying to access your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is java.net.MalformedURLException: no protocol: /page-not-found.aspx?aspxerrorpath=/Google.aspx
Warnings:

shopping cart 9/9/2009 12:40 AM Google Checkout

resulted in a semi-sale through google checkout - customer was able to use a free shipping method that should NOT have been available to his location. The order WAS NOT picked up by the cart at all.

Integration Console 1 - 8 of 8 issues
Date Type Order Description
Sep 9, 2009 3:14:51 AM CDT Error 552989376268034 We encountered an error trying to access your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is java.net.MalformedURLException: no protocol: /page-not-found.aspx?aspxerrorpath=/Google.aspx
Sep 9, 2009 1:33:02 AM CDT Error 552989376268034 We encountered an error trying to access your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is java.net.MalformedURLException: no protocol: /page-not-found.aspx?aspxerrorpath=/Google.aspx
Sep 9, 2009 12:53:08 AM CDT Error 552989376268034 We encountered an error trying to access your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is java.net.MalformedURLException: no protocol: /page-not-found.aspx?aspxerrorpath=/Google.aspx
Sep 9, 2009 12:45:30 AM CDT Error 552989376268034 We encountered an error trying to access your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is java.net.MalformedURLException: no protocol: /page-not-found.aspx?aspxerrorpath=/Google.aspx
Sep 9, 2009 12:43:23 AM CDT Error 552989376268034 We encountered an error trying to access your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is java.net.MalformedURLException: no protocol: /page-not-found.aspx?aspxerrorpath=/Google.aspx
Sep 9, 2009 12:42:53 AM CDT Error 552989376268034 We encountered an error trying to access your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is java.net.MalformedURLException: no protocol: /page-not-found.aspx?aspxerrorpath=/Google.aspx
Sep 9, 2009 12:42:51 AM CDT Error - We encountered an error trying to access your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is no protocol: /page-not-found.aspx?aspxerrorpath=/Google.aspx
Sep 9, 2009 12:42:44 AM CDT Error - We encountered an error trying to access your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is no protocol: /page-not-found.aspx?aspxerrorpath=/Google.aspx
Aug 28, 2009 3:13:05 PM CDT Warning - Merchant Item Id: 993 is not unique in this Shopping Cart.

We reported this problem to NetSol on 9/3. A ticket was created, and was told that it was being escalated to the ops team immediately, someone would be calling back. No one has called, but I looked at the ticket today, since we have been getting error messages for a week from Google, same as posted above.

Do you know, our ticket was marked resolved on 9/4/09 at 5:45 pm. I click the details link to read what was done, absolutely no information. WOW, just like the old days. DeJaVu

Something messed up the call back url, someone needs to resolve it!

Hi All-

There was a minor Google Checkout outage overnight last night. Our Ops team was able to work with Google to get it resolved, but you will get an error for any order placed during the outage. I do not have exact times as to when the outage occurred. If you have an issue outside of last night, I encourage you to place a ticket with Tech Support.

Rick, I'll look into your account and see what happened.

Thanks

Brian

11/3/2009 9:23 PM 11/3/2009 9:24 PM Google Checkout Google Checkout
not picked up by the cart, and the customer was able to use a free shipping method that should NOT have been available to his location.

Date Type Order Description
Nov 3, 2009 9:35:13 PM CST Error 951412941719340 We encountered an error trying to access your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is Send failed with code: 500. Response body was: There was no endpoint listening at http://coreservices.monstercommerce.com/13.10.7/core.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
Nov 3, 2009 9:28:15 PM CST Error 951412941719340 We encountered an error trying to access your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is Send failed with code: 500. Response body was: There was no endpoint listening at http://coreservices.monstercommerce.com/13.10.7/core.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
Nov 3, 2009 9:25:55 PM CST Error 951412941719340 We encountered an error trying to access your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is Send failed with code: 500. Response body was: There was no endpoint listening at http://coreservices.monstercommerce.com/13.10.7/core.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
Nov 3, 2009 9:25:23 PM CST Error 951412941719340 We encountered an error trying to access your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is Send failed with code: 500. Response body was: There was no endpoint listening at http://coreservices.monstercommerce.com/13.10.7/core.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
Nov 3, 2009 9:25:21 PM CST Error - We encountered an error trying to access your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is Sending failed with HTTP response code: 500. Response body was: There was no endpoint listening at http://coreservices.monstercommerce.com/13.10.7/core.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
Nov 3, 2009 9:24:46 PM CST Error - We encountered an error trying to access your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is Sending failed with HTTP response code: 500. Response body was: There was no endpoint listening at http://coreservices.monstercommerce.com/13.10.7/core.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.

I had two G00gle orders tonight that were processed and charged, but DID NOT come through the cart and were not issued order numbers. What's up with that?

I'm having the same issue. "Order Notification Failing"

Same here Classic Hostess.com

Date Type Order Description
Nov 4, 2009 7:04:35 AM CST Error 951412941719340 We encountered an error trying to access your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is Send failed with code: 500. Response body was: There was no endpoint listening at http://coreservices.monstercommerce.com/13.10.7/core.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
Nov 4, 2009 12:10:40 AM CST Error 951412941719340 We encountered an error trying to access your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is Send failed with code: 500. Response body was: There was no endpoint listening at http://coreservices.monstercommerce.com/13.10.7/core.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
Nov 3, 2009 10:11:20 PM CST Error 951412941719340 We encountered an error trying to access your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is Send failed with code: 500. Response body was: There was no endpoint listening at http://coreservices.monstercommerce.com/13.10.7/core.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.

This is what we got since Oct 28: I did file a ticket, technical told me it must of been a time out issue... I don't take it as an excuse.

Nov 4, 2009 12:29:55 AM EST Error - We encountered an error trying to access your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is Sending failed with HTTP response code: 500. Response body was: There was no endpoint listening at http://coreservices.monstercommerce.com/13.10.7/core.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details
.
Nov 4, 2009 12:29:17 AM EST Error - We encountered an error trying to access your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is Sending failed with HTTP response code: 500. Response body was: There was no endpoint listening at http://coreservices.monstercommerce.com/13.10.7/core.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.

Nov 4, 2009 12:27:36 AM EST Error - We encountered an error trying to access your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is Sending failed with HTTP response code: 500. Response body was: There was no endpoint listening at http://coreservices.monstercommerce.com/13.10.7/core.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.

Nov 3, 2009 6:13:49 PM EST Error 447742680977177 We encountered an error trying to access your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is Send failed with code: 500. Response body was: Shopping Cart Not Found.

Nov 2, 2009 11:56:03 PM EST Error 447742680977177 We encountered an error trying to access your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is Send failed with code: 500. Response body was: Shopping Cart Not Found.

Nov 1, 2009 11:52:25 PM EST Error 447742680977177 We encountered an error trying to access your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is Send failed with code: 500. Response body was: Shopping Cart Not Found.

Nov 1, 2009 2:51:24 AM EST Error 447742680977177 We encountered an error trying to access your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is java.net.SocketTimeoutException: Read timed out

Oct 31, 2009 12:05:04 AM EDT Error 447742680977177 We encountered an error trying to access your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is java.net.SocketTimeoutException: Read timed out

Oct 30, 2009 1:18:00 AM EDT Error 447742680977177 We encountered an error trying to access your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is Send failed with code: 500. Response body was: Shopping Cart Not Found.

Oct 29, 2009 1:30:52 AM EDT Error 447742680977177 We encountered an error trying to access your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is Send failed with code: 500. Response body was: Shopping Cart Not Found.

Oct 28, 2009 4:28:29 PM EDT Error 447742680977177 We encountered an error trying to access your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is Send failed with code: 500. Response body was: Shopping Cart Not Found.

Oct 28, 2009 2:28:38 PM EDT Error 447742680977177 We encountered an error trying to access your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is Send failed with code: 500. Response body was: Shopping Cart Not Found.

Oct 28, 2009 2:03:05 PM EDT Error 447742680977177 We encountered an error trying to access your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is Send failed with code: 500. Response body was: Shopping Cart Not Found.

Oct 28, 2009 1:54:44 PM EDT Error 447742680977177 We encountered an error trying to access your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is Send failed with code: 500. Response body was: Shopping Cart Not Found.

Oct 28, 2009 1:53:08 PM EDT Error 447742680977177 We encountered an error trying to access your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is Send failed with code: 500. Response body was: Shopping Cart Not Found.

Oct 28, 2009 1:52:28 PM EDT Error 447742680977177 We encountered an error trying to access your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is java.net.SocketTimeoutException: Read timed out

Oct 28, 2009 1:52:15 PM EDT Error - We timed out waiting for your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is: Read timed out. Your server must respond faster to merchant calculation callback requests.

Oct 28, 2009 1:52:03 PM EDT Error - We timed out waiting for your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is: Read timed out. Your server must respond faster to merchant calculation callback requests.

Oct 28, 2009 1:49:59 PM EDT Error - We timed out waiting for your server at https://ecompayments.monstercommerce.com/Google.aspx -- the error we got is: Read timed out. Your server must respond faster to merchant calculation callback requests.

Edited again when I realized that reply was from September. Please, someone from NS reply to this!

Having same issue here!

I keep getting messages from GC about errors. This is not only annoying but very unprofessional. I guess I have to turn off GC for now.

Well, Network Solutions®® is on top of things as usual. What a wonderful shopping cart!


I just love it and I have recommend it to all my former friends.

Hi All-

I apologize for any frustration you are experiencing, however, I do have to point out that for security reasons, we're not able to troubleshoot issues with payment gateways in the forums. I ask that you please open up a service request or give us a call at 888.252.3266. If you have an open issue that you feel is not getting the attention it deserves, please feel free to PM me with the service request number if possible and I will be happy to take a look.

Brian

I called when this started and was told that I should wait up to 4 hours for GC to notify my site of the order. Before 4 hours was up I received notice from GC that there were multiple errors so I CALLED. Guess what, 'it's a known issue and we are looking into it'. I received no SR#. Now what?

I'm still getting emails from GC about this issue. Fix it.

Hi Loxalot -

I'll have to research the issue log for the details, but I will point out that as with most 3rd party integrations, it may not be 100% within our control to fix. You wouldn't receive an SR# for a "known issue" because these are usually only resolved during a scheduled release.

Thanks

Brian

So in other words, the last update messed up the communication with GC but you're going to wait to fix it until the next update. Good to know. Should I wait to pay my next month's fee too?

we had 2 overnight orders that went through google checkout without issue. (IMG:http://forums.Network Solutions®®.com/style_emoticons/default/cool.gif)

Well the last update didn't have anything to do with Google Checkout, as I mentioned the problem could be outside of our control. However, I'm not sure how the fee structure works for your account with Google Checkout. But I'm sure you can call their support line and they'll be more than happy to discuss it with you.

Thanks

Brian

Ok so first I'm told this is a known issue and now you're telling me I need to call Google to fix the problem.

Someone with actual knowledge of this issue that works at NS please give me a straight answer.

Hi Jim -

I apologize if there was any confusion, but I what I have said (over several posts) is that a known issue is a defect with the software that is already logged, and therefore there is no need to have an open service request as the problem is already known and would need to be fixed in a scheduled update, if this is possible.

The last scheduled update made no changes to our software configurations for the Google Checkout integration, so it would be unlikely for it to be impacted by that release. Furthermore, since it is a 3rd party integration, there is part of the software that we are in control of, and part of the software that is the 3rd party, which we have no control over. If the defect lies in the side that is beyond our control, then obviously it is hard for us to resolve those issues.

Since in this case you are equally a customer of ours and the 3rd party, you should also investgate the issue with their support as well. Often it could be a configuration or other means of resolving within their control. If the issue is within our control, we will work as as diligently as possible to get the fix into a scheduled release.

Thanks

Brian