QuickBooks 2008 Remote Applciation Publishing & Windows Server 2008STD x64

Quickbooks 2008 Premeir Edition is installed and working on Windows
2008 Server x64 Standard Edition.

It appears to work well using Microsfot's new published application
feature with one exception;

When we attempt to print to the "QuickBooks PDF Printer", or to email
from within QB (which appears to use the QuickBooks PDF Printer as
well) we get the following error;

"Quickbooks cannot connect to your server because part of your company
data is currently in use".

I realize x64 is not supported, however publishing QB as an app is
very convenient and everything else seems to work without issue.

This seems like a simple QuickBooks PDF Printer (Amyuni PDF Creator)
x32/x64 print driver issue.

I have researched this group and Amyuni's support site and tried
several suggestions and upates, etc., all without success.

Any suggestions appreciated.

Thanks.

OK, I have managed to get QuickBooks 2008" send via email" working on
server 2008 as a Remote App. Here is what I did;

1. Reinstalled QuickBooks on Server 2008 Standard Edition x86

2. Elevated the user to administrator, logged on as the user via RDP,
ran IE7, went throught he initial IE setup and configured all security
settings to low (for testing). This did two things... First, it
initialized (created) the users profile and folders on the server, and
second, it configured the settigns in IE so that QuickBooks could run
its IE 7 interface.

Frankly, I think what solved the issue was IE7 and it would still work
in x64, but Im just trying to get it to work. I'll go back and play
with x64 later.

Remote Appa is such a cool feature!

I am still having a problem with XP SP-3 clients only where the local
printers dont map. This is not a problem with Vista clients.

Ideas anyone?


On Jul 7, 6:23*pm, bpowers <lwpow...@gmail.com> wrote:
> Quickbooks 2008 Premeir Edition is installed and working on Windows
> 2008 Server x64 Standard Edition.
>
> It appears to work well using Microsfot's new published application
> feature with one exception;
>
> When we attempt to print to the "QuickBooks PDF Printer", or to email
> from within QB (which appears to use the QuickBooks PDF Printer as
> well) we get the following error;
>
> "Quickbooks cannot connect to your server because part of your company
> data is currently in use".
>
> I realize x64 is not supported, however publishing QB as an app is
> very convenient and everything else seems to work without issue.
>
> This seems like a simple QuickBooks PDF Printer (Amyuni PDF Creator)
> x32/x64 print driver issue.
>
> I have researched this group and Amyuni's support site and tried
> several suggestions and upates, etc., all without success.
>
> Any suggestions appreciated.
>
> Thanks.

Update:

For whatever reason XP SP-3 did not update RDP 6.0.x to version 6.1.
This appears to be the casue of the printer mapping issues.

RDP 6.1 is not available as a stand alone install, it is only
available with SP3.

Contacting MSFT for support.



On Jul 8, 1:41*pm, bpowers <lwpow...@gmail.com> wrote:
> OK, I have managed to get QuickBooks 2008" send via email" working on
> server 2008 as a Remote App. Here is what I did;
>
> 1. Reinstalled QuickBooks on Server 2008 Standard Edition x86
>
> 2. Elevated the user to administrator, logged on as the user via RDP,
> ran IE7, went throught he initial IE setup and configured all security
> settings to low (for testing). This did two things... First, it
> initialized (created) the users profile and folders on the server, and
> second, *it configured the settigns in IE so that QuickBooks could run
> its IE 7 interface.
>
> Frankly, I think what solved the issue was IE7 and it would still work
> in x64, but Im just trying to get it to work. I'll go back and play
> with x64 later.
>
> Remote Appa is such a cool feature!
>
> I am still having a problem with XP SP-3 clients only where the local
> printers dont map. This is not a problem with Vista clients.
>
> Ideas anyone?
>
> On Jul 7, 6:23*pm, bpowers <lwpow...@gmail.com> wrote:
>
>
>
> > Quickbooks 2008 Premeir Edition is installed and working on Windows
> > 2008 Server x64 Standard Edition.
>
> > It appears to work well using Microsfot's new published application
> > feature with one exception;
>
> > When we attempt to print to the "QuickBooks PDF Printer", or to email
> > from within QB (which appears to use the QuickBooks PDF Printer as
> > well) we get the following error;
>
> > "Quickbooks cannot connect to your server because part of your company
> > data is currently in use".
>
> > I realize x64 is not supported, however publishing QB as an app is
> > very convenient and everything else seems to work without issue.
>
> > This seems like a simple QuickBooks PDF Printer (Amyuni PDF Creator)
> > x32/x64 print driver issue.
>
> > I have researched this group and Amyuni's support site and tried
> > several suggestions and upates, etc., all without success.
>
> > Any suggestions appreciated.
>
> > Thanks.- Hide quoted text -
>
> - Show quoted text -

I discovered that Server 2008's Terminal Services Easy Print
requires .NET 3.x.

Installed and problem solved.

Hope that helps someone.

On Jul 9, 1:20*pm, bpowers <lwpow...@gmail.com> wrote:
> Update:
>
> For whatever reason XP SP-3 did not update RDP 6.0.x to version 6.1.
> This appears to be the casue of the printer mapping issues.
>
> RDP 6.1 is not available as a stand alone install, it is only
> available with SP3.
>
> Contacting MSFT for support.
>
> On Jul 8, 1:41*pm, bpowers <lwpow...@gmail.com> wrote:
>
>
>
> > OK, I have managed to get QuickBooks 2008" send via email" working on
> > server 2008 as a Remote App. Here is what I did;
>
> > 1. Reinstalled QuickBooks on Server 2008 Standard Edition x86
>
> > 2. Elevated the user to administrator, logged on as the user via RDP,
> > ran IE7, went throught he initial IE setup and configured all security
> > settings to low (for testing). This did two things... First, it
> > initialized (created) the users profile and folders on the server, and
> > second, *it configured the settigns in IE so that QuickBooks could run
> > its IE 7 interface.
>
> > Frankly, I think what solved the issue was IE7 and it would still work
> > in x64, but Im just trying to get it to work. I'll go back and play
> > with x64 later.
>
> > Remote Appa is such a cool feature!
>
> > I am still having a problem with XP SP-3 clients only where the local
> > printers dont map. This is not a problem with Vista clients.
>
> > Ideas anyone?
>
> > On Jul 7, 6:23*pm, bpowers <lwpow...@gmail.com> wrote:
>
> > > Quickbooks 2008 Premeir Edition is installed and working on Windows
> > > 2008 Server x64 Standard Edition.
>
> > > It appears to work well using Microsfot's new published application
> > > feature with one exception;
>
> > > When we attempt to print to the "QuickBooks PDF Printer", or to email
> > > from within QB (which appears to use the QuickBooks PDF Printer as
> > > well) we get the following error;
>
> > > "Quickbooks cannot connect to your server because part of your company
> > > data is currently in use".
>
> > > I realize x64 is not supported, however publishing QB as an app is
> > > very convenient and everything else seems to work without issue.
>
> > > This seems like a simple QuickBooks PDF Printer (Amyuni PDF Creator)
> > > x32/x64 print driver issue.
>
> > > I have researched this group and Amyuni's support site and tried
> > > several suggestions and upates, etc., all without success.
>
> > > Any suggestions appreciated.
>
> > > Thanks.- Hide quoted text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -

OK, I've spent several days scouring the Internet and tweaking Server 2008 & QuickBooks to get this to work. I have successfully got QB Enterprise 9 working, WITH convert to PDF and email (using Outlook) over Server 2008 RemoteApp.

Note, I never did figure out how to get the PDF conversion working using the client computer via Easy Print like bpowers did. I opted instead to only use the host Server 2008's QuickBooks PDF Convertor printer.

Here were the steps I did:

1. Installed QB Enterprise and Outlook 2007
2. Edited host Server 2008's QuickBooks PDF Convertor printer: added a new port named "NUL:" (saw this on Internet for getting it to work on x64 OS)
3. Published QB Enterpise and Outlook 2007 as Remote Apps using TS RemoteApp Manager
4. Configured both remote aps' settings to NOT map printers
5. Configured RDP-tcp listener in Terminal Services Configuration to DISABLE LPT Port and Default to main client printer
6. From Vista client, ran Outlook RemoteApp to configure Exchange profile
7. From Vista client, ran QuickBooks RemoteApp, changed Preferences\Send Forms to use Outlook
   

Hope this helps someone. Trick for me was to make sure I wasn't passing client computers' printers. I tried all of the tips mentioned in this thread and a few others, but it wasn't until I disabled printer redirecting that the PDF conversion worked.

Update 1/27/10:

After easily spending 8 hours on my own researching and trying all the hoops (repair, reinstall, replace qbwpr32.DLL, delete Quickbooks PDF printer and re-create, etc.), and an hour on the phone with Intuit, Charlie, the Customer Service Representative FINALLY got this resolved:

There is an updated PDF convertor. It's called "PDF V 3.03" and the direct download link is h-t-t-p://w-w-w.quickbase.com/up/ba8uqfzbq/g/ref/eg/va/QBDPDF_303.exe (delete the dashes between h t t p and w w w to get it to work...can't post links on this forum until post 10 posts, and I will likely never have that many and am blatenlty trying to get around this lame security feature).

In any event, I can now save as PDF and email items on the computer and through Windows Server 2008 R2's RemoteApp using EasyPrint.

Hope this saves someone the hassle I went through!