Emailing from Sage 50 / Outlook 2013 or Thunderbird within a RDS environment

Hi,

A client of mine uses Sage 50 within an RDS environment (Terminal Services).

Are there any issues or concerns related to emailing Direct Deposit paystubs with this configuration?

I have read through the following link, however, this is specifically for a desktop installation of Sage 50: http://sagecity.na.sage.com/support_communities/sage_50_accounting_ca/b/sage_50_ca_supporthub_blog/archive/2014/02/25/what-should-i-do-if-i-am-unable-to-email-from-sage-50.aspx?Redirected=true

For troubleshooting I have tried the following:

1) Installed Thunderbird x86 and PDFCreator on the server with Sage 50

2) Set Thunderbird as the default mail / MAPI handler.

3) Within the sample company database I made changes to one of the users to support emailing Direct Deposit paystubs.

4) When I attempt to create a paycheque and click on 'Email & Process' it indicates that it's printing something to PDFCreator and then promptly comes up with the following error:

NOTE: This is all performed whilst logged in as a Domain Administrator to the server where Sage 50 is installed so this is *not* an RDP connection problem.

5) I have spoken with Sage technical support on a number of occasions related to this and each time they are uninterested in providing support.

The problem is if Thunderbird doesn't work my client will have to spend money on Outlook 2013, however, there's NO guarantee that even that will work. 


Any guidance related to this will be much appreciated!

  • 0

    Hi Jon C,

    I personally test Thunderbird on windows 7 and windows 8.1 locally.  Both works fine.  

    The reason why I did a personal test is because one of the Sage City citizens says he/she installed Mozilla Thunderbird and it worked with no issues for him/her.

    http://sagecity.na.sage.com/support_communities/sage_50_accounting_ca/f/160/t/69316.aspx?pi4755=2

    FYI, 2012 R2 is not listed under system requirement, so we are unable to guarantee all of the functions of Sage 50 and other 3rd party software integration will work under this environment. 

    Personally, I also do not have access and lack of the necessary knowledge to do a test on the 2012 R2 environment on my own computers. 

    The suggestion I can provide to you is to install a free virtual pdf writer and print to a pdf document.  Then, users can attach the pdf file to the email message and do the email.

    Hope this helps.

  • 0 in reply to Keith L

    Hi Keith,

    Thanks for the prompt reply, it's much appreciated.

    I honestly think I speak for many people when I say that it's in Sage's best interest to certify Server 2012.  It's a product that has been out for 2 (two) years now and many companies are opting to go with the latest version of Windows Server instead of Server 2008 R2. The logic is sound, why should I recommend to a client, deploy and support a product whose official mainstream support from Microsoft will be ending on 1/13/2015 when Server 2012 has further reaching mainstream support that ends only on 1/9/2018?

    I did install PDFCreator (free) and I have tried the 'Print & Process' option instead of 'Email & Process' and while it works as a user with local administrative privileges there's still issues with regular 'non-administrator' users.  I'm going to perform further testing tonight.

    I really believe Sage should put more effort into this.

  • 0 in reply to Jon C

    After performing further testing it appears that I can send emails using the 'Print & Process' option.  Not ideal but it's a workaround.  While I don't find the process particularly cumbersome I suspect that the accounting people that will be sending out +-400 emails every time payroll occurs probably will.  Workarounds are not long term fixes.  Please escalate this to your product specialists that have the power to certify Sage 50 in Server 2012 environments so that people such as myself can get the support that we need through official channels.

  • 0 in reply to Jon C

    Hi Jon C,

    Thanks for your opinion and it is passed through the correct channel.  

    FYI, we will support server 2008 until the extended support end date.  

    http://support.microsoft.com/lifecycle/search/default.aspx?sort=PN&alpha=Windows+server&Filter=FilterNO