When running application update scripts in SQL Server Query Analyzer (QA) program raises a lot of error conditions that are not really problems and can be safely ignored.

Follows are the most common error conditions that the SQL Server QA programs flags: 

"No Such User Or Group enterprise"

When this occurs, and you know for sure that you have set-sup user enterprise in your particular system, and you should be logged in as user enterprise when running the script, then this error is telling you that it can't switch to user enterprise because you are already logged on as user enterprise. This can be ignored. You can verify after the fact that the script did run the update to be doubly sure.

Dependence Issues 

Sometimes if the script generates a series of new stored procedures, and the calling or parent stored procedure is scripted before the child stored procedure, the system will give an error message that states that the Child Entity can't be found, but states that the stored procedure will be generated anyway. This is not an error condition and these messages can be safely ignored.