08-21-2017 07:09 AM
We have recently moved our users to a "new" server on which Act was installed. As the server utilised the same name/ip address as its predecessor we installed Act fresh and restored the databases from backup.
The server is running on Windows 2008 R2 64bit. Act was able to pick up the existing databases automatically and we can log in and view, edit records within the database. However we are unable to share the database with others users.
Each time we attempt to share the database we are met with the following error message:
There was a problem sharing/unsharing your ACT! database. The path is not of a legal form.
I have gone over the instructions in this KB:
However it has no affect (and additionally the link in step 2 is not working), the path of the database is on the local server, on a local drive.
I have also been able to succesfully move the database to D:\Act without issue. However the problem appears to be its refusal to share.
Does anyone know what the error means?
08-22-2017 06:29 AM
I would like to know how you moved the database to the new server from the options available. I believe the new server having the same name could potentially cause some issue.
I have provided the article below that has the steps to detach the database and have provided feedback on the article to be updated.
Once the database is detached then delete the .pad file and open the database via the .ADF file by double clicking on it.
It may also be worth sharing where the database is now stored IE: D:\Act
08-22-2017 06:56 AM
Thank you for responding. As mentioned we restored the database from a file backup to the new server, installed Act and on first run Act found the database.
I then used the Move method:
File -> Move Database -> Prepare and Complete a Move on this computer
To move it from its previous directory to D:\Act
I have followed both KB articles in your reply however I get the exact same error when I go to share the database.
Funnily enough I did some further testing by copying the database to a new copy.
File -> Save Copy As -> Create a copy of the database -> Location = D:\Act, Database Name = Test
This created a new database which I could open and subsequently share without any problems.
I then closed Act and then stopped the Act Host service so I could remove the troublesome database (I copied to a random location out the way). I then went through the exact same process to copy the Test database and generate a new copy based on the original name. Once the copy was generated I then tried to share and encountered exactly the same error.
This suggests it does not like the name of the database (which makes no sense, its literally lower and upper case letters) or possibly there is a schema reference to the original name within SQL that is causing the error.
08-22-2017 08:00 AM
Out of curiosity what are you naming the database? I have seen issues where certain names are restricted IE: Database
08-22-2017 12:42 PM
... QUESTION... If you try to share the demo database... works..??
Demo Database is on the next path, then it might be a good idea to place the Main database on the same path...
If you have the Firewall active, remember the exclusions CLICK
Best regards... ( www.praxisol.com )
08-23-2017 02:01 AM
08-23-2017 06:54 AM
I created a database on my own system with the same name and was able to share without issue, so the name is not restricted.
There must be something in SQL which is deciding this database name is problematic.
I would like to check if the datastore location can be changed for this database.
You can do this from Actdiag > Database Details List > Highlight your database > Actions > Datastore Location > Change to Machine Name (Ensure the machine name is correct to the PC you are on)
Then test again.
Alternatively it could be worth using a slight variation of the name.
08-25-2017 06:01 AM
I think it is that the share name is already on the network from the previous database. You cannot have 2 share names the same. Try unsharring the database on the old server or change the name of you new database.
08-25-2017 07:37 AM
08-25-2017 07:38 AM
That is certainly a good thought. Whilst I am getting around the issue by using a copy under a different name I may well test your theory over the weekend just to see if that does explain the problem.