After Migration, Everything is Broken

[SavageHands]

I'm running FMStudio 1.8.0 on Dreamweaver CS3 in Mac OS X 10.5.4. I recently used Apple's Migration Manager to transfer my user from one computer to another. When I loaded up  Dreamweaver on my new computer, I found that all of my Filemaker connections in all of my sites were broken. Whenever I try and select a database in the Filemaker Connection window, I get the standard complaint about the API not being installed, and after I cancel that, I get an error that reads "HTTP Error Code 403 Forbidden". I get the same error even if I create a new connection in a brand new site. I've tried it with databases hosted on entirely different servers, so it's not a problem with one server in particular. The error seems to occur regardless of what is entered into the Filemaker Server, Username and Password fields. Unfortunately, my old computer was wiped before I noticed this problem, so there's no way I can compare any settings.

At this point, I've reinstalled everything I can think of, the API, FMStudio, and Dreamweaver, and the problem still persists. Can anyone tell me what's going on?

[bandmandq]

yes, I think i know. 

When you moved your database files over to your new mac, the file permissions get reset to read only for some groups.  That may be why.

Go into your Hard Disk Library folder ->FileMaker Server -> Data -> Databases ->  Then click on a database and from the file menu select Get Info.

Then do as the picture below shows by changing Group  and File access.  I bet that the group will not be fmsadmin and that the Access will say Read Only.  Just change those like the picture below.

That is one possibility.

Hope this helps!  Let us know how it turns out.

Jon Montgomery
bandmandq

[SavageHands]

Sorry, I forgot to mention that the Filemaker files themselves are not on the computer in question, they're hosted elsewhere. The only thing that's on this computer is the Dreamweaver files. Also, my sites work fine when they're live on the web. The problem only manifests itself in Dreamweaver.

[bandmandq]

Well, my first thought then would be that your local and/or testing site information in Dreamweaver is incorrect.

Search the forum for this, i am sure it has been covered but not sure where they are right now. 
You can use the search option in dreamweaver under the FMStudio menu.

bandmadnq

[bandmandq]

have  you tried the serverTest.php tool to help you trace it down ?

http://fmwebschool.com/frm/index.php?topic=840.0

[SavageHands]

FINALLY I figured it out. I managed to trace it back to my Web Sharing settings on my computer. Apparently there is a known issue when upgrading to 10.5 that causes you to lose an Apache configuration file. Here's how to fix it, in case anyone else has this problem. Thanks for your help, bandmandq.

http://docs.info.apple.com/article.html?artnum=306884

[theKiwi]

It seems from reading this that you have the sites in your

Users/UserName/Sites

folder, rather than having them in

Library/WebServer/Documents/

folder. I've had a number of sites in the Library/WebServer/Documents folder on my Macs since not too long after Mac OS X came out with the Apache server etc built into it, and never had any problems like this during an upgrade.

The obvious advantage to this is that the sites are accessible at an address like http://localhost/ rather than at http://localhost/~userName/

Just wondering...

Roger