Sage 50 Free Download Crack Version
Tatum Cartwright
Is there no simple way to confirm which tax update version you are on? I thought it would be as easy as opening PR, going to Help > About and seeing it right there. According to an old Sage knowledgebase article I found. Their suggestion is to check the effective date on the taxes in PR. That's fine when you've only done a single update for the year, but all these sub-updates share an effective date so that doesn't tell me if I'm current. Instead, I have to compare the tax changes from the release notes with formulas in PR to see if they match up.
Look at the effective date prior to doing the update for a tax that is updating in the tax release you are downloading. This can be found in PR > Taxes > Tax Rates. Then pick the tax such as COSWH and note the effective date. Run the update and then go back to that screen. It should have updated the Effective Date if applied correctly.
I do appreciate you trying to help, but I feel that you didn't read my original post or might have missed my point. Your answer seems more geared toward "how can I confirm that a tax update applied correctly" rather than "how can I easily tell which tax version I'm on".
In my original post, I mentioned the method you are suggesting. Effective date isn't a good option when all the minor tax updates (like the 2-3 released so far this year) share the same effective dates. At best, this tells me that I'm on 2023.X. The X is important to know.
Create a Sage City or Sage Knowledgebase account
Search for the latest tax update release notes
Find something in that document that has changed with the latest update
Go into PR > Setup > Taxes > Tax Rates
Compare formulas with the thing you found in the document (since effective dates are the same for the sub-updates)
Feel reasonably confident that everything is as it should be
If you use the two step process, you'll end up with 2 different print files. If you download & choose to update at that same time, you'll end up with 1 print file. If you can locate these/this print file(s), (in other words, save it to file in a particular place so you'll have it as a reference) you can confirm you've downloaded the file & that you updated the taxes. If you open these print files, they will provide you with paths to backup copies of files that you can also use to confirm that you've got the latest using file explorer. I think there's been 3 tax updates so far this year. The last one included:
Thank you Rhonda. I do see the downloaded tax updates in Timberline Office\9.5\Accounting\MISC. I think that is probably the closest I'll get to an "easy" way to check other than by comparing tax rate formulas. Although there is always a chance that the tax update was downloaded and not applied, which means they may not up be to date.
I think I may be lost on the first suggestion. I do have the print file and I do see the backup_tax location. It has several backups in there, but I don't see how any of the file names or contents correspond to which tax version we are on. In our case, we accidentally missed the first two updates, which is why I'm trying to determine an easy way to confirm. Was the idea that I could look at the backup date and compare it to when the tax versions were released? If so, it unfortunately won't help in all cases.
If you change your view of the backup_tax location to show date modified and most recent first, it may help. The tax updates are cumlative so if you got PTUS2303.zip, you've got the others, too. The printout, if done as one step for both download & update will show two sections: One about the download, and one about the update. If done in two steps, you'll find two different printouts. When in doubt, you can always download taxes and update again. I try to name the print files to try to reflect which update I'm applying. Maybe not as reliable, but ... one more thing I compare beforehand is in the properties of the Tax.PRX file's, I compare the date created before and after the update is applied. The Tax.PRX file's location is controlled by your settings under File Locations.
My client has been pushing for the application to be updated since they are paying for the support and all from Sage. I called Sage and the procedure given was to upgrade to 15.1 and then to 17.1. I have been backing up the folder where the data files were installed but just that - thought that was enough.
I proceeded with the upgrade today by upgrading the application on the server (DC) to 15.1. Ran the data upgrade which went smoothly. Next, i did a File doctor scan and fixed one file, nothing major. Tested application and all seemed fine. I proceeded to upgrade to 17.1. rev6 went through the data file upgrade again and this time some of them failed. Complained of "unprintable control characters found". It appears some of the fields had characters which are no longer permitted (my guess), so I went along with the File Doctor fix which did work. After that I ran the data file upgrade again and this time it completed for the files that had failed previously. Tested the application, seemed fine.
Proceeded to install client on RDS server. Installation completed successfully but application is terribly slow. The logon window takes up to a minute just for the "log on" button to be activated ie not greyed out!! I opened project management and tried to browse around. It was so slow that on many occassions it just hung up and eventually crashed. it's not usable in this state and even though I will like to fix this, I can't wait till Monday to get support. (didn't know they are off weekends!). I want to move back to the old 13.1 but realize that I needed to have backed up the programdata folder as well. I'm royally scr***d.
Forgot to say, Data file server is 2008 R2. RDS server is 2012 Standard. Tried installing client on a windows 7 PC and got same slow performance. I don't think it's a network issue because it was working well before and i can still transfer files to and from server with good speed.
KB_17258.pdfLogon to the Sage Customer Support web site and go to the Sage Knowlegebase and search for Article 17258 that will inform you of the specific folders and paths you need to add as exclusions to your active anti-virus scanning. I uploaded and attached to this reply a copy in PDF form. There is a new version of Pervasive with the upgrades you performed and failure to exclude these folders and paths will slow your performance. Also review the portions of the User Guide for compliance with the system specifications of your hardware and operating systems. The User Guide is available from within the software under the Documents menu, or can be downloaded from the Sage Support Site where you downloaded the software.
Thanks so much for taking the time to reply. Unfortunately, I'm not running any antivirus software so I guess that is ruled out. The server however is a domain controller which they say is unsupported. When installing though it mentioned that because it is a DC, the sql replicator will not be available. We have no plans for that so I thought that was okay. Other than that, I don't see anything else in the user guide that might be the issue. I do have ample RAM and CPU resources. Any further thoughts?
If the slow response time is only on your RDS server, search RDS in the online knowledge base Only 4 articles appear. You might look at 30050 and 67046. Have you restarted the RDS server? Have you tried running the workstation install again on the RDS server? Did you use the UNC path to the WININST folder on the DC server when performing the workstation install to the RDS server? Your last resort is to call support first thing Monday morning.
If this does not resolved the issue you could try running the 13.1 install and upgrading files but only after a full server backup. As far as I know going backwards is unsupported and the upgrade process is not designed to go in that direction. I haven't ever tried this and I wouldn't doubt that there would be issues.
I found a backup of the ProgramData folder from 2 days ago and decided to try to roll back. I completely removed the 17.1 version from the system along with the software I think it installed (using "installed on" in control panel programs and features). Next, I replaced all the files in ProgramData\Sage with the files from the backup (made sure the Timberline Office share and permissions stayed but replaced the files within). Then i completely replaced the contents of the Shared Data folder with the 13.1 data backup i had before this whole mess ie keeping the shares, share permissions, and folder security permissions. After that I installed 13.1.
On trying to open Ts-main, I get the error "The Sage Pervasive License Service is not running". Clicking OK throws another error "Could not create path utilities component". I see the service is running though, tried restarting but no joy.
If i run the desktop, i get prompted for password and can login. Companies' UNC paths show up but selecting any gives "Data Folder open validation error: -2147024894". Closing gives same error "Could not create path utilities component".
I have verified that the permissions on the data folder and below still exist. I can navigate to the unc path of the data folder. I have run Saage system Verifier as admin, and it completes without any errors or warnings.
You cannot downgrade your data files to earlier versions. Installing an earlier version of the software without doing a complete uninstall of the Prerequisites such as Pervasive and the Sage programs likely left remnants of the 17.1 version. 17.1 uses a completely different Pervasive version, newer Crystal Reports runtime version, and other interface changes. You should have continued to troubleshoot your 17.1 installation. Call Support in the morning and choose the option for Systems or Installations at the prompts. You're going to need someone to connect to your server and RDS workstation to untangle this. I wouldn't attempt to offer help via forum postings or chat at this point.
b1e95dc632