Either don't use server '03 or XP, or don't upgrade to sage 2016.

Thanks for your reply
Unfortunately, the customer has been upgraded to sage 300 2016.
Server System: Windows Server 2012 R2 English - 64Bit
Database : SQL 2008 R2
Worksation: Windows 2003 terminal Server 32/64bit
Sage 300 Version: 2016 SP1
I can only suggest the customer update the terminal server to 2012/2008R2 version as soon as possible.
But now very embarrassed. I have to open the web deployment mode for workstation , but the report can not export excel.

Thanks for your reply
Unfortunately, the customer has been upgraded to sage 300 2016.
Server System: Windows Server 2012 R2 English - 64Bit
Database : SQL 2008 R2
Worksation: Windows 2003 terminal Server 32/64bit
Sage 300 Version: 2016 SP1
I can only suggest the customer update the terminal server to 2012/2008R2 version as soon as possible.
But now very embarrassed. I have to open the web deployment mode for workstation , but the report can not export excel.

Well sorry, pal, it's your customer, and it's your fault that you didn't tell them this. Besides, nobody should deploy anything on 2003 servers anymore, it's totally not supported by Microsoft, so is technically dangerous to run.

You should be embarrassed for not reviewing the hardware requirements.

Thank you for your reply, customers have purchase new Windows 2012 terminal license, New terminal server can be released next week.