EULA keeps poping up

[benny]

EULA ISSUES

I have read and tried this link and it did not work
http://support.microsoft.com/default.aspx?scid=kb;en-us;837655

I have recently installed hotfix hotfix KB838882 I ran the msp file, BUT
when I try and run the WEBSPS.SQL script in my database I get many errors.
Some follow...

Server: Msg 4604, Level 16, State 1, Line 2
There is no such user or group 'MSProjectServerRole'.

Now when I try to log onto the project server web based thing, it just keeps
bringing me back to the EULA. I am hopping that my problem is in me not
being able to execute the SQL script correctly.

The instructions to exectue are as follows. I think I am following it
correctly, but errors say otherwise.

SQL Stored Procedure Update required to install all ProjectServer patches
-------------------------------------------------------------------------

In order to ensure that your Project Server has all of the fixes contained
in this patch applied correctly, please take the following steps:

1. Run the self-extracting package, which will extract the files to a
temporary directory of your choosing.
2. For each SQL query file (such as WEBSPS.SQL) that is extracted to the
temporary directory you indicated in step 1, follow the following
instructions :

If you are using Microsoft SQL Server as the backend for your Project
Server,

a. Run SQL Query Analyzer on the MAIN SQL SERVER in your configuration.
b. In the database drop-down box, choose the ProjectServer database
c. From the menu, select File/Open, navigate to the SQL Query file
(located in the
temporary directory specified in step 1), and open the file
d. From the menu select Query/Execute
e. When the query is finished executing, you may close Query Analyzer

Thanks for you help all,

Ben

 

[Gary L. Chefetz [MVP]]

Benny:

Until you run the stored procedure correctly, your system is in a unusable
state. You can't half-succeed at applying a service pack and expect the
system to function. Post the command line you're using, and maybe we can
figure out what's going wrong. The error indicates that you're not
specifying the correct database, or you're entering the command incorrectly.

The bouncing EULA page after a SP installation might be cured by deleting
the Project Server active X objects from your workstation.

 

[benny]

Gary,
Thanks for your help. As for the hotfix the instructions I followed are
below with my original post. I think the only thing that I am doing wrong is
I am trying to run the script on the wrong database, but I'm not really sure
how to connect specifically to the project server database. I think I keep
connecting to the master database. So maybe what I am asking is how do you
connect to a specific database?

 

[Gary L. Chefetz [MVP]]

Benny:

Like I said in my previous answer: "Post the command line you're using" and
we'll try to fix it.

 

[benny]

Gary,
I'm guessing you mean the sql statement. There really is no command
line. I open the sql statement in SQL Query Analyzer and run it on the
database. The sql statement is very long, so I'm only going to put a little
in this post and if you want more I can email it to you or post it to a
website.

****************************************************************************************************/

/* Drop the MSP_PROJECTS_AI_TRG trigger if it exists when upgrading 10.5 -
11, since it only needs to exist in a 10.5 scenario */

IF EXISTS (SELECT id FROM dbo.sysobjects WHERE id =
OBJECT_ID(N'dbo.MSP_PROJECTS_AI_TRG')
AND OBJECTPROPERTY(id, N'IsTrigger') = 1)
DROP TRIGGER dbo.MSP_PROJECTS_AI_TRG
GO


/* Remove obsolete P10 stored procedures */


IF EXISTS (SELECT id FROM dbo.sysobjects WHERE id =
OBJECT_ID(N'[dbo].[MSP_WEB_SP_ADM_GetAllCategories]')
AND OBJECTPROPERTY(id, N'IsProcedure') = 1)
DROP PROCEDURE [dbo].[MSP_WEB_SP_ADM_GetAllCategories]
GO


IF EXISTS (SELECT id FROM dbo.sysobjects WHERE id =
OBJECT_ID(N'[dbo].[MSP_WEB_SP_ADM_GetCategoriesForResID]')
AND OBJECTPROPERTY(id, N'IsProcedure') = 1)
DROP PROCEDURE [dbo].[MSP_WEB_SP_ADM_GetCategoriesForResID]
GO


IF EXISTS (SELECT id FROM dbo.sysobjects WHERE id =
OBJECT_ID(N'[dbo].[MSP_WEB_SP_ADM_GetProjectsForCategoryID]')
AND OBJECTPROPERTY(id, N'IsProcedure') = 1)
DROP PROCEDURE [dbo].[MSP_WEB_SP_ADM_GetProjectsForCategoryID]
GO


IF EXISTS (SELECT id FROM dbo.sysobjects WHERE id =
OBJECT_ID(N'[dbo].[MSP_WEB_SP_ADM_GetUsersForCategoryID]')
AND OBJECTPROPERTY(id, N'IsProcedure') = 1)
DROP PROCEDURE [dbo].[MSP_WEB_SP_ADM_GetUsersForCategoryID]
GO


IF EXISTS (SELECT id FROM dbo.sysobjects WHERE id =
OBJECT_ID(N'[dbo].[MSP_WEB_SP_ADM_GetViewsForCategoryID]')
AND OBJECTPROPERTY(id, N'IsProcedure') = 1)
DROP PROCEDURE [dbo].[MSP_WEB_SP_ADM_GetViewsForCategoryID]
GO



The

 

[Gary L. Chefetz [MVP]]

Benny:

The SQL upgrade script is designed to run from a command line. That's the
only way you can specify the server, the database, the account to use to
upgrade, and the password necessary. Running it from query analyzer might
work if you select the database correctly, and you're logged in with the
correct rights. Perhaps that's the crux of the matter here? Did you read the
readme file?

Gary,
I'm guessing you mean the sql statement. There really is no command
line. I open the sql statement in SQL Query Analyzer and run it on the
database. The sql statement is very long, so I'm only going to put a
little
in this post and if you want more I can email it to you or post it to a
website.

****************************************************************************************************/

/* Drop the MSP_PROJECTS_AI_TRG trigger if it exists when upgrading 10.5 -
11, since it only needs to exist in a 10.5 scenario */

IF EXISTS (SELECT id FROM dbo.sysobjects WHERE id =
OBJECT_ID(N'dbo.MSP_PROJECTS_AI_TRG')
AND OBJECTPROPERTY(id, N'IsTrigger') = 1)
DROP TRIGGER dbo.MSP_PROJECTS_AI_TRG
GO


/* Remove obsolete P10 stored procedures */


IF EXISTS (SELECT id FROM dbo.sysobjects WHERE id =
OBJECT_ID(N'[dbo].[MSP_WEB_SP_ADM_GetAllCategories]')
AND OBJECTPROPERTY(id, N'IsProcedure') = 1)
DROP PROCEDURE [dbo].[MSP_WEB_SP_ADM_GetAllCategories]
GO


IF EXISTS (SELECT id FROM dbo.sysobjects WHERE id =
OBJECT_ID(N'[dbo].[MSP_WEB_SP_ADM_GetCategoriesForResID]')
AND OBJECTPROPERTY(id, N'IsProcedure') = 1)
DROP PROCEDURE [dbo].[MSP_WEB_SP_ADM_GetCategoriesForResID]
GO


IF EXISTS (SELECT id FROM dbo.sysobjects WHERE id =
OBJECT_ID(N'[dbo].[MSP_WEB_SP_ADM_GetProjectsForCategoryID]')
AND OBJECTPROPERTY(id, N'IsProcedure') = 1)
DROP PROCEDURE [dbo].[MSP_WEB_SP_ADM_GetProjectsForCategoryID]
GO


IF EXISTS (SELECT id FROM dbo.sysobjects WHERE id =
OBJECT_ID(N'[dbo].[MSP_WEB_SP_ADM_GetUsersForCategoryID]')
AND OBJECTPROPERTY(id, N'IsProcedure') = 1)
DROP PROCEDURE [dbo].[MSP_WEB_SP_ADM_GetUsersForCategoryID]
GO


IF EXISTS (SELECT id FROM dbo.sysobjects WHERE id =
OBJECT_ID(N'[dbo].[MSP_WEB_SP_ADM_GetViewsForCategoryID]')
AND OBJECTPROPERTY(id, N'IsProcedure') = 1)
DROP PROCEDURE [dbo].[MSP_WEB_SP_ADM_GetViewsForCategoryID]
GO



The

Benny:

Like I said in my previous answer: "Post the command line you're using"
and
we'll try to fix it.

 

[benny]

Gary,
I also did this from the command line.
If you are using Microsoft MSDE as the backend for your Project Server,

a. On the MAIN SQL SERVER in your configuration, click Start, click Run,
type "osql -i <tempdir>\<queryfile.sql> -U sa" in the Open box, and then
click OK. For example, if you extracted the files in step 1 to c:\temp and
the name of the query file was websps.sql, you would type "osql -i
c:\temp\websps.sql -U sa". This connects you to the local, default instance
of MSDE 2000 by using the SA account. You may also run osql with another
username that has SA permissions on the server.
b. At the Password prompt, enter the password for the account you used in
step a, and then press ENTER.
c. This will run the sql query file you specified in step a.


I recived a bunch of numbers in the cmd prompt then some errors that looked
similar to the errors I got when running it in the analyser. I have read the
read me. How would I run the script from the command prompt?

Benny:

The SQL upgrade script is designed to run from a command line. That's the
only way you can specify the server, the database, the account to use to
upgrade, and the password necessary. Running it from query analyzer might
work if you select the database correctly, and you're logged in with the
correct rights. Perhaps that's the crux of the matter here? Did you read the
readme file?

Gary,
I'm guessing you mean the sql statement. There really is no command
line. I open the sql statement in SQL Query Analyzer and run it on the
database. The sql statement is very long, so I'm only going to put a
little
in this post and if you want more I can email it to you or post it to a
website.

