Skip to main content


Showing posts with the label Errors

SQL71562: external references are not supported when creating a package from this platform

Last week I got this error from one of developer who was trying to deploy his project from Testing server to SQL Azure QA server. He was using “Deploy Database to SQL Azure” option from SSMS Tool-Task option. After connecting to SQL Azure portal when operation started to deployment below errors occurs. Validation of the schema model for data package failed. Error SQL71562: Error validating element has an unresolved refrence to object xx.dbo.xxxx external refrences are not supported when creating a package from this platform . Reason: The reason of the this error was; some functions of project was dependent on master database and only single database was being deploy to SQL Azure. DACFx must block Export when object definitions (views, procedures, etc.) contain external references, as Azure SQL Database does not allow cross-database external references So, this error was coming. Solution : I suggested him to create those function to locally

The database could not be exclusively locked to perform the operation

When database goes big it will difficult to do any administrative task and think if you have to change the name of database ; then it will be major task. I got below error while changing database name on my test database , users were loged in and i was trying to change the name , database server quickly pop-up error . I tried 2-3 times error was same like below : I followed below step to resolv e this issue :- ALTER DATABASE school SET SINGLE_USER WITH ROLLBACK IMMEDIATE ; GO EXEC sp_renamedb N'school' , N'SQLSchool' ; message - The database name 'SQLSchool' has been set . ALTER DATABASE SQLSchool SET MULTI_USER WITH ROLLBACK IMMEDIATE ;

Database 'distribution' cannot be opened. It has been marked SUSPECT by recovery

Last week I faced an error on testing environment while right click on my subscriber and article property.    ------------------------------ Database 'distribution' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server error log for more information. (Microsoft SQL Server, Error: 926) For help, click: ------------------------------

MySQL showing Wrong Time due to time zone

Last Month Faced an Issue on one of MySQL DB Server. System Date was showing wrong while System time was correct. I compared both time like below:

Could not delete publication 'XXX'. Microsoft SQL Server, Error: 15517

Hey friends, I am filling good to write my 1st post in 2015. This is related to error in replication which i faced in 2014 he he. Last month i was facing an error during roll backing Transnational replication as below.. ------------------------------ Could not delete publication 'XXX'. Microsoft SQL Server, Error: 155 17 TITLE: Microsoft.SqlServer.ConnectionInfo

Some Generic Errors in IIS 7 and IIS 8

Below are two generic errors in every version of IIS. If we deploy applications without few configuration or setting in Application Pool & ISPAI Extension these errors will comes up. There are few changes in IIS 7/ IIS 8 but process are same.  After New installation of IIS and before deploying any Application I do below configuration in IIS 8/7 to remove these error.   The requested content appears to be script and will not be served by the static file handler.  or An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.

safe update mode updates in mySQL workbench error

Error Code: 1175  You are using safe update mode and you tried to update a table without a WHERE that uses a KEY column. above error came in MySQL Workbench 5.2. During executing update command on table using MySQL Workbench 5.2. while updating rows. update bl_user set user_email='' where user_name='suman';

Operating system error 5(Access is denied.)

Actually I should write this post before my last post Network shared Backup , which I shared yesterday. I have decided I will share this week on network database activity. Show this is my 2 nd post on the same. While I was started to backup, restore and creating a database on network shares I faced below errors. And most of the cases issues are related to Start-up services. Generally when we install SQL server the service will be Local or Network in this situation it will not work until we will not change start-up services or we will give full access to the network shared folder.  


Error:  It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS." I faced with above error while implementing application yesterday in the company where I am working. Actually this error will come when Virtual Directory is not being configured as an ASP.NET application. To do so we have to follow below steps :- 

How to recover msdb database from suspect mode

 It was Monday 9 th Jun 47 degr. temperature of Delhi-NCR. Temperature was like boiling me and database. When I reached my office( @ 8.45 am) got an alert from one of Server. “MSDB is in suspected mode” At the same time comes in my mind, this issue will boil me today.. I just tried to cool my self through cold drink then connected server from my local system using windows authentication mode..

Error : Full Backup Failed for server ,, due to Log File is Full

After New Installation of SQL Server database will be in Full Recovery Mode by default. When our Application Goes Live and Transaction started processing we should have a proper Backup-DR plan otherwise We can face below error in SQL server in future. Because it is necessary to Truncate the TLOG in Full Recovery Mode.

Shared Memory Provider, error: 0 - No process is on the other end of the pipe

Error - provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe "A mountain in labour and a mouse be result" .Sometimes it happens in finding Root Couse. I faced the same when I was new in organization. Web application was throwing error something like below …

Error : Database diagram support objects cannot be installed because

When we are going to design an Entity Relationship Diagram 1st time using SSMS in SQL Server, we will face an error of authorization like below.