This weekend we moved to a new file server - Server 2.

The data path we had set in Max Doc 1.2 is

s:\data\max\docs

This has not changed - S still maps to this path - albeit on a different physicaly server.

Now when we try to open documents already in Max, I get an error - \\server1\data\max\docs\d\j not found..

I can see why this has happened, but I thought that was the reason for installing Maxdoc using a mapped drive rather than UNC name..

Help!

Having done more testing and spoken to CABC support, they confirm there is nothing that can be done about this - short of building / running a completely separate server with the old name..

This is disgraceful.

Can you think of any other application whatsoever that doesnt let you move Data to a differnet server / path / drive? I cant in 15 years as a pro.

I was told to install MaxDoc with a mapped drive letter - which I did. However this obviously makes NO DIFFERENCE when you want to move data.

There needs to be a CLEAR WARNING on the Max Doc box, saying;

If you buy this product and you want to move data to a new server, tough you cant.

Not happy.

Hello Jason,

As explained in our recent telephone conversation, it's a regretable issue concerning the filestore that unfortunately cannot be resolved by anybody other than Multiactive. It is a feature of Maximizer that when you link a file, even if from a file path containing a mapped drive, that it is resolved to a UNC file path before the link is saved.

I suspect that this was a design decision that Multiactive took early on so that linked documents could be accessed from anywhere on a network.

While I agree that perhaps the documentation could have been more concise (it has now been amended) it does very clearly state the following:

"You must give very careful consideration to the location of the Max Doc filestore on your network server. You don't want to have to move the filestore at a later date, as this can break all the links between the documents and your Maximizer databases".

The simplest advice that we can offer is that you give your new server the same name as your previous one. Is there a particular reason why this cannot be done?

This cannot be done for several reasons. As you may or may not know migrating to a new W2K server is quite a long winded affair - even with active directory enabled.

The easiest / best way is to build a new server (which obviously needs a new name) alongside the existing server, migrate whatever, connect it to Active Directory and connect it as in effect a backup domain controller.

Then you have to promote the new server to be the master..

Renaming the new server to what the old name was is not an option.

Is there no way whatsoever to edit / search / replace the Max database to change this UNC name?

Jason

So is that it then? Im stuffed basically..?