Skip to main content

Get 50% OFF QuickBooks for 3 months*

Buy now
Switch to QuickBooks and 70% off for 3 Months
Talk to Sales: 877-683-3280
Hours
Mon - Fri, 5am - 6pm PST
Sat - Sun, 7am - 4pm PST
Product support & help
Need help signing in?
T
Twi 12
April 23, 2024
Solved

Quickbooks Pro 2024 error codes when shipping FedEx

  • April 23, 2024
  • 4 replies
  • 3 views

We just upgraded to Desktop Pro 2024 and the FedEx shipping manager is getting Error codes.  It is along error that starts with this code: DBISAM Engine Error # 11949 SQL parsing error - 

 

We can't ship anything through QB until this error gets resolved.

Best answer by Twi 12

@Twi 12 

It find several other errors though.

 

Can you still open your company file on QB Desktop 2021? Run the Verify/Rebuild Data utility. Did you encounter the same error message?


@4Gal Level 10

 

Thanks for all the great advice.  I did talk to a great Intuit rep in Mexico City last night and we went through every procedure in this blog. We also ran the Fix and Repair Toolkit on our server (that stores the data) and in the individual desktops. We could not even uninstall the shipping manager or change any of the FedEx settings.  The rep also recommended going back to the last QB version which was the Desktop Pro 2023.

 

We had to uninstall the the 2024 versions and reinstall it on ALL computers. That seemed to be the solution. We do not get the error messages anymore and QB does integrate with FedEx so we can now make labels from the invoices. So we did not have to go back to the previous version in the end.  The whole process including all the fix recomendations took about a day. If anyone else has this problem just try to reinstall the 2024 program and see it works on one user.  If it does then you can change on all other (if you are set up for multi-users).

 

The only problem is the LegacyWrapper 32 integrated App from Microsoft does not work properly (this runs in the back ground of the shipping integration in QB).  Instead of automatically opening in QB when you use the shipping manager, it will open in the Windows system tray. This causes a multi step process to ship something. The LegacyWrapper 32 is also unstable in the current configuration. It will freeze up and when it does you must close QB and reopen it...which is very time consuming and inconvenient. This was a problem we have had since the 2023 upgrade and it has not been fixed.

 

Microsoft blames Intuit and Intuit blames Microsoft...in the meantime we the customers pay the price.  It is sad we have to pay thousands of dollars for the ALL upgrades every year and the upgrades cause more problems than the previous versions.

4 replies

4
4Gal
Level 5
April 23, 2024

Run the Verify/Rebuild Data utility. Did you encounter any error message?

 

T
Twi 12Author
April 23, 2024

Thanks 4Gal,

 

Unfortunately that did not work.  It find several other errors though.

 

I am going to try the new post from QB that came in next.

 

This is the complete error code we are getting:

 

