A new model created using File - New has all the criteria and defaults set based on the information in the Ramis.ini file, which can be configured using Ram Manager - Tools - Ram Defaults utility. For more on this see: Ram SS Installation FAQ
Alternatively, you can take any model that you have set up the way you like, delete all the stuff in the model (layouts, grids, stories) and then use that like a template to start new models using File - Save-as. Some users prefer this approach to starting new files based on the defaults utility settings because you can
See also: Do You Like to Start With a Template?
A RAM Structural System model file (e.g. filename.rss) is literally a Zip file and within any .rss file you should find many component files of the same name with a wide range of extensions including (but not limited to) .b3d, .ram and .uid. These files are extracted from the model file and put into the working directory when opened in RAM Manager (in older versions of the program all of these files were simply saved together in the model directory). In some cases a zip repair utility can be used to open a .rss or .backup file that won't otherwise open.
For this reason the working directory should always be on the local drive and in a place in which the “user” has administrative rights. It’s also important for the user to have the rights to add, modify and delete files in the model directory. Furthermore, we recommend that users exempt the working directory from any virus scanner software. If the virus scanner stops the generation or modification of files in this folder it could cause the program to perform slowly or fail to save model changes.
Note: the working directory is set the first time the program is run, to confirm or edit the working directory location go to C:\ProgramData\Bentley\Engineering\RAM Structural System and double click the Ramis.ini file (c:\windows\ramis.ini prior to version 14). This should bring up the Ramis.ini file in Notepad (or other text editor). Look for the line that begins
working=path to working directory.
You can edit this path to the working directory here. Spaces are allowed as are references to mapped drives, but for the reasons mentioned above, a local drive should be used.
Also in the [Directories] section you will find the paths for other installation directories like the Tables folder where the program looks for all the tables and the default reports directory for saved reports.
For more information on the contents of the Ramis.ini file, refer to the RAM Defaults Guide [TN] and the RamSS Installation FAQ.
Regretfully Ram SS models are not backward compatible. Typically with each major release there are changes in the model data base format. Once models are converted to the new version they can no longer be used in prior versions.
When a model is converted a backup of the original file is automatically created in the same folder with the same name and appended with the original file version, e.g. MyFile_Orig_14_7.zip, in case there is any need to revert to the prior version.
Note, though version 14.06.01 is generally considered a minor release, file conversion from version 14.06.00 is required. See the 14.06.01 Release Notes for details.
As of version 17, the Ram Manager utilizes a 32 bit zip control to compress the working files into a single zipped .rss file. This control is limited to 4GB. Should you have a file that exceeds that limit it may not save completely, giving the "Could not unzip . . . . . " error message. At that point you should Save as Archive to save the input without results and then try to reduce the file size, e.g. by increasing the mesh size or changing criteria to not save some of the results, e.g. wall stresses.
If the listed user really is in the file, they need to exit the program normally to release the model so that you can open it (RAM SS models do not allow for concurrent use).
If that user is not currently in the file or unavailable, you should navigate to the directory where the model is saved and look for a file of the same name with the file extension “.usr”. This is a lock file that was created when the user last accessed the model. The .usr file is normally deleted when the model is closed, but if the program terminated irregularly, the file might persist. Simply delete the .usr file and the .rss file can then be opened.
If you select the “Most Recent Database” you are telling the program to reload the files from the working directory which should be the same as they were just before the crash. In such cases, we suggest that you immediately use the file – save-as feature to turn this into a new model file.
Clicking “Backup Database” deletes the working files and restores the files from the saved model whenever it was last saved. “Cancel” leaves everything alone. If your not sure when the last save occurred, click cancel and then check the modified date of the model file through an explorer window before returning to pick either option.
Starting with version 14.06 an additional backup file is created for models that crash and are then re-opened. A copy of the rss file with the extension .ssr is created if you reopen a model that is already expanded to the working directory indicating a previous crash or incomplete closure. Like the .backup file, the .ssr file can be renamed with a .rss extension to restore that version of the file.
There are two situations where this message might appear. The first is a restriction to the working directory or the model directory. The user needs to have the rights to add, modify and delete files from both locations (preferably administrative rights). See above for more on the working directory.
The second problem is a corrupt or partial model file. If the model file is missing any of the critical component files it will not open correctly and the same message will appear. To investigate, rename the model file, changing the extension form .rss to .zip and double-click it to see what inside. You should see a series of files all with the same name but with a wide range of extensions including (but not limited to) .b3d, .ram and .uid. When a model file does not contain a complete set of component files it is unusable. It is a mystery what causes a file to become this way, but it seems that something must have interrupted the save process. A virus scanner may also be responsible.
At this point the backup file should be used, see below.
The error may be caused by an installation issue with a database component included with RAM Structural System. Removing and reinstalling the component may resolve the issue. To do this, perform the following steps:
* In RAM Structural System version 16 there is no longer a separate option to install the SQL Server only, but repairing the installation should replace it. The same can also be obtained directly from Microsoft.
In rare cases, we are seeing initial settings for some computers (Windows 10) are causing this issue. If all of the above steps do not resolve the issue, please create a service request, attach the machine.config file with the service request and give the path of it.
See also Unable to find the requested .NET framework data provider
Yes, in the directory where the model file is saved, there should be another file of the same name with the extension, “.backup”. Rename this file something.rss (you won’t be able to use the same name of the original model file unless you move or rename it first). The backup file should be a complete version of the model from the previous time it was saved. If your not sure when that was, simply check the modified date.
Note: when backing up your own files, it is only the .rss model file that you need to save. When restoring backup files or old files from a backup CD or tape, make sure the files are not read-only. If you attempt to open a RAM model that is read-only, you will get another warning, “Failed CopyRssFileToWorkingDir:…”, “Failed DeleteRssInWorkingDir:…”, or “File error 2,6”.
Starting in version 17.01, use Ram Manager - File - Save as Archive to create a backup file without analysis results. The save-as dialog will appear and the default file name with match the original with the version and date added as a suffix.
For older versions, see below:
A RAM Structural System model (file.rss) is already a compressed zip file, but the size of that file can become quite large, especially when the analysis and design results are saved with the file. In RAM Manager under the File menu is an option to ZIP the model. When zipping models using that command you will have the opportunity to purge the model of some unnecessary results (which can be regenerated later just by running the file again). The optional results are:
Unable to find the requested .NET framework data provider
RAM Defaults Guide [TN]
RAM SS File-Open Troubleshooting [TN]
RAM Table Editing [FAQ]
Ram SS Installation FAQ