Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Connect with and learn from others in the QuickBooks Community.
Join nowWe 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.
Solved! Go to Solution.
@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.
Run the Verify/Rebuild Data utility. Did you encounter any error message?
I appreciate you for reporting this issue in the Community, @Twi .
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.
If this doesn't work, rename the Shipping Manager folders. You can follow these steps:
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:
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.
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)
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.
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.
You have clicked a link to a site outside of the QuickBooks or ProFile Communities. By clicking "Continue", you will leave the community and be taken to that site instead.