I got the deployment issue in visual studio and powershell scripts in farm solutions. Most of the solutions in the google are suggesting to do the following steps and I did and restarted the all the servers. But the issue continues. Fortunately I got the real reason after reviewing the sharepoint log file. So the lesson learned is "The reason may be anything and review your log file carefully"
The actions which I tried (not got the solution)
1. Make sure SharePoint timer service should be started on all the servers (web front ends as well as app server)
2. Try restarting the SharePoint Administration service on all the servers.
3. Restart all the SharePoint servers
4. Make sure that all the servers in farm are on the same time zone.
5. Execute stsadm -o execadmsvcjobs on all the servers of the farm
6. Cancel the deployment job by means of central administration, remove the solution and try to add the solution again & check the results.
7. Check the status of the jobs by means of CA-timer job status or use te following command - stsadm -o enumdeployments - This will give you the list of all the pending & active deployments.
Still had the error while cancel the deployment job using CA. The error thrown by CS is "Object reference not set to an instance of an object". This confuses me more and I started reviewing the sharepoint log file using ULS Viewer, and I got the real reason for this strange behaviour.
SharePoint Log Critical Error
Database full error on SQL Server instance 'XXX' in database 'SharePoint_Config'. Additional error information from SQL Server is included below. Could not allocate space for object 'dbo.Tombstones'.'PK_Tombstones' in database 'SharePoint_Config' because the 'PRIMARY' 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.
Solution
Increased the DB size and the issue is resolved
USE master;
GO
ALTER DATABASE SharePoint_Config
MODIFY FILE
(NAME = test1dat3,
SIZE = 10240MB);
GO
or Use "SQL Management Studio" as shown below.
The actions which I tried (not got the solution)
1. Make sure SharePoint timer service should be started on all the servers (web front ends as well as app server)
2. Try restarting the SharePoint Administration service on all the servers.
3. Restart all the SharePoint servers
4. Make sure that all the servers in farm are on the same time zone.
5. Execute stsadm -o execadmsvcjobs on all the servers of the farm
6. Cancel the deployment job by means of central administration, remove the solution and try to add the solution again & check the results.
7. Check the status of the jobs by means of CA-timer job status or use te following command - stsadm -o enumdeployments - This will give you the list of all the pending & active deployments.
Still had the error while cancel the deployment job using CA. The error thrown by CS is "Object reference not set to an instance of an object". This confuses me more and I started reviewing the sharepoint log file using ULS Viewer, and I got the real reason for this strange behaviour.
SharePoint Log Critical Error
Database full error on SQL Server instance 'XXX' in database 'SharePoint_Config'. Additional error information from SQL Server is included below. Could not allocate space for object 'dbo.Tombstones'.'PK_Tombstones' in database 'SharePoint_Config' because the 'PRIMARY' 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.
Solution
Increased the DB size and the issue is resolved
USE master;
GO
ALTER DATABASE SharePoint_Config
MODIFY FILE
(NAME = test1dat3,
SIZE = 10240MB);
GO
or Use "SQL Management Studio" as shown below.
No comments:
Post a Comment