Sage 100

I swear that @Diane Ruth posted something similar, no search in this group is finding it so I must remember wrong :(. Moved Sage 100 (4.3) to a new server and there are 38,000+ broken memo attachment links. Using the LM Link Maintenance Utility is a cruel slow death as the reload of the broken links (even with only show broken links selected) is so very slow. Isn't there something else I can use to relink all these broken links?

That is the only one I am aware of.......

@MoiraGoggin you would think there would be a faster easier solution but re link is the only way I'm aware of also.

The concept is good. Better than moving them. The selection process just sucks to no end. Plus if you select too many, it still blows up on you.

Thanks for the responses, I must have been dreaming there was a faster way...guess I'm in for a long slog to relink..sigh.

Can you put the old server with the pdf's back on the network? If you can still point to \\oldserver\PLO\<folders>, then you can execute a MOVE to the new location. @ChuckPeddy does this all the time.

@MoiraGoggin , is this Sage 100 Standard or Advanced (""MAS 90"" or ""MAS 200"")?

I have found that physically moving the files via Win Explorer THEN relinking is way faster than using the move command within paperless. The process is very similar with either. Highlight, select then cross your fingers that you aren't moving too many at once or else the system blows on you.

@JeffSchwenk does the 8K limit apply to Link Maintenance also?

I did 18K in link maintenance yesterday. it did take a few minutes but worked great. I agree with @JeffSchwenk ... much easy to move outside and relink with utility.

I actually don't know the selection limit is but it does blow up on me. I always do the relink at the server. Perhaps the issue is a memory issue? I would never try 18K at one time like @JimWoodhead . The other pain is if you select a broken link, it will throw a rod at times. I haven't discovered any rhyme or reason with it.

@JeffSchwenk why not? At the end of the routine it will publish how many moved and if there were any failures. Then you can check the dislpay only broken links and review the issues

One other thing is that I will copy them to the new location instead of moving them. So it will be in both places. This will limit the broken links initially. once all linking is done they can archive the old system.

Can you use Link Maintenance when moving servers? I seem to recall trying it once, but couldn't give it a new path. My memory may be faulty (wouldn't be the first time).

It's worked for me in the past.

Yes, you can use Link Maintenance when moving servers. I do it all the time. I've run into issues with the path here and there as well, but only when I've tried to run it on the server. I've never had a problem when running from a workstation. I attribute my path problems to user error.

@JimWoodhead - Not sure. Just know that I semi dread doing this because the log refresh is very slow and for the other aforementioned glitches. Will make note them on my next more. Hopefully, things have improved.

Wow, thank you all. The old server was dieing (and has passed) but I copied their 'attachments' directory from the old server to new before it died. This is advanced version. The directory has about 20 sub-directories in it, so I can't just select all and then relink to one directory. That makes it even slower....also some users used a mapped drive to this directory and others unc path.

You'll find even if you browse to it from a mapped drive, it's going to switch it to a UNC path unless you're running it from the server.

Thanks @MaryJoKrueger - it works most of the time, I think the 'failures' are from someone moving/deleting it so it's been a broken link for a long time before the server move.