DBISAM Engine Error # 11949 SQL parsing error - Expected column name but instead found CargoAircraftOnly in INSERT SQL statement at line 1, column 1955
SQL: INSERT INTO Package (BOLD_ID, BOLD_TYPE, PackageTrackingNumber, RatesTotal, LabelRoutingCode, LabelURCData, PackageActualWeight, DeliverToAttnName, DeliverToPhoneNumber, PackagingType, MerchandiseDescription, VoidInd, PkgPublishedDimWt, PkgLength, PkgWidth, PkgHeight, PackageReference1, AdditionalHandling, CODType, CODFunds, CODCurrencyCode, CODAmount, DCISType, InsuranceType, InsuranceAmount, InsuranceCurrency, VerbalConfInd, VerbalConfPhone, VerbalConfName, Oversized, PackageReference2, PackageReference3, PackageReference4, PackageReference5, SpecialInstructions, DialInd, RateWeight, ShipDate, LabelTrkURL, LabelFilename, LabelFormat, RateBaseCharge, RateAdditionalCharge, RateMarkup, IsTestPackage, PostponedWeight, AdvancedSettings, DryIceFlag, DryIceWeight, PkgHasDeliveryNotification, PkgHasExceptionNotification, PkgHasReturnNotification, PkgHasShipNotification, PkgHasShipNotificationFax, PkgShipNotificationEMail, PkgShipNotificationFaxNum, PkgDeliveryNotificationEMail, PkgExceptionNotificationEMail, PkgReturnNotificationEMail, ShipperRelease, AddFreightChargesToCOD, UPSServiceType, DeliveryAddress, SenderAddress, ARSType, ShipmentID, SuppTrkNumber, EMailLabelURL, EMailLabelDateTime, EMailLabelUserID, EMailLabelPassword, IsProcessed, HistCompany, HistName, NonStandardContainerFlag, Carrier, RateDiscount, Tracking_DeliveryStatus, Tracking_DeliveryDateTime, LabelPackedData1, LabelPackedData2, LabelPackedData3, LabelPackedData4, RateCarrierCharges, RateListAdditionalCharge, RateListBaseCharges, RateListCarrierCharges, EffectiveCarrierCharges, RateListDiscount, RatesListTotal, HistZIP, HistAddress1, PackageAdmissability, CODTrackingNumber, PkgHasInboundReturnNotification, PkgInboundReturnNotificationEmail, IsLargePackage, HoldForPickup, USPSCertifiedMail, USPSElectronicReturnReceipt, USPSAutomationRate, USPSMachinable, USPSShowReturnAddress, USPSReturnToSender, USPSGirth, ExternalTransactionId, CargoAircraftOnly, FDXPriorityAlertDetailContent, FDXPriorityAlert, RestrictedDelivery, RequireSignature, PkgHasInTransitNotification, PkgInTransitNotificationEMail, DeliveryConfirmation, FDXPriorityAlertPlus, Refrigeration, ProactiveResponse, ContainsBattery, BatteryMaterial, BatteryPacking, InsuredByShipRush, InsuranceCharges, FDXDangerousGoods, DryIceMedical, Shipment) VALUES (:BOLD_ID, :BOLD_TYPE, :PackageTrackingNumber, :RatesTotal, :LabelRoutingCode, :LabelURCData, :PackageActualWeight, :DeliverToAttnName, :DeliverToPhoneNumber, :PackagingType, :MerchandiseDescription, :VoidInd, :PkgPublishedDimWt, :PkgLength, :PkgWidth, :PkgHeight, :PackageReference1, :AdditionalHandling, :CODType, :CODFunds, :CODCurrencyCode, :CODAmount, :DCISType, :InsuranceType, :InsuranceAmount, :InsuranceCurrency, :VerbalConfInd, :VerbalConfPhone, :VerbalConfName, :Oversized, :PackageReference2, :PackageReference3, :PackageReference4, :PackageReference5, :SpecialInstructions, :DialInd, :RateWeight, :ShipDate, :LabelTrkURL, :LabelFilename, :LabelFormat, :RateBaseCharge, :RateAdditionalCharge, :RateMarkup, :IsTestPackage, :PostponedWeight, :AdvancedSettings, :DryIceFlag, :DryIceWeight, :PkgHasDeliveryNotification, :PkgHasExceptionNotification, :PkgHasReturnNotification, :PkgHasShipNotification, :PkgHasShipNotificationFax, :PkgShipNotificationEMail, :PkgShipNotificationFaxNum, :PkgDeliveryNotificationEMail, :PkgExceptionNotificationEMail, :PkgReturnNotificationEMail, :ShipperRelease, :AddFreightChargesToCOD, :UPSServiceType, :DeliveryAddress, :SenderAddress, :ARSType, :ShipmentID, :SuppTrkNumber, :EMailLabelURL, :EMailLabelDateTime, :EMailLabelUserID, :EMailLabelPassword, :IsProcessed, :HistCompany, :HistName, :NonStandardContainerFlag, :Carrier, :RateDiscount, :Tracking_DeliveryStatus, :Tracking_DeliveryDateTime, :LabelPackedData1, :LabelPackedData2, :LabelPackedData3, :LabelPackedData4, :RateCarrierCharges, :RateListAdditionalCharge, :RateListBaseCharges, :RateListCarrierCharges, :EffectiveCarrierCharges, :RateListDiscount, :RatesListTotal, :HistZIP, :HistAddress1, :PackageAdmissability, :CODTrackingNumber, :PkgHasInboundReturnNotification, :PkgInboundReturnNotificationEmail, :IsLargePackage, :HoldForPickup, :USPSCertifiedMail, :USPSElectronicReturnReceipt, :USPSAutomationRate, :USPSMachinable, :USPSShowReturnAddress, :USPSReturnToSender, :USPSGirth, :ExternalTransactionId, :CargoAircraftOnly, :FDXPriorityAlertDetailContent, :FDXPriorityAlert, :RestrictedDelivery, :RequireSignature, :PkgHasInTransitNotification, :PkgInTransitNotificationEMail, :DeliveryConfirmation, :FDXPriorityAlertPlus, :Refrigeration, :ProactiveResponse, :ContainsBattery, :BatteryMaterial, :BatteryPacking, :InsuredByShipRush, :InsuranceCharges, :FDXDangerousGoods, :DryIceMedical, :Shipment)

T
Twi 12AuthorAnswer
April 24, 2024

@Twi 12 

It find several other errors though.

 

Can you still open your company file on QB Desktop 2021? Run the Verify/Rebuild Data utility. Did you encounter the same error message?


@4Gal Level 10

 

Thanks for all the great advice.  I did talk to a great Intuit rep in Mexico City last night and we went through every procedure in this blog. We also ran the Fix and Repair Toolkit on our server (that stores the data) and in the individual desktops. We could not even uninstall the shipping manager or change any of the FedEx settings.  The rep also recommended going back to the last QB version which was the Desktop Pro 2023.

 

