Quickbooks Pro 2024 error codes when shipping FedEx

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. 

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.

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.

@Twi  

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?

This is the SAME error I'm encountering. Worse yet, when I try to put the Account Number into the pop-up or ANY information into the pop-up, the screen just FREEZES. Is there anyway around it? Is QB fixing the issues or link / data issues?

From the sound of it, there's NO SOLUTION for 2024 version is that correct?  The only way to resolve this issue is to downgrade to 2023 version and it'll work?  

I acknowledge the importance of fixing this as soon as possible, Rose. Let's do some troubleshooting and ensure the error will be removed. Doing so, you'll be able to use the program without any issues. 

There's no need to revert to the 2023 version. There are times when the program's installation files or modules can get damaged for various reasons. When this happens, they can't function properly, leading to issues like runtime errors and freezing behaviors.

To resolve this, we'll need to perform a clean install, which involves completely uninstalling the software from your computer and then reinstalling it. This process will remove the damaged files and modules, replacing them with new undamaged ones. It's like giving QuickBooks Desktop a fresh start.

Before we proceed, create a backup file of your company to prevent any potential losses due to unforeseen circumstances. 

To uninstall QuickBooks: 

1. Open the Windows Start menu. Search the Control Panel, then open it.
2. Choose Programs and Features or Uninstall a Program.
3. Pick the version of QuickBooks Desktop you want to remove from the list of programs. 
4. Hit Uninstall/Change, Remove, and then Next.  If you don't see this option, sign out and sign back into Windows as an admin. 

Once done, install QuickBooks Desktop. QuickBooks will automatically create new folders and rename your old ones.

If the issue persists, I recommend contacting our technical support to check this matter. If necessary, our expert team can refer this to our engineering team. 

For future reference, you can visit these resources as a guide in handling your shipping manager and QuickBooks Desktop:

• Intuit QuickBooks Shipping Manager
• Fix issues when QuickBooks has stopped working. 
• QuickBooks Desktop won't open. 

By following the troubleshooting steps, you can ensure that you can use the program with ease, allowing you to focus on your task. If you need further assistance, click the Reply button below. I'm always here for you. 

I have tried uninstalling and downloading ONE the computer and the method DOES NOT work. The issue presisted and I have called QB support twice. Both people were NOT able to solve my problem for me. Would someone be able to call me and assist me with the issue?

I can see that you did everything you could to fix the issue, Rose and I appreciate you for that. 
 

I'm aware you've already gotten in touch with our Phone Support team, but it's the best we can do given that they have all the tools required to look at your account through screen sharing. This way, they can further investigate what's causing the error and assist you in resolving this matter timely. They can be reached while using QuickBooks. 

Here's how:

