I had some issues with Peachtree.... (never ming Peachtree in inself is an HUGE ISSUE... A pathetic peace of software anywhere) my company uses it for Accounts.
so I thought of installing it on a test server and I did a remote into it, when i ran the Autorun.exe it gave me the error...
Failed to switch Terminal Server to INSTALL mode ... BLA BLA bla....!!!!
I closed the error and ran setup.exe.... again the same error !!!!
tried many things but nothing did resolve my issue...
was it someting to be set on server or some config issue.... didnt get anything and no matter what iI did i couldnt get it to work ...
Just as I was browsing the Install folders I found another setup.exe when I execuited it Peachtree... (the junk) installed successfully..
Path to the file is
Disk1\peachw\install\_setup.exe
mine was peachtree2010 just search for all .exe files and check yours.
I wonder if its Coders issues or the Company's issues to mislead others or blame other if their crap piece of code dosent work...
the blame was on remote desktop login I dont know WHY? and why it go installed from same CD but another location.
One more Microsoft in the making...
Thanks,
so I thought of installing it on a test server and I did a remote into it, when i ran the Autorun.exe it gave me the error...
Failed to switch Terminal Server to INSTALL mode ... BLA BLA bla....!!!!
I closed the error and ran setup.exe.... again the same error !!!!
tried many things but nothing did resolve my issue...
was it someting to be set on server or some config issue.... didnt get anything and no matter what iI did i couldnt get it to work ...
Just as I was browsing the Install folders I found another setup.exe when I execuited it Peachtree... (the junk) installed successfully..
Path to the file is
Disk1\peachw\install\_setup.exe
mine was peachtree2010 just search for all .exe files and check yours.
I wonder if its Coders issues or the Company's issues to mislead others or blame other if their crap piece of code dosent work...
the blame was on remote desktop login I dont know WHY? and why it go installed from same CD but another location.
One more Microsoft in the making...
Thanks,
I know this is a bit old but.....
ReplyDeleteWhen installing program on a terminal server you need to change the server to install mode by running “change user /install” from a command prompt or use “Add/Remove Programs.” After the installation you must run “change user /execute” to bring it out of install mode.
Thanks for finding this out! Nothing like this on their website.. This worked on the 2012 version as well.
ReplyDeleteThanks! You saved my day.
ReplyDeleteTHANKS!!!!!!
ReplyDeleteWorked with Sage50 2013 as well
ReplyDeletePeachtree/Sage: Consistently the crappiest software/install/upgrade process I've encountered in 10 years of consulting.
ReplyDeleteIt never works, never goes smoothly, never acts like it's even been tested.
Thanks, It worked for Peachtree Quantum 2011
ReplyDeleteThanks, this works. The change user /install option will not work in virtual environments so this is the only option. I agree with the others, Peachtree is horrible software.
ReplyDeleteThanks! This saved me a lot of time.
ReplyDeleteThank you save my day...
ReplyDeleteAlso if running on 2008r2 Install "remote desktop Host" feature on the server before attempting install. It will bug you for licenseing and i dont know if you can uninstall the feature after its installed successfully but its a start. we are using the software for dev, no warm body from their support team in 3 weeks. had to figure this one out alone...
ReplyDeleteJust wanted to add that the file for Sage 50 2014 is located in c:\sage\peachw\install\_setup.exe. The server we install on has no monitor so is only remotely controlled. When trying to switch to /install mode, this error comes along "install mode does not apply to a terminal server configured for remote administration." by running the above setup file all works out great.
ReplyDeleteThanks for the update...
DeleteThanks it worked
ReplyDeleteThanks, saved me a headache! Works on 2014 as well after right clicking and running as administrator (even while logged in as an admin)
ReplyDeleteIf installing remotely, be sure to use console and not RDP
ReplyDeleteRDPing to a server for remote administration is not Terminal Services. The folks at Sage PeachTree don't understand this. You can't switch to install mode in this instance., it doesn't read the console switch.
ReplyDeleteTo anyone reading this, if you are considering purchasing Sage PeachTree and are looking for reviews, do not buy Sage PeachTree. Find other software. If you are considering upgrading Sage PeachTree, stop where you are and find another vendor.
This worked for Sage 50 (Peachtree) 2014 too....
ReplyDeleteAgree Peachtree is crap..... Stay away if you can.......
Thanks a ton. Saved me a lot of stress today. And to parrot the others, yes it is consistently in the top 5 worst software we support. Horrible stuff.
ReplyDeleteThank you much!
ReplyDeleteMake sure you log into the server locally and not through RDP.
ReplyDeleteWorks for 2014!
ReplyDeleteIt provide a simple but powerful pattern which will help you to structure your application.
ReplyDeleteWindows Thin Client & Citrix Thin Client
You can try to logon to the "console" (it's like logging in to the physical machine) through rdp, by running 'mstsc /console' or 'mstsc /admin'. If you still have trouble, use Logmein, since Logmein will use the console.
ReplyDeleteAlso worked for 2015. Great!
ReplyDeleteThank you Sirji.. Bachaliya isane.. worked for 2015 too
ReplyDeleteRaj
Ran into this today.
ReplyDeleteNothing has changed now that the product is Sage 50 instead of Peachtree. The setup.exe is even still in the peachw directory
@Justin - I tried mstsc /admin as well and no dice. This worked will for me when I did a fresh install but I ran into the same issue on an update... Only apparent option with the update was to logon to the server from the physical console.
ReplyDelete