We had to uninstall the the 2024 versions and reinstall it on ALL computers. That seemed to be the solution. We do not get the error messages anymore and QB does integrate with FedEx so we can now make labels from the invoices. So we did not have to go back to the previous version in the end.  The whole process including all the fix recomendations took about a day. If anyone else has this problem just try to reinstall the 2024 program and see it works on one user.  If it does then you can change on all other (if you are set up for multi-users).

 

The only problem is the LegacyWrapper 32 integrated App from Microsoft does not work properly (this runs in the back ground of the shipping integration in QB).  Instead of automatically opening in QB when you use the shipping manager, it will open in the Windows system tray. This causes a multi step process to ship something. The LegacyWrapper 32 is also unstable in the current configuration. It will freeze up and when it does you must close QB and reopen it...which is very time consuming and inconvenient. This was a problem we have had since the 2023 upgrade and it has not been fixed.

 

Microsoft blames Intuit and Intuit blames Microsoft...in the meantime we the customers pay the price.  It is sad we have to pay thousands of dollars for the ALL upgrades every year and the upgrades cause more problems than the previous versions.

    AlverMarkT
    AlverMarkTModerator
    Moderator
    April 23, 2024

    I appreciate you for reporting this issue in the Community, @Twi 12.

     

    Upon checking on my end, our Product Engineers are working on a fix for the error you've encountered as of posting. However, I can still guide you through possible solutions to resolve this and route you to our Support Team if the problem persists. 

     

    This issue is usually system-specific, and I highly recommend collaborating with your IT expert for the steps outlined below. 

     

    One fix we can perform is to register the ShipRush OCX file. 

     

    1. Click on the Windows Start menu and select All Programs. Then, select Accessories.
    2. Right-click on Command Prompt and choose Run as Administrator.
    3. In your command prompt window you need to type this command to change your working directory and after that press Enter:
         a. cd c:\Windows\syswow64
    4. You need to type the following command in your command prompt window and press Enter to register the ShipRush file:
         a. regsvr32.exe “c:\Program Files (x86)\Common Files\Intuit\ShippingManager\ZRush_ShipRush9_QB.ocx”
    5. Click OK on the message that is displayed. 
    6. Reboot the computer and set up Shipping Manager again.

     

    If this doesn't work, rename the Shipping Manager folders. You can follow these steps:

     

    1. Browse to the following folders in Windows File Explorer:
         a. C:\Program Files (x86)\Common Files\Intuit\ShippingManager
         b. C:\Users\[WindowsUserName]\AppData\Roaming\Intuit\ShippingManager
    2. Right-click on the folder name, choose Rename and add OLD to the end of the name (…ShippingManagerOLD).
    3. Repair/Reinstall QuickBooks.
    4. Reboot the computer even if not prompted. 
    5. Set up the Shipping Manager again. 

     

    If you encounter the same problem shipping after the steps above, I'd recommend contacting our Support Team for further assistance. This way, you'll also be notified once the error you encountered is resolved. Here's how you can reach out to them:

     

    1. In your QBDT, go to Help, then select QuickBooks Desktop Help/Contact Us.
    2. Select Contact Us. Give a brief description of your issue, then click on Continue.
    3. Sign in to your Intuit account, select Continue and Continue with my account.
    4. We'll email you a single-use code. Enter your code and select Continue.
    5. Select to Have us call you.

     

    If you need a guide for setting up and managing your inventory after the issue is resolved, let me add this article as a reference: Set up Advanced Inventory in QuickBooks Desktop. 

     

    We'll be here in the Community if you have further updates on the error you encountered when shipping within the QBDT system. We'll do our best to assist.

    T
    Twi 12Author
    April 23, 2024

     

    So I followed the steps on the "ShipRush OCX file" fix.  But got this message..

     

    The module “c:\Program Files (x86)\Common Files\Intuit\ShippingManager\ZRush_ShipRush9_QB.ocx” was loaded but the call to DllRegisterServer failed with error code 0x800040005

     

    I will try to contact the support team by phone. Although they had this report when we upgraded the system on Friday.  They had a copy of the error report and were supposed to call me back on Monday 4/22/24 but never did.  That is why i trying to resolve this issue in the forum.

     

      A
      Anne16720
      May 22, 2024

      Since our update to 2024 last week we are dealing with the same issues - making shipping next to impossible through QB.  This is a known issue and we were basically forced into the 24 version from 21.  Not a good plan!  We have spent hours trying to resolve this with both support and our in-house IT.  At this point we need a solution and we need it today.  For the price of this product the solution should have already been provided.  

      For reference this is affecting all shipping, FedEx, USPS and UPS 

      Error Code DBISAM Engine Error SQL parsing error #11949 & also the Legacy Wrapper error - repairs, reinstalls and other suggestions have NOT worked for us.

      P
      pamross123
      May 29, 2024

      Everyone is having problems and there is no resolution which is scary. All the IT employees at intuit pretend it isn’t happening and your the first call. It’s all BS. 

        Need QuickBooks guidance?
        Log in to access expert advice and community support instantly.
        Terms & ConditionsAccessibility statement