1. In your top menu bar, go to Help, then QuickBooks Desktop Help.
2. Click Contact Us.
3. Enter a brief description of the issue in our Ask a question (or tell us what's wrong) field.
4. Hit Continue.
5. Select We’ll contact you for a callback or Message Us to start an instant messaging session.

Be sure to review their support hours so you'll know when agents are available. In the event you're unable to reach out to Intuit through your books, you can get in touch through our website.

Moreover, you'll want to visit this article to learn more about the shipping manager: Intuit QuickBooks Shipping Manager.

Please keep us updated about the result, Rose. You can also reply to this thread if you have more questions about managing the shipping manager in QuickBooks. The Community team is open 24/7 to assist you. 

Thank you for this post.  I am having the exact same issue, with the same error message since I upgraded.  Quickbooks customer support has been no help, I have contacted them 5 times now and keep receiving a "this is a third party application issue" and then they end the chat, glad I found this post!  Im trying to figure out how to downgrade back to Quickbooks 2023 right now.

I would advise not listening to this post.  Sorry, but I did a clean re-install twice, then many conversations with Quickbooks help.  From what I can tell, Quickbooks 2024 simply does not work with the shipping applications.  Figure out how to return to using Quickbooks 2023.  Support was unable to help.

NOTHING works. My IT even refresh the entire computer just to test out if it our computer problem or QB problem. After refreshing the computer, reinstalling a few times, we have come to the conclusion that this is a QB problem!  

QB needs to fix this 2024 issue. It's making our shipping extremely DIFFICULT. 

I acknowledge the impact of this error on your shipment processing, Rose. Let me guide you through some troubleshooting steps to resolve the issue and get your business back on track.

As mentioned by @AlverMarkT, we have an ongoing investigation where users encountered an error when using the Shipping Manager (INV-73387). Alternatively, you'll have to register the Ship Rush ocx file again and rename the Shipping Manager folders to move past the error. I recommend working with an IT professional when performing these tasks.

Here's how to re- register Ship Rush ocx file:

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

Rename the Shipping Manager folders:
 

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

If none of these suggestions work, I recommend you reach out to our Technical Support Team and subscribe to the notification list to receive email updates. Furthermore, browse through these resources to gain more insights about the Shipping Manage feature and managing sales transactions:
 

• Intuit QuickBooks Shipping Manager
• Sales and customers
  
  

We appreciate your patience while we're working through this. Feel free to visit the Community again if you have other QuickBooks concerns or additional questions about the Shipping Manager feature. I'm always ready to provide the assistance you need. 

One of the big problems is in the "Shipping Window" that Pops up when you are shipping something.  It uses a Legacy 32 intergrader (this is a Microsoft application). When you first start QB and ship something the window will pop up but if you don't wait about 30 seconds for the integrator to fully open...The program will freeze and you have to restart QuickBooks (QB).  We find ALWAYS waiting about 30 seconds to start shipping something keeps the system from freezing.  

After the initial shipment is made the pop up screen does not pop up anymore...but it is the icon is in the Microsoft windows systems tray. If you don't click on the icon QB will not let you do anything else.

Microsoft says it is QB problem and QB says it is a Microsoft problem. The fact is this worked before the 2023 and 2024 QB upgrades, so I say it has to to be a QB problem.  This is very annoying and QB doesn't seems to be able to fix it.

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.

The solutions that are painstakingly listed and followed do nothing to fix this issue.  I also tried to call technical support for help and they are too busy to call back until Friday....No idea what is going on in this company but they are not very customer service oriented.  We will continue to look for other options - they are failing their customers. 

This method that QB has suggested DOES NOT work. In the 2024 QB, there is no ZRush_ShipRush9_QB.ocx file. QB has mess this one up for sure. 

As many others have mentioned, QB FORCED us to upgrades, but FAIL to test to ensure all the modules works. It's extremely inefficient and inconvenient that our team have to TEST to ensure shipping works every morning. It has become a new habit of ours. A softwares needs to work the way it's intended to work. QB is NOT cheap or FREE. 

The workaround for us is open up QB --> go to a processed invoice --> click shipping --> click which ever shipping service you use --> the shipping window will pop-up --> wait for 10 seconds and type in a number anywhere. IF it freezes, close the QB and reopen. 

Once reopened, click on file and run through the process as if you are setting-up a shipping information for the first time. Once the set-up box is open, try typing a number on any of the boxes. IF you can type a number without it freezing, that means your shipping is work. If it freezes, then you'll need to start the process over again.

This is such a STUPID workaround. QB, fix this issue NOW!

@Anne16720 

We will continue to look for other options

Once you're ready to move on, use the trial version of QB Desktop Enterprise to access your historical data for good.Then you may start from scratch in the new program to lower your conversion costs.

I am planning on moving to other opinions since I heard 1) QB has known this issue since 2023, but failed to address it and 2) QB desktop 2024 is the last desktop version they'll provide. 

FYI - Sage has a very similar system. There are pros and cons in every system, but I seem other small business owners moved over to sage to save on all these headaches that QB won't fix. 

@HelloRose  Wow!  I haven't heard that 2024 is the last version being produced.  Can I verify this somewhere?  We have a huge system here and we would need to start planning a transition sooner than later!

Thank you for the suggestion.  I am starting a file with all the info I can find to make our transition smooth.  We really do hate the upheaval and losing access to 25+ years of history but it seems we are not being left with much choice.   Maybe I will start a new post #QBWalkaway so I can get all the ideas in one place. 

Thanks again!

My IT saw it in a form somewhere. He was like "Oh wow, 2024 is the last version QB will provide for Desktop version." Hummm, we will have to figure out how to repoint / reset-up your files, which is a HUGE headache.