Could not allocate space for object ‘%.*ls’ in database ‘%.*ls’ because the ‘%.*ls’ filegroup is full.

Details
Product: SQL Server
Event ID: 1105
Source: MSSQLServer
Version: 10.0
Component: SQLEngine
Symbolic Name: NO_MORE_SPACE_IN_FG
Message: Could not allocate space for object ‘%.*ls’%.*ls in database ‘%.*ls’ because the ‘%.*ls’ filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.
   
Explanation

No disk space is available in a filegroup.

   
User Action

The following actions may make space available in the filegroup:

  • Turn on autogrow.

  • Add more files to the file group.

  • Free disk space by dropping index or tables that are no longer needed.

  • For more information, see “Troubleshooting Insufficient Data Disk Space” in SQL Server Books Online.

   
   
Version: 9.00.1281.60
Symbolic Name: NO_MORE_SPACE_IN_FG
Message: Could not allocate space for object ‘%.*ls’%.*ls in database ‘%.*ls’ because the ‘%.*ls’ filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.
   
Explanation

No disk space is available in a filegroup.

   
User Action

The following actions may make space available in the filegroup:

  • Turn on autogrow.

  • Add more files to the file group.

  • Free disk space by dropping index or tables that are no longer needed.

  • For more information, see “Troubleshooting Insufficient Data Disk Space” in SQL Server Books Online.

   
   
Version: 9.0
Component: SQLEngine
Symbolic Name: NO_MORE_SPACE_IN_FG
Message: Could not allocate space for object ‘%.*ls’%.*ls in database ‘%.*ls’ because the ‘%.*ls’ filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.
   
Explanation

No disk space is available in a filegroup.

   
User Action

The following actions may make space available in the filegroup:

Turn on autogrow.

Add more files to the file group.

Free disk space by dropping index or tables that are no longer needed.

For more information, see “Troubleshooting Insufficient Data Disk Space” in SQL Server Books Online.

   
   
Version: 8.0
Component: SQL Engine
Message: Could not allocate space for object ‘%.*ls’ in database ‘%.*ls’ because the ‘%.*ls’ filegroup is full.
   
Explanation

The specified filegroup has run out of free space.

   
User Action

To gain more space, you can free disk space on any disk drive containing a file in the full filegroup, allowing files in the group to grow. Or you can gain space using a data file with the specified database.

Freeing disk space

You can free disk space on your local drive or on another disk drive. To free disk space on another drive:

  1. Move the data files in the filegroup with an insufficient amount of free disk space to a different disk drive.
  2. Detach the database by executing sp_detach_db.
  3. Attach the database by executing sp_attach_db, pointing to the moved files.

Using a data file

Another solution is to add a data file to the specified database using the ADD FILE clause of the ALTER DATABASE statement. Or you can enlarge the data file by using the MODIFY FILE clause of the ALTER DATABASE statement, specifying the SIZE and MAXSIZE syntax.

Related:

%1 (%2) %3An attempt to open the file “%4” for read only access failed with system error %6: “%7”. The open file operation will fail with error %5.

Details
Product: Windows Operating System
Event ID: 489
Source: ESENT
Version: 5.2
Symbolic Name: OSFS_OPEN_FILE_RO_ERROR_ID
Message: %1 (%2) %3An attempt to open the file “%4” for read only access failed with system error %6: “%7”. The open file operation will fail with error %5.
   
Explanation

An error occurred while a file was being opened.

Probable causes include:

  • The file is locked or in use.
  • A virus checker might have mistakenly quarantined a file, or a backup process might have temporarily denied access.
  • A flat file backup system or anti-virus software might be running against the database, the check file directories, or the M drive.
  • The permissions on the folder (such as MDBDATA) that contains the files for the information stores are not sufficient for the stores to function correctly.
  • A disk input/output (I/O) problem prevented access to a requested page in the database or to a check file. A disk or controller failure may have occurred, and access to the entire drive was lost, perhaps temporarily. This issue can occur when the path for the check file (such as E00.chk) is not correct.
  • The path for the log files or the check file was changed before the system was restored.
  • The check file (such as E00.chk) is corrupted.
   
User Action

To solve this problem, do one or all of the following:

If the file is locked or in use:

  • Change the permissions on the folders that contain the information store files to the default permissions.
  • Configure the flat file backup and anti-virus software to not scan the Windows Information Store subdirectories or the M drive.
  • Use an online backup and anti-virus software.

If there is an Input/Output problem, do one or all of the following:

  • Run chkdsk /f /r at the command prompt.
  • Examine the permissions on the folder structure.
  • Troubleshoot any file-level antivirus software running.
  • Check the System Log in Event Viewer for any related I/O or drive events.
  • Check and correct the path for the check file (such as E00.chk).
  • Correct the root cause, and then restore from online backup, if there is a recent backup.

If the path was changed:

  • Move the Information Store files back to their original locations and then try to restore again.
  • If the .chk file is corrupt, you may be able to remove it and read all the transactions into the database. If the database remains inconsistent, then restore from online backup if there is a recent version.

For more information about this event, see article Q823022 in the Microsoft Knowledge Base.

Related:

IIS reports 401.3 error for static files, but appears to have correct ACL

I am working on a website running Sitecore 6.3.1 on a Windows Server 2008 R2 instance.

Everything was working beautifully until I copied some static files (CSS, JS, images) from a ZIP archive provided by one of our frontend developers into C:\Inetpub\wwwroot\(website name)\Website\static.

Now, any time I try to access any of those static files (e.g., http://localhost/static/css/main.css), I get a 401.3 error (according to C:\inetpub\logs\LogFiles\W3SVC2\u_ex110216.log).

The Sitecore application itself is working just fine, and the static files were perfectly accessible until I replaced them with the updated files.

According to every resource I could find on the subject, a 401.3 error indicates that the ACL for the requested resource is not permitting access to the IIS user account.

  • I looked at the ACL for a file that is currently working (e.g., C:\Inetpub\wwwroot\(website name)\Website\default.css), and it appears to be identical to that of the static files that are inaccessible.

  • I checked the application pool settings for the Sitecore site, and the anonymous user is “IUSR”. Following the instructions in this thread, I gave the IUSR account read and execute permissions for the C:\Inetpub\wwwroot\(website name)\Website\static directory and recursively applied it to all subfolders and files in that directory. No dice.

  • Based on the suggestions offered in this thread, I tried removing the static directory entirely and recreating it and its subdirectories by hand so that they inherit permissions from the parent Website directory. However, the problem persisted.

What else can I try to resolve these 401.3 errors?

Related:

How can I rewrite / redirect URL’s in Glassfish V3?

I’d like to simplify the URL’s to access a Glassfish V3 application by removing file extensions and otherwise shortening URL’s.

I’ve already set my application as the default application, so that there is no need to include the context root in the URL.

I’d like to:
* Remove file extensions
* Shorten the URL to files deep in the folder structure

I’d like to do this using pattern matching rather than on a per file basis (Site is small at the moment but will change frequently and grow).

Some examples of what I’d like to do:
* foo.com/bar.html -> foo.com/bar
* foo.com/folder1/folder2/bar2.html -> foo.com/bar2

Any help would be greatly appreciated. Thanks.

Cheers,

Jin

Related: