Sage 100

Prior to migrating MAS 90 ver 4.4 from an old 2003 server to a new 2012r2 server, the vSalesOrderEntry table contained udf's. These view files were used to create crystal reports. The Crystal reports will not run because the udf's are no longer in the file vSalesOrderEntry. We have rebuilt the customizer files, still not there. Any idea how they got there in the 1st place? As the consultant that did that is no longer with us Or other suggestions? See attached images Thanks

Looks like the system migration didn't properly happen or it had some type of error. I recommend migrating over the system and reconverting.data. Let me know if you need help with it.

Did you upgrade or just moved the files from old server to new?

We migrated the files from the old server to the new. No error messages at the time of conversion.

Confused. Moving the files from one server to another doesn't require data conversion.

Are you running Standard or Advanced. You do need to reinstall it is advanced but there are some tricks so you can copy the software once you install. .Or once you install you can migrate,

I don't use them much, but could they be from Business Insights Reports? I don't think BI Reports migrate well.

We did this through: Library master \ utilities \ Parallel Migration. This is MAS90, not 200/advanced 4.4

@RobertaChase Thanks, we ran the BI report listing from the old server. Empty. Tried the BI exporter it is also empty.

Do I understand correctly? This was a hardware/OS upgrade and Mas90 was at 4.40 and stayed at 4.40?

@MarkChinsky I recommend just copying the entire MAS90 Folder from old server to new one as Mark mentioned. (Rename the existing MAS90 folder) My guess is that the migration didn't properly migrate the Views. Since you have Standard you should be fine .

I just did the same for one of our customers. He didn't want to upgrade; just get a new server. Here's almost an foolproof way to move to a new server, assuming old and new Sage is identical.: 1. Install Sage, SP, Server Config, and anything else you need on the new server, using the same paths, same port number as current Sage. Run WKsetup, make sure it works. Basically, it's a proper install that will write to the registry. 2. On the new server, change the name of the MAS90 directory that you just installed (Let's call it MAS90NewServer). 3. Grab the MAS90 directory from the old server and put it where it now belongs on the new server. 4. In this MAS90 folder, rename the Unistall and UninstallInformation folders (you may have only one). 5. Copy the Uninstall and Uninstall Information folders from the MAS90NewServer and paste it into the MAS90 folder. 6. Remember to change the PaperlessOffice path names.

If they are using paperless office they to will need to update the location of the new one and change the path pointer on the existing PDF Logs. There is a couple wayx to accomplish that too. (different thread keyword ""moving paperless

Thanks so far. We will try this now.

Unfortunately they've been entering data all day. Can we just copy the system files? Thanks

I'd rename the mas90 version (let's call it mas90062916) that they are working on today, install and move their Sage (from old server) as I noted above. This will get them an exact copy of everything they had as of last night. The trick is that you need to have the same path and port. Now your only issue is to get them updated data. I'd rename the MAS90\MAS_XXX, copy the MAS90062916\MAS_XXX and place it into MAS90 folder. This will only update data, so if they have change system files (taxes, users, roles, etc.) they will not be moved, so beware! You will also need to move the paperless office Logs from MAS90062916 to MAS90. I do it this way because I am less technical than some of our super-90 Minds consultants and I know it has worked for me. I do know that I have seen others recommend moving specific files which will probably take less time than my suggestion; perhaps you could do a search for that info. PS Make sure you have a backup. :)

I always rebuild the UDF's when I do something like this. Not sure if this is still beneficial.....

When done let us know if this brings back the vSalesOrderEntry file.

It looks like we are just going to recreate the reports. They aren't too complex, but thanks a ton for all your help.