Go easy on meh.....

Good Morning Everyone,

So, this is going to be (most likely) a pretty stupid question, However it is something that has been hounding me and holding up a server (2008R2 to 2012R2) upgrade. It has now come to a point that I need to make sure that it is completed. 

Now you may ask "What HAS to be completed Brett(and or stupid question "tall" guy). The answer is pretty long (SO grab your blankie and here we go). 

Many years ago (before I OR my prior IT manager) worked for my company they used Sage/Timberline Office 300 (I believe it was version 9.5) on one of our servers. This program has not been used by our company for over 5 years (and it might be longer) however there is still a requirement that we have access to the data that is in this program even though it has not been opened since I started working here. 

This leads to my questions, having never actually used said program, and having seen it only once actually started I'm concerned about what files/folders I need to copy and move to a new (Virtual server) so that we have data integrity. While I know that said program has to be reinstalled, my issue is I do not know that files need to be copied and moved prior to install. I also have questions about re pointing the PC (or PC's) that will require access to Sage 300. Meaning will we need to reinstall and re point to the new install version of 300 OR is it possible to just modify the path. 

As I said this may be a somewhat odd question, however as a "new" IT type person, I want to make sure that this is done correctly, and I'll be honest, the only docs that I can find about this version of Sage really does not help me in migration. 

Any help would be appreciated, I realize that this version of 300 is pretty dang old and no longer supported, that is one of the reasons why I found this forum and hope that perhaps someone can help me.

Thank you in advance...

Brett B 

  • 0

    HI Brett,
    We have some pretty good documentation on how to migrate Sage 300 CRE to a new server. The knowledgebase article number is 18500. This article is available on Sage City. If your company has an active support plan with Sage you can also call us to get help finding the documentation that outlines the process to migrate to a new server.
    I will do my best to determine how you can find the KB article here on Sage City and update my reply once I have determined where you go to find that.

    Okay I found it. Click "Support"  from the Black banner at the top of the page. From there select  you can click the FIND button under the Product Downloads and Knowledge Base Column associated with Sage 300 Construction and Real Estate.  Type 18500 in the "Search the Knowledgebase" box.

  • 0
    Denise,

    So, thank you for the help, the info that is there is pretty much everything that I've been looking for. However (You knew that was coming)....

    My boss (and HIS boss) have pretty much decided that instead of installing the 300 suite either in "real" or "virtual" form that we are going to simply install Sage/Timberline office on it's own notebook (running Win7) THAT however has me asking more questions.

    Since this is just one install on one notebook (for legacy) will I need to install the client or the server version.

    Either way, per the link that you gave, all of the data files will (I'm going to guess) in this case reside ON the legacy notebook, I'm not quite sure what the file structure will be in this case.

    The only other thing I can think of is to install BOTH the server and client on the same notebook, but that simply seems to be a TON of work....

    Yep, I'm totally lost I'm just sayin........:(
  • 0 in reply to Brett B

    If the plan is to install the software to your boss' standalone notebook computer and noone else on the network will be using the software then you would do a SERVER install on that stand alone notebook computer. The data files will be on that same notebook. You would only be able to run the software and look at the data on that one notebook. You will want to check minimum requirements to run the version that you are installing to make sure that the notebook meets the minimum recommended system requirements.
    You don't need to install both the Accounting Server and Accounting Client on the notebook, only the Accounting Server.

    Oh and if the notebook already has the client version installed on it, you will want to uninstall that before installing the Server version.

  • 0 in reply to Denise Paulus
    Denise,

    Thank you so much for helping me figure this out, I've got to admit that while I am "old school" (with DOS 6.X) :) I'm totally at a loss here. SO I've got (yet more) questions that I'm totally at a loss for. While trying to install the server version of Sage/Timberline office 9.x I start the install and then get this (prepare yourself THIS is a LONG paragraph of text)

    Error 1721 there is a problem with this windows installer package a program required for this install to complet could not be run contact your support personnel or package vendor Action: Dofilemerging, location C:\users\

    Now I'm not sure what the full text is, and I'm trying to find out what the required program that is required IS, but I'm not having a ton of luck here.....

    So once again...Herlp! :(
  • 0 in reply to Brett B
    You are installing a very very old version. Exactly which 9.x version are you trying to install? Also what is the operating system on the computer you are trying to install to?

    You may want to contact Microsoft for this type of error.
  • 0 in reply to Denise Paulus
    Denise....

    Currently the version of Sage that I am trying to install would be 9.7, this is being installed on a Dell Notebook currently running Windows 7 professional. Looking at the install guide for 9.7 I believe the system requirements are good. I may need to do some more research...... :(
  • 0 in reply to Brett B
    So looking a bit deeper (and a bit of google) I can see that this is the file that could not be run:

    tscfgins.exe

    Which I have no idea where or what it might be....