Filemaker Server 5.5 not serving my ebase database
Filemaker Server 5.5 (v4) shows that it is running. The serving tray is spinning, and it appears in my activity monitor as 'active'. When I click the database alias on another computer, it opens FMP, asks for my password, tries to open the file and then nothing happens - FMP program stays open but not database appears. Database is running fine on the host computer . Server appears to be running on host computer.
I tried reinstalling the FM Server. I also tried opening the database by using the client prompt in the installation disk - that generated the same problem - it could not access the database file, so nothing opened. Any suggestions?
a 6ya expert can help you resolve that issue over the phone in a minute or two.
best thing about this new service is that you are never placed on hold and get to talk to real repairmen in the US.
the service is completely free and covers almost anything you can think of (from cars to computers, handyman, and even drones).
click here to download the app (for users in the US for now) and get all the help you need. goodluck!
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
An MDF file isn't a backup file isn't the main data file (or master data file depending on who you ask) hence the file extension MDF. You can attach the MDF to the database by right clicking on the databases folder in Enterprise Manager (SQL 2000) or Management Studio (SQL 2005) then selecting all tasks and then Attach Database.
When you do this you will get an error about the log file missing. This shouldn't matter as SQL Server will simply create a new log file for you.
This will only work if the SQL Server was stopped when you copied the MDF file from the old SQL Server. If you copied the file while the SQL Server was running this file probably will not attach either and you will need to get a valid backup of the database.
Download help tool for sql database - SQL Server Restore Toolbox. http://www.sqlserver.restoretools.com/
You can read up more on SQL Server here. http://www.filerepairforum.com/forum/microsoft/microsoft-aa/sql-server/498-creating-a-new-database-using-an-mdf-file?_=1416149856104/
1.open your MS SQL Server Management Studio, 2. connect to your data server and locate the database that has an issue on disk space 3. Right click that DB and select properties, 4. a new window will open, on the upper left part, select Files, now you may notice the settings for initial size of your DB. 5. on the autogrowth column, click the button corresponds to your database. 6. a new window will appear and displays options for your database autogrowth settings, 7. set your desired configuration, apply and your done,.
or you may check this blog: http://blog.sqlauthority.com/2007/08/08/sql-server-2005-ssms-enable-autogrowth-database-property/
Sheldon, The data might really be gone. There are several reasons you might lose data with Filemaker 7 including the file being closed unexpectedly due to power failure, so the application doesn't close the file properly, or the Filemaker application unexpectedly quitting. However, the data might still be recoverable in this scenario. Under the File menu there is a recover command you can try that will create a new "Recovered" file from the current one. Additionally, I strongly recommend you start a daily incremental back up for your FileMaker database files. While corruption issue are rare, accidentally deleting a record, or information in a field, or purposeful sabotage by an unhappy employee is permanent without a backup. Additionally, a back up would provide a solution for recovering the data in the event client data disappears in the future.
I hope I've done a good job answering your question. I am a FileMaker 7 expert (and 8, 9, and 10 as well); if you have any additional questions I will do my best to answer them. If my answer was helpful for you I'd appreciate a 5 thumbs up rating, or a click on the yes this was helpful button. Thank you!
FileMaker 5.5 is a long time ago for me, but I think I will try to answer your question (although it is likely you have a solution or no longer need one.) While in layout mode, while working on the layout, go to printer setup and choose the printer and page size you will be printing to. This will cause FileMaker to have a dashed line where the printer pages are on the layout. Anything that extends over these lines will require additional pages to print. Simply bring everything back in before these lines to limit to 1 page (including the blank space at the bottom of the page. There is a tab you will need to drag above the page break line to prevent a second page from printing. Additionally, if you cannot work it out, while printing from FileMaker if you choose the page range of 1 to 1, only 1 page will print, however, doing this prevents you from printing additional records without writing a script to do it. However, if you are able to redesign the layout to only print 1 page then you will notice there is an option on the print dialog box that indicates something to the effect of "Print current record" and "Print records currently being browsed" (Don't remember the exact wording in FileMaker 5.5); Choosing the records currently being browsed option will print all records in your current found set.
I hope I've done a good job answering your question. I am a FileMaker expert for version after 7 and have used Filemaker since version 4; if you have any additional questions I will do my best to answer them. If my answer was helpful for you I'd appreciate a 5 thumbs up rating, or a click on the yes this was helpful button. Thank you!
It should install automatically when you insert the CD - double clikc cd-rom drive if it does not begin to load.
This might be a useful article - there was a bug - you may need to upgrade to SP2. http://www.microsoft.com/sql/prodinfo/previousversions/system-requirements.mspx
Note: If you are running a 64-bit version of a Microsoft Windows
Server™ operating system, you need to use SQL Server 2000 Enterprise
Edition (64-bit). Visit the SQL Server 2000 (64-bit) System Requirements page for additional information.
Perform following steps to recover sql server database:
Create a database with same size that you are trying to recover
Shutdown the SQL server
Swap old mdf file with new mdf file
Start the SQL server
Database may go in suspect
Set database in emergency mode
Run DBCC CHECKDB with repair_allow_data_loss to repair database
USE [master] GO ALTER DATABASE [RdmStoreInformation] SET EMERGENCY GO ALTER DATABASE [RdmStoreInformation] SET SINGLE_USER GO DBCC CHECKDB ([RdmStoreInformation], REPAIR_ALLOW_DATA_LOSS) GO ALTER DATABASE [RdmStoreInformation] SET MULTI_USER GO ALTER DATABASE [RdmStoreInformation] SET ONLINE
I suggest you use the Enterprise manager (gui tool to manage SQL).
Restoring a single table is not an option.
You can however restore a file or filegroup.
Make sure to backup before you start and NOT to restore database to its original name or original file location, to avoid acidents.
Normally you will have databases with only 2 files: the data at its Primary file group, and log file.
You may wish to create a new file group and move tables to the new group by recreating them there and exporting data from old table to new table. Then recreate indexes. This may prove to be complex as all tables and indexes have unique names and can't coexist with exact duplicate of them.
oh yea..... did I say backup?
well just in case backup backup backup backup backup backup backup backup backup backup backup backup backup backup backup backup backup backup backup backup backup backup backup
but dont overwrite that backup
a bit late for the answer, but maybe it can help others...
This usually means the file has not been closed properly following a hard shutdown of the server (power outage?). It could be that the file needs to be recovered, or simply checked by Filemaker.
In both cases, you need to open the file with the client version of Filemaker Pro 8, then close it again, and the Server should happily open it thereafter. Here, we keep a copy of Filemaker client on the server for these rare occasions.