Quickbooks SDK, XP and version 24.0.4006.0 woes - windows-xp

We're a 3rd party software suite that interfaces with Quickbooks via the QB SDK. A dozen+ of our customers are using Windows XP (yes), and some of them very recently installed QB's update 24.0.4006.0. Which has broken the programmatic interface before our app and QB. Specifically, our XP customers are reporting back "procedure entry point EnumProcessModulesEx could not be located in the dynamic link library PSAPI.dll". QB itself is working, for now, which is putting focus on our software at this point.
Anyone else seeing this conflict, between 24.0.4006.0 and XP ? Beyond trying to back out the 24.0.4006.0, or getting these custs off XP, could anyone suggest a workaround ?

all:
info this AM on this problem, workaround : "You can use an R5 or earlier version of QBXMLRP2.dll to fix the problem until fix is available."

Just to add some additional information.
Intuit has officially ended support for Windows XP with their QuickBooks product line. Pop over to Intuit and check out the requirements documents, specifically the Operating System support for details.
Right now, the only way to restore functionality would be to get the user to uninstall QuickBooks completely from their PC, then have them reinstall QuickBooks. Do not take them past R5 (release 5, IE: update/service pack 5) and the DLL will still be functional.
Full details on this re-installation process are available from Intuit at http://support.quickbooks.intuit.com/support/articles/SLN86786

Related

Not able to install software on macOS using installer

I just bought a new MacBook Pro 2016 Edition about 2 weeks ago.
I installed a bunch of applications and software so far by copying them into Applications Folder as well as by following installer wizard.
Now today I tried to install Wireshark using installer wizard. I tried to install teamviewer too later today which also uses installer wizard. And both give me the same error.
I really need to resolve this because I need TeamViewer soon and I'm not finding anyone else facing this issue online anywhere.
Please advise.
Thank you
I also encountered such an error before,to solve it dont copy the pakage to your app folder, but instead open it with admin powers and that should fix the issue.
If you have purchased this software then you can call the tech support, else dont call them it can put you in danger for installing pirated software.
I looked everywhere. Didn't find a viable solution. But then reinstalled the OS. Which didn't affect any of my data or installed application. I got the whole Operating System the same way I left it. But resolved the issue I was facing.

Setup required to communicate with QuickBooks

Sorry if this is a dumb question but I have spent hours looking for a solution.
I want to connect to a QuickBooks Company file that is installed on a server from a workstation that is on the network.
I am running the AddCust.exe that is supplied with the QuickBooks SDK.
What do I need to install on the server to make this work.
I am running the executable on the workstation. Do I have to have QuickBooks installed on the workstation that I want to run this app? I have installed the ABXMLRP2Installer on the workstation.
I know this is old, but in case anyone is still searching....
This answer is based on Quickbooks SDK 11.0.
You need to install the SDK on the machine running Quickbooks.
Next, you will need two programs that are part of the SDK:
RDS6ServerInstaller.exe RDS6ClientInstaller.exe
You will find these somewhere in the SDK install location:
on my machine, they were in:
C:\Program Files\Intuit\IDN\QBSDK11.0\tools\Installers
Here is a good write up on how to get this going...
http://www.h2officesolutions.com/h2os_custguide/Customizing_the_RDS_server.htm
Use the sample program provided in the SDK called SDKTestPlus3 for testing.
Be prepared for some serious tinkering and time to get this going....
You don't need to install anything on the server if you install QuickBooks and the required SDK components on the workstation. It is also possible to use Remote Data Sharing (RDS) to access data on the server, but it is much simpler to install QuickBooks on the workstation as long as you don't mind using a license for that purpose.
SDK applications always require that SDK components be installed; SDK components do not come pre-installed with QuickBooks. In the case of the AddCust sample app, the QBXMLRP2 installer is what you need.

How to develop and run app for office 2013?

I want to develop some app for office 2013. my problem is when i searched for microsoft developer tools office 2013 i find only that link OfficeDevToolsForVS2012 . That link is all over the blogs even on microsoft site msdn.microsoft . The downloaded file run Web Platform API but it tells me that it can't find that product(i don't know how even i get it from microsoft link). So i want to know how to develop app for office using vs2012.
UPDATE**:
I found some exe file called officetools_bundle.exe that installed the required tools but when i run anything even the online samples i get this error
Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
any help.
This issue is solved not, but i still don't know what's the reason behind it.
All i did is i installed fresh Windows 7 64bit on my machine and then every thing is working like charm.

How do I tell I have Standard or Professional Edition?

We're using DataDynamic ActiveReports .Net 3.0 on Windows-XP and we're looking to upgrade to the latest version for Windows-7. Then we ran into a problem. We could not tell which Edition (standard or professional) are we using. I tried Google search adn it wasn't very helpful. We looked in the "Program Files" and in the "Data Dynamics" folder, we found there's no executable file. So, we don't know what we have.
Thanks...
It depends on your serial number. The installation is the same for both releases. Email or call the ComponentOne sales team with you serial number (or if you don't have the serail, send the registered user or purchaser) and they can tell you which edition you have a license for.
Alternatively, if you have the product installed on a developer machine already you could try just using the features that are included only in the professional edition (e.g. WebViewer, End User Designer Control) to see if they are showing an "Evaluation" message or not. If they show an evaluation message when you run the product then you have Standard. If they don't, you have Pro.

How do I make a custom .net client profile installer?

For .net 3.5 SP1, Microsoft have the new client profile which installs only a subset of .net 3.5 SP1 on to Windows XP user's machines.
I'm aware of how to make my assemblies client-profile ready. And I've read the articles on how to implement an installer for ClickOnce or MSI.
But I've been using Inno Setup for my project so far and I'd like to continue to use it (as an Express user, I can't easily make MSIs), I need to know how to use the client-profile installer in a custom environment.
There is an article on a Deployment.xml schema, but no indication of how to write one, package it or anything else. Can someone explain this process? Finding the articles I linked to alone was a painful search experience.
Microsoft has now shipped the Client Profile Configuration Designer (Beta).
This designer lets you edit the XML files with some limitations, this isn't a 'Google beta' by any means.
Information and download
Can you clarify: Are you trying to write an installer for your app, which depends on the Client-Profile, or are you trying to write a custom installer for the client-profile?
I haven't used it personally, but if it's anything like the dotnetfx 1 and 2 msi's, you basically have to just invoke it's executable yourself from your own .exe file, or from an Msi BEFORE the InstallExecuteSequence starts up - you can't "embed" those in your own app, MS go out of their way to tell you not to do that due to suckage of MSI.
Client profile works only on clean XP. If your user as .Net 1 or 2 installed, client profile wont install...
You have an offline version (integrating Full .Net3.5 Install in case Client Wont install) 200 to 300Mo don't remember
Online version will get required files.
You can call a silent install from the first steps of your install.