****************************************************************************************************/

/* Drop the MSP_PROJECTS_AI_TRG trigger if it exists when upgrading 10.5 -
11, since it only needs to exist in a 10.5 scenario */

IF EXISTS (SELECT id FROM dbo.sysobjects WHERE id =
OBJECT_ID(N'dbo.MSP_PROJECTS_AI_TRG')
AND OBJECTPROPERTY(id, N'IsTrigger') = 1)
DROP TRIGGER dbo.MSP_PROJECTS_AI_TRG
GO


/* Remove obsolete P10 stored procedures */


IF EXISTS (SELECT id FROM dbo.sysobjects WHERE id =
OBJECT_ID(N'[dbo].[MSP_WEB_SP_ADM_GetAllCategories]')
AND OBJECTPROPERTY(id, N'IsProcedure') = 1)
DROP PROCEDURE [dbo].[MSP_WEB_SP_ADM_GetAllCategories]
GO


IF EXISTS (SELECT id FROM dbo.sysobjects WHERE id =
OBJECT_ID(N'[dbo].[MSP_WEB_SP_ADM_GetCategoriesForResID]')
AND OBJECTPROPERTY(id, N'IsProcedure') = 1)
DROP PROCEDURE [dbo].[MSP_WEB_SP_ADM_GetCategoriesForResID]
GO


IF EXISTS (SELECT id FROM dbo.sysobjects WHERE id =
OBJECT_ID(N'[dbo].[MSP_WEB_SP_ADM_GetProjectsForCategoryID]')
AND OBJECTPROPERTY(id, N'IsProcedure') = 1)
DROP PROCEDURE [dbo].[MSP_WEB_SP_ADM_GetProjectsForCategoryID]
GO


IF EXISTS (SELECT id FROM dbo.sysobjects WHERE id =
OBJECT_ID(N'[dbo].[MSP_WEB_SP_ADM_GetUsersForCategoryID]')
AND OBJECTPROPERTY(id, N'IsProcedure') = 1)
DROP PROCEDURE [dbo].[MSP_WEB_SP_ADM_GetUsersForCategoryID]
GO


IF EXISTS (SELECT id FROM dbo.sysobjects WHERE id =
OBJECT_ID(N'[dbo].[MSP_WEB_SP_ADM_GetViewsForCategoryID]')
AND OBJECTPROPERTY(id, N'IsProcedure') = 1)
DROP PROCEDURE [dbo].[MSP_WEB_SP_ADM_GetViewsForCategoryID]
GO



The

Benny:

Like I said in my previous answer: "Post the command line you're using"
and
we'll try to fix it.




Gary,
Thanks for your help. As for the hotfix the instructions I followed
are
below with my original post. I think the only thing that I am doing
wrong
is
I am trying to run the script on the wrong database, but I'm not really
sure
how to connect specifically to the project server database. I think I
keep
connecting to the master database. So maybe what I am asking is how do
you
connect to a specific database?

:

Benny:

Until you run the stored procedure correctly, your system is in a
unusable
state. You can't half-succeed at applying a service pack and expect
the
system to function. Post the command line you're using, and maybe we
can
figure out what's going wrong. The error indicates that you're not
specifying the correct database, or you're entering the command
incorrectly.

The bouncing EULA page after a SP installation might be cured by
deleting
the Project Server active X objects from your workstation.




EULA ISSUES

I have read and tried this link and it did not work
http://support.microsoft.com/default.aspx?scid=kb;en-us;837655

I have recently installed hotfix hotfix KB838882 I ran the msp file,
BUT
when I try and run the WEBSPS.SQL script in my database I get many
errors.
Some follow...

Server: Msg 4604, Level 16, State 1, Line 2
There is no such user or group 'MSProjectServerRole'.

Now when I try to log onto the project server web based thing, it
just
keeps
bringing me back to the EULA. I am hopping that my problem is in me
not
being able to execute the SQL script correctly.

The instructions to exectue are as follows. I think I am following
it
correctly, but errors say otherwise.

SQL Stored Procedure Update required to install all ProjectServer
patches
-------------------------------------------------------------------------

In order to ensure that your Project Server has all of the fixes
contained
in this patch applied correctly, please take the following steps:

1. Run the self-extracting package, which will extract the files to
a
temporary directory of your choosing.
2. For each SQL query file (such as WEBSPS.SQL) that is extracted
to
the
temporary directory you indicated in step 1, follow the following
instructions :

If you are using Microsoft SQL Server as the backend for your
Project
Server,

a. Run SQL Query Analyzer on the MAIN SQL SERVER in your
configuration.
b. In the database drop-down box, choose the ProjectServer database
c. From the menu, select File/Open, navigate to the SQL Query file
(located in the
temporary directory specified in step 1), and open the file
d. From the menu select Query/Execute
e. When the query is finished executing, you may close Query
Analyzer

Thanks for you help all,

Ben