Problem with SQLServer 2000

i installed the Visual Studio 2004+ Framework.NET 2

and SQLserver 2005

after those

i installed SQLserver 2000

and i got this :

http://img240.imageshack.us/img240/7392/sql2fk.jpg

thank you

This is the wrong forum. From your screenshot it looks like you should be checking the Express forum: http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=385&SiteID=1

In the meantime, have you checked in the Services panel that SQL Server is running?

Have you enabled remote conenctions using the Surface Area configuraiton tool?

-Jamie

|||what should i change here?

http://img86.imageshack.us/img86/746/remote6np.jpg

thank you|||

From the screenshot http://img240.imageshack.us/img240/7392/sql2fk.jpg - it looks like you are trying to access SQL Server 2005 Express Edition from SQL Server Enterprise Manager.

Try accessing SQL Server 2005 express edition from SQL Server Management Studio (which is equivalent of SQL Server 2000 Enterprise manager for SQL Server 2005.)

Thanks,
Loonysan

|||i dont know what do u mean...

i even dont need SQL server 2005 i need only the 2000...

but i have heard that removing SQL server 2005 from my computer wont work...

can someone give me step by step what to do to solve the problem...

thank you :D|||

deViance wrote:

i dont know what do u mean...
i even dont need SQL server 2005 i need only the 2000...
but i have heard that removing SQL server 2005 from my computer wont work...
can someone give me step by step what to do to solve the problem...

thank you :D

For a starter, you are in the wrong place.

If you don't need SQL2005 why did you install it? What exactly are you trying to do?

-Jamie

Problem with SQLH2

Hi all i have problem with SQLH2. SQLH2 installed on Windows XP Pro SP2
Russian.
Version SQLH2 is H2 Collector ver. V2 2.0.024.0 9/30/04 17:58
this is log
28.12.2004 15:00:16 Opening Log
28.12.2004 15:00:16 SQLH2 ver. V2 2.0.024.0 9/30/04 17:58
28.12.2004 15:00:16 Status: Init
28.12.2004 15:00:16 WARNING: There are no PerfProviders in the config file
28.12.2004 15:00:16 Status: Initializing repository: manushind
28.12.2004 15:00:16 Status: Repository Database: SQLH2Repository
28.12.2004 15:00:16 INFO: host_id = 1
28.12.2004 15:00:16 Status: Starting RUN
28.12.2004 15:00:16 Status: Registering Run
28.12.2004 15:00:16 INFO: run_id = 8
28.12.2004 15:00:16 Status: Starting Targets processing
28.12.2004 15:00:16 Status: Initializing Target: SRV-ELDDB2
28.12.2004 15:00:16 Status: registering Server
28.12.2004 15:00:16 INFO: srv_id = 2; signature =
aad193c2-d36c-4760-a312-57dc78d07944
28.12.2004 15:00:16 Status: Scanning Registry on SRV-ELDDB2
28.12.2004 15:00:16 Status: registering instance SRV-ELDDB2
28.12.2004 15:00:16 INFO: inst_id = 1
28.12.2004 15:00:16 INFO: version: 8.00.818
28.12.2004 15:00:16 Status: RUN
28.12.2004 15:00:16 Status: Initializing collector: WMI
28.12.2004 15:00:16 Status: Running WMI collector
28.12.2004 15:00:16 Status: Opening Unit 1 (OS/CS)
28.12.2004 15:00:16 Status: Collecting Win32_OperatingSystem
28.12.2004 15:00:17 Status: Closing Unit 1
28.12.2004 15:00:17 ERROR: NotFound
28.12.2004 15:00:17 WARNING: WMI Collector encountered critical error.
Abandoning Collector.
28.12.2004 15:00:17 Status: Initializing collector: EventLog
28.12.2004 15:00:17 Status: Initializing collector: SQL
28.12.2004 15:00:17 Status: Running SQL collector on SRV-ELDDB2
28.12.2004 15:00:17 Status: Opening Unit 5 (Server Properties)
28.12.2004 15:00:17 Status: Closing Unit 5
28.12.2004 15:00:17 Status: Opening Unit 1 (Databases)
28.12.2004 15:00:18 ERROR: There are fewer columns in the INSERT statement
than values specified in the VALUES clause. The number of values in the
VALUES clause must match the number of columns specified in the INSERT
statement.
28.12.2004 15:00:18 ERROR: Insert dbo.c_database
(run_id,srv_id,inst_id,dbid,name,CompatibilityLeve l,CreateDate,DataSpaceUsage,IndexSpaceUsage,dbSize ,SpaceAvailable,IsSystem,txSize,txSpaceAvailable,t xLastBackup,oRecoveryModel,oPageVerify,oUserAccess ,oAutoClose,oAutoShrink,oAutoCreateStat,oAutoUpdat eStat
,oOffline,oReadOnly,oSelectIntoBulkCopy,oTruncateL ogOnCheckpoint,oPublished,oSubscribed,oMergePublis hed,oMergeSubscribed,oFullTextEnabled,oDbChaining)
Values (8, 2, 1, 8, 'auxdb', 80, '15.12.2004 15:25:56', 15904, 368,
38,812500, 8,414063, 0, 1,250000, 0,820313, '18.12.2003 1:35:22', 3, 1, 0, 0,
0, 1, 1, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0)
28.12.2004 15:00:18 ERROR: Unit 1 failed
28.12.2004 15:00:18 Status: Closing Unit 1
28.12.2004 15:00:18 ERROR: Insert dbo.c_database
(run_id,srv_id,inst_id,dbid,name,CompatibilityLeve l,CreateDate,DataSpaceUsage,IndexSpaceUsage,dbSize ,SpaceAvailable,IsSystem,txSize,txSpaceAvailable,t xLastBackup,oRecoveryModel,oPageVerify,oUserAccess ,oAutoClose,oAutoShrink,oAutoCreateStat,oAutoUpdat eStat
,oOffline,oReadOnly,oSelectIntoBulkCopy,oTruncateL ogOnCheckpoint,oPublished,oSubscribed,oMergePublis hed,oMergeSubscribed,oFullTextEnabled,oDbChaining)
Values (8, 2, 1, 8, 'auxdb', 80, '15.12.2004 15:25:56', 15904, 368,
38,812500, 8,414063, 0, 1,250000, 0,820313, '18.12.2003 1:35:22', 3, 1, 0, 0,
0, 1, 1, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0)
28.12.2004 15:00:18 ERROR: SRV-ELDDB2: Collection failed; Error:104;
Provider Error: 110
28.12.2004 15:00:18 ERROR: Critical Repository Failure
28.12.2004 15:00:18 SQLH2 is shutting down
28.12.2004 15:00:18 Closing Log
P.S.
i have Domain admins right.
Thank you.
Dimitri,
I suspect this is a localisation issue. Is your decimal symbol a comma by
any chance?
If you look at the Appendix C of the SQLH2 Deployment Guide (this should be
in your root installation directory), you will see some useful hints on how
to get SQLH2 working on localised Windows platforms.
Looking at your log, I would also advise that your dates are not in the
expected format for SQLH2, so you will need to use the /D switch (again
please see Appendix C).
Hope this helps,
John Marsh
"dmitri" wrote:

> Hi all i have problem with SQLH2. SQLH2 installed on Windows XP Pro SP2
> Russian.
> Version SQLH2 is H2 Collector ver. V2 2.0.024.0 9/30/04 17:58
> this is log
> 28.12.2004 15:00:16 Opening Log
> 28.12.2004 15:00:16 SQLH2 ver. V2 2.0.024.0 9/30/04 17:58
> 28.12.2004 15:00:16 Status: Init
> 28.12.2004 15:00:16 WARNING: There are no PerfProviders in the config file
> 28.12.2004 15:00:16 Status: Initializing repository: manushind
> 28.12.2004 15:00:16 Status: Repository Database: SQLH2Repository
> 28.12.2004 15:00:16 INFO: host_id = 1
> 28.12.2004 15:00:16 Status: Starting RUN
> 28.12.2004 15:00:16 Status: Registering Run
> 28.12.2004 15:00:16 INFO: run_id = 8
> 28.12.2004 15:00:16 Status: Starting Targets processing
> 28.12.2004 15:00:16 Status: Initializing Target: SRV-ELDDB2
> 28.12.2004 15:00:16 Status: registering Server
> 28.12.2004 15:00:16 INFO: srv_id = 2; signature =
> aad193c2-d36c-4760-a312-57dc78d07944
> 28.12.2004 15:00:16 Status: Scanning Registry on SRV-ELDDB2
> 28.12.2004 15:00:16 Status: registering instance SRV-ELDDB2
> 28.12.2004 15:00:16 INFO: inst_id = 1
> 28.12.2004 15:00:16 INFO: version: 8.00.818
> 28.12.2004 15:00:16 Status: RUN
> 28.12.2004 15:00:16 Status: Initializing collector: WMI
> 28.12.2004 15:00:16 Status: Running WMI collector
> 28.12.2004 15:00:16 Status: Opening Unit 1 (OS/CS)
> 28.12.2004 15:00:16 Status: Collecting Win32_OperatingSystem
> 28.12.2004 15:00:17 Status: Closing Unit 1
> 28.12.2004 15:00:17 ERROR: NotFound
> 28.12.2004 15:00:17 WARNING: WMI Collector encountered critical error.
> Abandoning Collector.
> 28.12.2004 15:00:17 Status: Initializing collector: EventLog
> 28.12.2004 15:00:17 Status: Initializing collector: SQL
> 28.12.2004 15:00:17 Status: Running SQL collector on SRV-ELDDB2
> 28.12.2004 15:00:17 Status: Opening Unit 5 (Server Properties)
> 28.12.2004 15:00:17 Status: Closing Unit 5
> 28.12.2004 15:00:17 Status: Opening Unit 1 (Databases)
> 28.12.2004 15:00:18 ERROR: There are fewer columns in the INSERT statement
> than values specified in the VALUES clause. The number of values in the
> VALUES clause must match the number of columns specified in the INSERT
> statement.
> 28.12.2004 15:00:18 ERROR: Insert dbo.c_database
> (run_id,srv_id,inst_id,dbid,name,CompatibilityLeve l,CreateDate,DataSpaceUsage,IndexSpaceUsage,dbSize ,SpaceAvailable,IsSystem,txSize,txSpaceAvailable,t xLastBackup,oRecoveryModel,oPageVerify,oUserAccess ,oAutoClose,oAutoShrink,oAutoCreateStat,oAutoUpdat eSt
at,oOffline,oReadOnly,oSelectIntoBulkCopy,oTruncat eLogOnCheckpoint,oPublished,oSubscribed,oMergePubl ished,oMergeSubscribed,oFullTextEnabled,oDbChainin g)
> Values (8, 2, 1, 8, 'auxdb', 80, '15.12.2004 15:25:56', 15904, 368,
> 38,812500, 8,414063, 0, 1,250000, 0,820313, '18.12.2003 1:35:22', 3, 1, 0, 0,
> 0, 1, 1, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0)
> 28.12.2004 15:00:18 ERROR: Unit 1 failed
> 28.12.2004 15:00:18 Status: Closing Unit 1
> 28.12.2004 15:00:18 ERROR: Insert dbo.c_database
> (run_id,srv_id,inst_id,dbid,name,CompatibilityLeve l,CreateDate,DataSpaceUsage,IndexSpaceUsage,dbSize ,SpaceAvailable,IsSystem,txSize,txSpaceAvailable,t xLastBackup,oRecoveryModel,oPageVerify,oUserAccess ,oAutoClose,oAutoShrink,oAutoCreateStat,oAutoUpdat eSt
at,oOffline,oReadOnly,oSelectIntoBulkCopy,oTruncat eLogOnCheckpoint,oPublished,oSubscribed,oMergePubl ished,oMergeSubscribed,oFullTextEnabled,oDbChainin g)
> Values (8, 2, 1, 8, 'auxdb', 80, '15.12.2004 15:25:56', 15904, 368,
> 38,812500, 8,414063, 0, 1,250000, 0,820313, '18.12.2003 1:35:22', 3, 1, 0, 0,
> 0, 1, 1, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0)
> 28.12.2004 15:00:18 ERROR: SRV-ELDDB2: Collection failed; Error:104;
> Provider Error: 110
> 28.12.2004 15:00:18 ERROR: Critical Repository Failure
> 28.12.2004 15:00:18 SQLH2 is shutting down
> 28.12.2004 15:00:18 Closing Log
> P.S.
> i have Domain admins right.
> Thank you.
|||John, i see this hints but not try use it yet. I hope this help. thank you.
"John Marsh" wrote:
[vbcol=seagreen]
> Dimitri,
> I suspect this is a localisation issue. Is your decimal symbol a comma by
> any chance?
> If you look at the Appendix C of the SQLH2 Deployment Guide (this should be
> in your root installation directory), you will see some useful hints on how
> to get SQLH2 working on localised Windows platforms.
> Looking at your log, I would also advise that your dates are not in the
> expected format for SQLH2, so you will need to use the /D switch (again
> please see Appendix C).
> Hope this helps,
> John Marsh
>
> "dmitri" wrote:
Stat,oOffline,oReadOnly,oSelectIntoBulkCopy,oTrunc ateLogOnCheckpoint,oPublished,oSubscribed,oMergePu blished,oMergeSubscribed,oFullTextEnabled,oDbChain ing)[vbcol=seagreen]
Stat,oOffline,oReadOnly,oSelectIntoBulkCopy,oTrunc ateLogOnCheckpoint,oPublished,oSubscribed,oMergePu blished,oMergeSubscribed,oFullTextEnabled,oDbChain ing)[vbcol=seagreen]

Problem with SQL Server Managment Studio Express CTP

Hi, I have installed the product in subject but after installation if a click on program to use it, i have no result.

Someone can tell me how i can control why it no work?

The real problem is that it no give me an error code simply the program not start.?!?!?

Thank's for your attention.

By Fabrizio

I find...

When you downloaded the updated Management Studio Express, did you see it take some time to download it again, or did it start immediately? (If it starts immediately, you're running a cached copy of the Windows installer package for SSMSE.)

If you rename the "HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\90\Tools\Shell" registry key to "HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\90\Tools\ShellX" using regedit, SSMSE should start. This should not affect the stand-alone Books Online at all.

After you rename the registry key and then start Management Studio Express, does the splash Screen say "SQL Server Management Studio Express Edition" or just "Management Studio Express"? The November 11 download says "Management Studio Express."

Problem with SQL Server 2005 dev edition

Hi
I have just installed SQL Server 2005 dev edition. I successfully have
created a new database and a table in that database. When I try to open the
table (right click on the table and choose Open Table) I get the error
"Unspecified error" and there is nothing shown. What is wrong and how can I
fix this?
Thanks!
Julia
Julia
Hmmm, strange. Have you try SELECT * FROM table from Query Builder?
Also take a look at ERRO.LOG to see some info
"Julia" <Julia@.discussions.microsoft.com> wrote in message
news:28B6CE1C-D855-4FC3-A138-73103C4CAC9C@.microsoft.com...
> Hi
> I have just installed SQL Server 2005 dev edition. I successfully have
> created a new database and a table in that database. When I try to open
> the
> table (right click on the table and choose Open Table) I get the error
> "Unspecified error" and there is nothing shown. What is wrong and how can
> I
> fix this?
> Thanks!
> Julia

Problem with SQL Server 2005 dev edition

Hi
I have just installed SQL Server 2005 dev edition. I successfully have
created a new database and a table in that database. When I try to open the
table (right click on the table and choose Open Table) I get the error
"Unspecified error" and there is nothing shown. What is wrong and how can I
fix this?
Thanks!
JuliaJulia
Hmmm, strange. Have you try SELECT * FROM table from Query Builder?
Also take a look at ERRO.LOG to see some info
"Julia" <Julia@.discussions.microsoft.com> wrote in message
news:28B6CE1C-D855-4FC3-A138-73103C4CAC9C@.microsoft.com...
> Hi
> I have just installed SQL Server 2005 dev edition. I successfully have
> created a new database and a table in that database. When I try to open
> the
> table (right click on the table and choose Open Table) I get the error
> "Unspecified error" and there is nothing shown. What is wrong and how can
> I
> fix this?
> Thanks!
> Julia

Problem with SQL Query file

I'm hoping you can help with something.
I've installed the Project Server post SP1 Hotfix in my test lab and all
looks ok, apart from some errors when I execute the websps.sql query file
that forms part of the hotfix. The errors look like this.
There is no such user or group 'MSProjectServerRole'.
Here's an example of one of the entries in the query file that generates the
error.
/* Query #65005 */
CREATE PROCEDURE dbo.MSP_WEB_SP_QRY_GetNotificationAdminInfo
AS
select WADMIN_SMTP_SERVER_NAME,
WADMIN_SMTP_SERVER_PORT,
WADMIN_DEFAULT_LANGUAGE,
WADMIN_NTFY_FROM_EMAIL,
WADMIN_NTFY_EMAIL_TRAILER,
WADMIN_ORG_EMAIL_ADDRESS,
WADMIN_NPE_LAST_RUN,
WADMIN_NPE_NEXT_RUN,
WADMIN_NPE_SCHEDULED_TIME,
WADMIN_INTRANET_SERVER_URL,
WADMIN_EXTRANET_SERVER_URL,
WADMIN_EMAIL_CHARSET
from MSP_WEB_ADMIN
RETURN
GO
GRANT EXECUTE ON dbo.MSP_WEB_SP_QRY_GetNotificationAdminInfo TO
MSProjectServerRole
GO
********************************
I've checked that the MSProjectServerRole exists and is populated with
MSProjectServerUser, so all looks ok. I'm confused as to why the execution
of the stored procedure comes up with the error. The CREATE PROCEDURE part
doesn't appear to work as the stored procedure
MSP_WEB_SP_QRY_GetNotificationAdminInfo does not appear in Enterprise Manager
after the query file has finished executing.
Not being a SQL guy, can anyone give me a pointer as to how I can
troubleshoot this problem? I'm executing the query file as sa, so I don't
think this is a permissions thing.
Thanks
Tony
It appears that you created the proc in the wrong database. Likely, you put
it in master.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"Tony Murray" <TonyMurray@.discussions.microsoft.com> wrote in message
news:1530354A-94BA-4F8C-B1E7-F31980B603A9@.microsoft.com...
I'm hoping you can help with something.
I've installed the Project Server post SP1 Hotfix in my test lab and all
looks ok, apart from some errors when I execute the websps.sql query file
that forms part of the hotfix. The errors look like this.
There is no such user or group 'MSProjectServerRole'.
Here's an example of one of the entries in the query file that generates the
error.
/* Query #65005 */
CREATE PROCEDURE dbo.MSP_WEB_SP_QRY_GetNotificationAdminInfo
AS
select WADMIN_SMTP_SERVER_NAME,
WADMIN_SMTP_SERVER_PORT,
WADMIN_DEFAULT_LANGUAGE,
WADMIN_NTFY_FROM_EMAIL,
WADMIN_NTFY_EMAIL_TRAILER,
WADMIN_ORG_EMAIL_ADDRESS,
WADMIN_NPE_LAST_RUN,
WADMIN_NPE_NEXT_RUN,
WADMIN_NPE_SCHEDULED_TIME,
WADMIN_INTRANET_SERVER_URL,
WADMIN_EXTRANET_SERVER_URL,
WADMIN_EMAIL_CHARSET
from MSP_WEB_ADMIN
RETURN
GO
GRANT EXECUTE ON dbo.MSP_WEB_SP_QRY_GetNotificationAdminInfo TO
MSProjectServerRole
GO
********************************
I've checked that the MSProjectServerRole exists and is populated with
MSProjectServerUser, so all looks ok. I'm confused as to why the execution
of the stored procedure comes up with the error. The CREATE PROCEDURE part
doesn't appear to work as the stored procedure
MSP_WEB_SP_QRY_GetNotificationAdminInfo does not appear in Enterprise
Manager
after the query file has finished executing.
Not being a SQL guy, can anyone give me a pointer as to how I can
troubleshoot this problem? I'm executing the query file as sa, so I don't
think this is a permissions thing.
Thanks
Tony
|||Thanks Tom, you were spot-on :-) I had highlighted the ProjectServer
database in the left hand pane of Query Analyzer, but had not specified it in
the drop down list in the right pane.
Tony
"Tom Moreau" wrote:

> It appears that you created the proc in the wrong database. Likely, you put
> it in master.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> ..
> "Tony Murray" <TonyMurray@.discussions.microsoft.com> wrote in message
> news:1530354A-94BA-4F8C-B1E7-F31980B603A9@.microsoft.com...
> I'm hoping you can help with something.
> I've installed the Project Server post SP1 Hotfix in my test lab and all
> looks ok, apart from some errors when I execute the websps.sql query file
> that forms part of the hotfix. The errors look like this.
> There is no such user or group 'MSProjectServerRole'.
> Here's an example of one of the entries in the query file that generates the
> error.
> /* Query #65005 */
> CREATE PROCEDURE dbo.MSP_WEB_SP_QRY_GetNotificationAdminInfo
> AS
> select WADMIN_SMTP_SERVER_NAME,
> WADMIN_SMTP_SERVER_PORT,
> WADMIN_DEFAULT_LANGUAGE,
> WADMIN_NTFY_FROM_EMAIL,
> WADMIN_NTFY_EMAIL_TRAILER,
> WADMIN_ORG_EMAIL_ADDRESS,
> WADMIN_NPE_LAST_RUN,
> WADMIN_NPE_NEXT_RUN,
> WADMIN_NPE_SCHEDULED_TIME,
> WADMIN_INTRANET_SERVER_URL,
> WADMIN_EXTRANET_SERVER_URL,
> WADMIN_EMAIL_CHARSET
> from MSP_WEB_ADMIN
> RETURN
> GO
> GRANT EXECUTE ON dbo.MSP_WEB_SP_QRY_GetNotificationAdminInfo TO
> MSProjectServerRole
> GO
> ********************************
> I've checked that the MSProjectServerRole exists and is populated with
> MSProjectServerUser, so all looks ok. I'm confused as to why the execution
> of the stored procedure comes up with the error. The CREATE PROCEDURE part
> doesn't appear to work as the stored procedure
> MSP_WEB_SP_QRY_GetNotificationAdminInfo does not appear in Enterprise
> Manager
> after the query file has finished executing.
> Not being a SQL guy, can anyone give me a pointer as to how I can
> troubleshoot this problem? I'm executing the query file as sa, so I don't
> think this is a permissions thing.
> Thanks
> Tony
>
|||It's a common problem with DBA's. We usually belong to the sysadmin role
and have a default DB of master. If you include a USE statement, that can
fend off the wrong DB problem. Any object you create should also have the
appropriate GRANT statements, too. When you're in sysadmin, it always
works.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"Tony Murray" <TonyMurray@.discussions.microsoft.com> wrote in message
news:209BE0C0-C948-4AE6-886E-F87A76AC3823@.microsoft.com...
Thanks Tom, you were spot-on :-) I had highlighted the ProjectServer
database in the left hand pane of Query Analyzer, but had not specified it
in
the drop down list in the right pane.
Tony
"Tom Moreau" wrote:

> It appears that you created the proc in the wrong database. Likely, you
> put
> it in master.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> ..
> "Tony Murray" <TonyMurray@.discussions.microsoft.com> wrote in message
> news:1530354A-94BA-4F8C-B1E7-F31980B603A9@.microsoft.com...
> I'm hoping you can help with something.
> I've installed the Project Server post SP1 Hotfix in my test lab and all
> looks ok, apart from some errors when I execute the websps.sql query file
> that forms part of the hotfix. The errors look like this.
> There is no such user or group 'MSProjectServerRole'.
> Here's an example of one of the entries in the query file that generates
> the
> error.
> /* Query #65005 */
> CREATE PROCEDURE dbo.MSP_WEB_SP_QRY_GetNotificationAdminInfo
> AS
> select WADMIN_SMTP_SERVER_NAME,
> WADMIN_SMTP_SERVER_PORT,
> WADMIN_DEFAULT_LANGUAGE,
> WADMIN_NTFY_FROM_EMAIL,
> WADMIN_NTFY_EMAIL_TRAILER,
> WADMIN_ORG_EMAIL_ADDRESS,
> WADMIN_NPE_LAST_RUN,
> WADMIN_NPE_NEXT_RUN,
> WADMIN_NPE_SCHEDULED_TIME,
> WADMIN_INTRANET_SERVER_URL,
> WADMIN_EXTRANET_SERVER_URL,
> WADMIN_EMAIL_CHARSET
> from MSP_WEB_ADMIN
> RETURN
> GO
> GRANT EXECUTE ON dbo.MSP_WEB_SP_QRY_GetNotificationAdminInfo TO
> MSProjectServerRole
> GO
> ********************************
> I've checked that the MSProjectServerRole exists and is populated with
> MSProjectServerUser, so all looks ok. I'm confused as to why the
> execution
> of the stored procedure comes up with the error. The CREATE PROCEDURE
> part
> doesn't appear to work as the stored procedure
> MSP_WEB_SP_QRY_GetNotificationAdminInfo does not appear in Enterprise
> Manager
> after the query file has finished executing.
> Not being a SQL guy, can anyone give me a pointer as to how I can
> troubleshoot this problem? I'm executing the query file as sa, so I don't
> think this is a permissions thing.
> Thanks
> Tony
>

Problem with SQL Query file

I'm hoping you can help with something.
I've installed the Project Server post SP1 Hotfix in my test lab and all
looks ok, apart from some errors when I execute the websps.sql query file
that forms part of the hotfix. The errors look like this.
There is no such user or group 'MSProjectServerRole'.
Here's an example of one of the entries in the query file that generates the
error.
/* Query #65005 */
CREATE PROCEDURE dbo.MSP_WEB_SP_QRY_GetNotificationAdminInfo
AS
select WADMIN_SMTP_SERVER_NAME,
WADMIN_SMTP_SERVER_PORT,
WADMIN_DEFAULT_LANGUAGE,
WADMIN_NTFY_FROM_EMAIL,
WADMIN_NTFY_EMAIL_TRAILER,
WADMIN_ORG_EMAIL_ADDRESS,
WADMIN_NPE_LAST_RUN,
WADMIN_NPE_NEXT_RUN,
WADMIN_NPE_SCHEDULED_TIME,
WADMIN_INTRANET_SERVER_URL,
WADMIN_EXTRANET_SERVER_URL,
WADMIN_EMAIL_CHARSET
from MSP_WEB_ADMIN
RETURN
GO
GRANT EXECUTE ON dbo.MSP_WEB_SP_QRY_GetNotificationAdminInfo TO
MSProjectServerRole
GO
********************************
I've checked that the MSProjectServerRole exists and is populated with
MSProjectServerUser, so all looks ok. I'm confused as to why the execution
of the stored procedure comes up with the error. The CREATE PROCEDURE part
doesn't appear to work as the stored procedure
MSP_WEB_SP_QRY_GetNotificationAdminInfo does not appear in Enterprise Manage
r
after the query file has finished executing.
Not being a SQL guy, can anyone give me a pointer as to how I can
troubleshoot this problem? I'm executing the query file as sa, so I don't
think this is a permissions thing.
Thanks
TonyIt appears that you created the proc in the wrong database. Likely, you put
it in master.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"Tony Murray" <TonyMurray@.discussions.microsoft.com> wrote in message
news:1530354A-94BA-4F8C-B1E7-F31980B603A9@.microsoft.com...
I'm hoping you can help with something.
I've installed the Project Server post SP1 Hotfix in my test lab and all
looks ok, apart from some errors when I execute the websps.sql query file
that forms part of the hotfix. The errors look like this.
There is no such user or group 'MSProjectServerRole'.
Here's an example of one of the entries in the query file that generates the
error.
/* Query #65005 */
CREATE PROCEDURE dbo.MSP_WEB_SP_QRY_GetNotificationAdminInfo
AS
select WADMIN_SMTP_SERVER_NAME,
WADMIN_SMTP_SERVER_PORT,
WADMIN_DEFAULT_LANGUAGE,
WADMIN_NTFY_FROM_EMAIL,
WADMIN_NTFY_EMAIL_TRAILER,
WADMIN_ORG_EMAIL_ADDRESS,
WADMIN_NPE_LAST_RUN,
WADMIN_NPE_NEXT_RUN,
WADMIN_NPE_SCHEDULED_TIME,
WADMIN_INTRANET_SERVER_URL,
WADMIN_EXTRANET_SERVER_URL,
WADMIN_EMAIL_CHARSET
from MSP_WEB_ADMIN
RETURN
GO
GRANT EXECUTE ON dbo.MSP_WEB_SP_QRY_GetNotificationAdminInfo TO
MSProjectServerRole
GO
********************************
I've checked that the MSProjectServerRole exists and is populated with
MSProjectServerUser, so all looks ok. I'm confused as to why the execution
of the stored procedure comes up with the error. The CREATE PROCEDURE part
doesn't appear to work as the stored procedure
MSP_WEB_SP_QRY_GetNotificationAdminInfo does not appear in Enterprise
Manager
after the query file has finished executing.
Not being a SQL guy, can anyone give me a pointer as to how I can
troubleshoot this problem? I'm executing the query file as sa, so I don't
think this is a permissions thing.
Thanks
Tony|||Thanks Tom, you were spot-on :-) I had highlighted the ProjectServer
database in the left hand pane of Query Analyzer, but had not specified it i
n
the drop down list in the right pane.
Tony
"Tom Moreau" wrote:

> It appears that you created the proc in the wrong database. Likely, you p
ut
> it in master.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> ..
> "Tony Murray" <TonyMurray@.discussions.microsoft.com> wrote in message
> news:1530354A-94BA-4F8C-B1E7-F31980B603A9@.microsoft.com...
> I'm hoping you can help with something.
> I've installed the Project Server post SP1 Hotfix in my test lab and all
> looks ok, apart from some errors when I execute the websps.sql query file
> that forms part of the hotfix. The errors look like this.
> There is no such user or group 'MSProjectServerRole'.
> Here's an example of one of the entries in the query file that generates t
he
> error.
> /* Query #65005 */
> CREATE PROCEDURE dbo.MSP_WEB_SP_QRY_GetNotificationAdminInfo
> AS
> select WADMIN_SMTP_SERVER_NAME,
> WADMIN_SMTP_SERVER_PORT,
> WADMIN_DEFAULT_LANGUAGE,
> WADMIN_NTFY_FROM_EMAIL,
> WADMIN_NTFY_EMAIL_TRAILER,
> WADMIN_ORG_EMAIL_ADDRESS,
> WADMIN_NPE_LAST_RUN,
> WADMIN_NPE_NEXT_RUN,
> WADMIN_NPE_SCHEDULED_TIME,
> WADMIN_INTRANET_SERVER_URL,
> WADMIN_EXTRANET_SERVER_URL,
> WADMIN_EMAIL_CHARSET
> from MSP_WEB_ADMIN
> RETURN
> GO
> GRANT EXECUTE ON dbo.MSP_WEB_SP_QRY_GetNotificationAdminInfo TO
> MSProjectServerRole
> GO
> ********************************
> I've checked that the MSProjectServerRole exists and is populated with
> MSProjectServerUser, so all looks ok. I'm confused as to why the executio
n
> of the stored procedure comes up with the error. The CREATE PROCEDURE pa
rt
> doesn't appear to work as the stored procedure
> MSP_WEB_SP_QRY_GetNotificationAdminInfo does not appear in Enterprise
> Manager
> after the query file has finished executing.
> Not being a SQL guy, can anyone give me a pointer as to how I can
> troubleshoot this problem? I'm executing the query file as sa, so I don't
> think this is a permissions thing.
> Thanks
> Tony
>|||It's a common problem with DBA's. We usually belong to the sysadmin role
and have a default DB of master. If you include a USE statement, that can
fend off the wrong DB problem. Any object you create should also have the
appropriate GRANT statements, too. When you're in sysadmin, it always
works.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"Tony Murray" <TonyMurray@.discussions.microsoft.com> wrote in message
news:209BE0C0-C948-4AE6-886E-F87A76AC3823@.microsoft.com...
Thanks Tom, you were spot-on :-) I had highlighted the ProjectServer
database in the left hand pane of Query Analyzer, but had not specified it
in
the drop down list in the right pane.
Tony
"Tom Moreau" wrote:

> It appears that you created the proc in the wrong database. Likely, you
> put
> it in master.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> ..
> "Tony Murray" <TonyMurray@.discussions.microsoft.com> wrote in message
> news:1530354A-94BA-4F8C-B1E7-F31980B603A9@.microsoft.com...
> I'm hoping you can help with something.
> I've installed the Project Server post SP1 Hotfix in my test lab and all
> looks ok, apart from some errors when I execute the websps.sql query file
> that forms part of the hotfix. The errors look like this.
> There is no such user or group 'MSProjectServerRole'.
> Here's an example of one of the entries in the query file that generates
> the
> error.
> /* Query #65005 */
> CREATE PROCEDURE dbo.MSP_WEB_SP_QRY_GetNotificationAdminInfo
> AS
> select WADMIN_SMTP_SERVER_NAME,
> WADMIN_SMTP_SERVER_PORT,
> WADMIN_DEFAULT_LANGUAGE,
> WADMIN_NTFY_FROM_EMAIL,
> WADMIN_NTFY_EMAIL_TRAILER,
> WADMIN_ORG_EMAIL_ADDRESS,
> WADMIN_NPE_LAST_RUN,
> WADMIN_NPE_NEXT_RUN,
> WADMIN_NPE_SCHEDULED_TIME,
> WADMIN_INTRANET_SERVER_URL,
> WADMIN_EXTRANET_SERVER_URL,
> WADMIN_EMAIL_CHARSET
> from MSP_WEB_ADMIN
> RETURN
> GO
> GRANT EXECUTE ON dbo.MSP_WEB_SP_QRY_GetNotificationAdminInfo TO
> MSProjectServerRole
> GO
> ********************************
> I've checked that the MSProjectServerRole exists and is populated with
> MSProjectServerUser, so all looks ok. I'm confused as to why the
> execution
> of the stored procedure comes up with the error. The CREATE PROCEDURE
> part
> doesn't appear to work as the stored procedure
> MSP_WEB_SP_QRY_GetNotificationAdminInfo does not appear in Enterprise
> Manager
> after the query file has finished executing.
> Not being a SQL guy, can anyone give me a pointer as to how I can
> troubleshoot this problem? I'm executing the query file as sa, so I don't
> think this is a permissions thing.
> Thanks
> Tony
>

Problem with SQL Query file

I'm hoping you can help with something.
I've installed the Project Server post SP1 Hotfix in my test lab and all
looks ok, apart from some errors when I execute the websps.sql query file
that forms part of the hotfix. The errors look like this.
There is no such user or group 'MSProjectServerRole'.
Here's an example of one of the entries in the query file that generates the
error.
/* Query #65005 */
CREATE PROCEDURE dbo.MSP_WEB_SP_QRY_GetNotificationAdminInfo
AS
select WADMIN_SMTP_SERVER_NAME,
WADMIN_SMTP_SERVER_PORT,
WADMIN_DEFAULT_LANGUAGE,
WADMIN_NTFY_FROM_EMAIL,
WADMIN_NTFY_EMAIL_TRAILER,
WADMIN_ORG_EMAIL_ADDRESS,
WADMIN_NPE_LAST_RUN,
WADMIN_NPE_NEXT_RUN,
WADMIN_NPE_SCHEDULED_TIME,
WADMIN_INTRANET_SERVER_URL,
WADMIN_EXTRANET_SERVER_URL,
WADMIN_EMAIL_CHARSET
from MSP_WEB_ADMIN
RETURN
GO
GRANT EXECUTE ON dbo.MSP_WEB_SP_QRY_GetNotificationAdminInfo TO
MSProjectServerRole
GO
********************************
I've checked that the MSProjectServerRole exists and is populated with
MSProjectServerUser, so all looks ok. I'm confused as to why the execution
of the stored procedure comes up with the error. The CREATE PROCEDURE part
doesn't appear to work as the stored procedure
MSP_WEB_SP_QRY_GetNotificationAdminInfo does not appear in Enterprise Manager
after the query file has finished executing.
Not being a SQL guy, can anyone give me a pointer as to how I can
troubleshoot this problem? I'm executing the query file as sa, so I don't
think this is a permissions thing.
Thanks
TonyIt appears that you created the proc in the wrong database. Likely, you put
it in master.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"Tony Murray" <TonyMurray@.discussions.microsoft.com> wrote in message
news:1530354A-94BA-4F8C-B1E7-F31980B603A9@.microsoft.com...
I'm hoping you can help with something.
I've installed the Project Server post SP1 Hotfix in my test lab and all
looks ok, apart from some errors when I execute the websps.sql query file
that forms part of the hotfix. The errors look like this.
There is no such user or group 'MSProjectServerRole'.
Here's an example of one of the entries in the query file that generates the
error.
/* Query #65005 */
CREATE PROCEDURE dbo.MSP_WEB_SP_QRY_GetNotificationAdminInfo
AS
select WADMIN_SMTP_SERVER_NAME,
WADMIN_SMTP_SERVER_PORT,
WADMIN_DEFAULT_LANGUAGE,
WADMIN_NTFY_FROM_EMAIL,
WADMIN_NTFY_EMAIL_TRAILER,
WADMIN_ORG_EMAIL_ADDRESS,
WADMIN_NPE_LAST_RUN,
WADMIN_NPE_NEXT_RUN,
WADMIN_NPE_SCHEDULED_TIME,
WADMIN_INTRANET_SERVER_URL,
WADMIN_EXTRANET_SERVER_URL,
WADMIN_EMAIL_CHARSET
from MSP_WEB_ADMIN
RETURN
GO
GRANT EXECUTE ON dbo.MSP_WEB_SP_QRY_GetNotificationAdminInfo TO
MSProjectServerRole
GO
********************************
I've checked that the MSProjectServerRole exists and is populated with
MSProjectServerUser, so all looks ok. I'm confused as to why the execution
of the stored procedure comes up with the error. The CREATE PROCEDURE part
doesn't appear to work as the stored procedure
MSP_WEB_SP_QRY_GetNotificationAdminInfo does not appear in Enterprise
Manager
after the query file has finished executing.
Not being a SQL guy, can anyone give me a pointer as to how I can
troubleshoot this problem? I'm executing the query file as sa, so I don't
think this is a permissions thing.
Thanks
Tony|||Thanks Tom, you were spot-on :-) I had highlighted the ProjectServer
database in the left hand pane of Query Analyzer, but had not specified it in
the drop down list in the right pane.
Tony
"Tom Moreau" wrote:
> It appears that you created the proc in the wrong database. Likely, you put
> it in master.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> ..
> "Tony Murray" <TonyMurray@.discussions.microsoft.com> wrote in message
> news:1530354A-94BA-4F8C-B1E7-F31980B603A9@.microsoft.com...
> I'm hoping you can help with something.
> I've installed the Project Server post SP1 Hotfix in my test lab and all
> looks ok, apart from some errors when I execute the websps.sql query file
> that forms part of the hotfix. The errors look like this.
> There is no such user or group 'MSProjectServerRole'.
> Here's an example of one of the entries in the query file that generates the
> error.
> /* Query #65005 */
> CREATE PROCEDURE dbo.MSP_WEB_SP_QRY_GetNotificationAdminInfo
> AS
> select WADMIN_SMTP_SERVER_NAME,
> WADMIN_SMTP_SERVER_PORT,
> WADMIN_DEFAULT_LANGUAGE,
> WADMIN_NTFY_FROM_EMAIL,
> WADMIN_NTFY_EMAIL_TRAILER,
> WADMIN_ORG_EMAIL_ADDRESS,
> WADMIN_NPE_LAST_RUN,
> WADMIN_NPE_NEXT_RUN,
> WADMIN_NPE_SCHEDULED_TIME,
> WADMIN_INTRANET_SERVER_URL,
> WADMIN_EXTRANET_SERVER_URL,
> WADMIN_EMAIL_CHARSET
> from MSP_WEB_ADMIN
> RETURN
> GO
> GRANT EXECUTE ON dbo.MSP_WEB_SP_QRY_GetNotificationAdminInfo TO
> MSProjectServerRole
> GO
> ********************************
> I've checked that the MSProjectServerRole exists and is populated with
> MSProjectServerUser, so all looks ok. I'm confused as to why the execution
> of the stored procedure comes up with the error. The CREATE PROCEDURE part
> doesn't appear to work as the stored procedure
> MSP_WEB_SP_QRY_GetNotificationAdminInfo does not appear in Enterprise
> Manager
> after the query file has finished executing.
> Not being a SQL guy, can anyone give me a pointer as to how I can
> troubleshoot this problem? I'm executing the query file as sa, so I don't
> think this is a permissions thing.
> Thanks
> Tony
>|||It's a common problem with DBA's. We usually belong to the sysadmin role
and have a default DB of master. If you include a USE statement, that can
fend off the wrong DB problem. Any object you create should also have the
appropriate GRANT statements, too. When you're in sysadmin, it always
works.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"Tony Murray" <TonyMurray@.discussions.microsoft.com> wrote in message
news:209BE0C0-C948-4AE6-886E-F87A76AC3823@.microsoft.com...
Thanks Tom, you were spot-on :-) I had highlighted the ProjectServer
database in the left hand pane of Query Analyzer, but had not specified it
in
the drop down list in the right pane.
Tony
"Tom Moreau" wrote:
> It appears that you created the proc in the wrong database. Likely, you
> put
> it in master.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> ..
> "Tony Murray" <TonyMurray@.discussions.microsoft.com> wrote in message
> news:1530354A-94BA-4F8C-B1E7-F31980B603A9@.microsoft.com...
> I'm hoping you can help with something.
> I've installed the Project Server post SP1 Hotfix in my test lab and all
> looks ok, apart from some errors when I execute the websps.sql query file
> that forms part of the hotfix. The errors look like this.
> There is no such user or group 'MSProjectServerRole'.
> Here's an example of one of the entries in the query file that generates
> the
> error.
> /* Query #65005 */
> CREATE PROCEDURE dbo.MSP_WEB_SP_QRY_GetNotificationAdminInfo
> AS
> select WADMIN_SMTP_SERVER_NAME,
> WADMIN_SMTP_SERVER_PORT,
> WADMIN_DEFAULT_LANGUAGE,
> WADMIN_NTFY_FROM_EMAIL,
> WADMIN_NTFY_EMAIL_TRAILER,
> WADMIN_ORG_EMAIL_ADDRESS,
> WADMIN_NPE_LAST_RUN,
> WADMIN_NPE_NEXT_RUN,
> WADMIN_NPE_SCHEDULED_TIME,
> WADMIN_INTRANET_SERVER_URL,
> WADMIN_EXTRANET_SERVER_URL,
> WADMIN_EMAIL_CHARSET
> from MSP_WEB_ADMIN
> RETURN
> GO
> GRANT EXECUTE ON dbo.MSP_WEB_SP_QRY_GetNotificationAdminInfo TO
> MSProjectServerRole
> GO
> ********************************
> I've checked that the MSProjectServerRole exists and is populated with
> MSProjectServerUser, so all looks ok. I'm confused as to why the
> execution
> of the stored procedure comes up with the error. The CREATE PROCEDURE
> part
> doesn't appear to work as the stored procedure
> MSP_WEB_SP_QRY_GetNotificationAdminInfo does not appear in Enterprise
> Manager
> after the query file has finished executing.
> Not being a SQL guy, can anyone give me a pointer as to how I can
> troubleshoot this problem? I'm executing the query file as sa, so I don't
> think this is a permissions thing.
> Thanks
> Tony
>

Problem with SQL 2005 Beta 2 Reporting Services

I've just installed SQL 2005 Beta 2 onto a Windows Server 2003 SP1 box.
I've installed all the components, including Reporting Services.
When I try to connect to the web site I get the message
The request failed with HTTP status 407: Proxy Authentication Required.
Anonymous access to the web site is allowed.
Any thoughts?
Thanks
Laurence
--
Laurence Sharp
Senior Systems Engineer
TNS UKOn Thu, 7 Apr 2005 07:09:05 -0700, "Laurence Sharp"
<LaurenceSharp@.discussions.microsoft.com> wrote:
>I've just installed SQL 2005 Beta 2 onto a Windows Server 2003 SP1 box.
>I've installed all the components, including Reporting Services.
>When I try to connect to the web site I get the message
>The request failed with HTTP status 407: Proxy Authentication Required.
>Anonymous access to the web site is allowed.
>Any thoughts?
>Thanks
>Laurence
Hi Laurence,
Questions about RS2005 should probably go to the
microsoft.private.sqlserver2005.reportingsvcs. Despite the name it's a
public newsgroup intended for the RS2005 beta and CTPs.
Are you really using Beta 2 from June/July last year? Beta 2 has
functionality similar to RS2000 with little new.
If you are, then you should probably update BUT be sure to read
carefully CTPNotes.mht about uninstall order before upgrading.
The February CTP has new functionality and has fewer configuration
problems than earlier builds.
Andrew Watt
MVP - InfoPath

Problem with SQL 2000 Reporting Services in Windows Server 2000 IIS 5.0

Hi,

I′m having a problem with the SQL 2000 Reporting Services.
I′ve installed it in a windows 2000 server with IIS 5.0 and after i′ve installed the Reporting Services (even with the SP2 os Reporting Services installed), when i try to log on to the reports webside in order to start creating the folders of the reports that i want to create i get an error (ACCESS DENIED) and i′m trying to access it locally.

How can i solve this?

Regards,

Ricardo

Are you trying to open the website on the installed server or via another computer ?

HTH, Jens SUessmeyer.

http://www.sqlserver2005.de

|||Hi,

I′m trying to open the website on the instaled server. Even if i try to open it from a diferent computer, the error is the same.|||

Try using the rskeymgmt utility to backup the encryption key, and rsactivate utility to activate the site.

Check to see if the Default Application Pool in IIS is using the Network account identity.

Filemon from www.sysinternals.com may also help identify where the issue is.

cheers,

Andrew

|||Do you get an rsAccessDenied or the IIS Access Denied ?

HTH, Jens SUessmeyer.

http://www.sqlserver2005.de

Problem with SQL (Job cannot run, Job status not updated)

Hi All,

I would need your help please.

I just installed a new fresh SQL server under Windows 2000 Advanced server SP 4

1. Firstly i tried to run normal database backup to a folder by select backup database then run manually and it ran very well. Then i tried to run it with schedule as sql backup job to the same folder. After the job was showed in the sql jobs list, i tried to run it manually by clicking start job. When i refresh the screen under the status field it says "executing job step '0 (unknown)" then in about 5 seconds the status turned into "not running". And i cannot find any error in the log and in the last run job status. The SQLSERVERAGENT is running, the strange thing is another job which is only to update the database can run with the scheduler very well.

2. Whenever i run job then after it finished the last run job status is always unknown.

What will be the solution for the conditions above, please help (

Thank you very much in advance

Best Regards

Felix

Just restart the sql server agent and see......may be the agent might have been in hanged state.........but i am not sure about it.....|||

Hi deepak,

Thank you very much

I can only try the solution tomorrow morning, just to make sure.

I have tried to run another jobs which is not backup job by using sqlserveragent as well and its working well.

So with this information perhaps you have other opinition please let me know.

I will let you know how it goes tomorrow morning, wish me luck

many thanks

Felix

sql

Problem with sp2... bug?

After I've installed the sql server 2005 sp2, some reports have a strange
behaviour. For example
In some case the Inscope function in a matrix, in the subtotal column,
returns different result (between sp1 and sp2)
And if I calcuted sum(field!FieldName,"row_matrix") in the subtotal column
(using the inscope function) , in some case it do the sum of the column.
I think that the two stange behaviour are correlateOn Apr 20, 10:45 am, "abc_abc" <e...@.phones.it> wrote:
> After I've installed the sql server 2005 sp2, some reports have a strange
> behaviour. For example
> In some case theInscope function in a matrix, in the subtotal column,
> returns different result (between sp1 and sp2)
> And if I calcuted sum(field!FieldName,"row_matrix") in the subtotal column
> (using theinscopefunction) , in some case it do the sum of the column.
> I think that the two stange behaviour are correlate
We just ran across this today too. The Inscope function evaluates
differently depending on where its being evaluated.|||Allen M ha scritto:
> On Apr 20, 10:45 am, "abc_abc" <e...@.phones.it> wrote:
> > After I've installed the sql server 2005 sp2, some reports have a strange
> > behaviour. For example
> >
> > In some case theInscope function in a matrix, in the subtotal column,
> > returns different result (between sp1 and sp2)
> > And if I calcuted sum(field!FieldName,"row_matrix") in the subtotal column
> > (using theinscopefunction) , in some case it do the sum of the column.
> > I think that the two stange behaviour are correlate
> We just ran across this today too. The Inscope function evaluates
> differently depending on where its being evaluated.
I also have the same problem.
is it a bug of SP2 ?
Alessio|||On May 17, 1:26 am, mxl...@.tiscali.it wrote:
> Allen M ha scritto:
> > On Apr 20, 10:45 am, "abc_abc" <e...@.phones.it> wrote:
> > > After I've installed the sql server 2005 sp2, some reports have a strange
> > > behaviour. For example
> > > In some case theInscope function in a matrix, in the subtotal column,
> > > returns different result (between sp1 and sp2)
> > > And if I calcuted sum(field!FieldName,"row_matrix") in the subtotal column
> > > (using theinscopefunction) , in some case it do the sum of the column.
> > > I think that the two stange behaviour are correlate
> > We just ran across this today too. TheInscopefunction evaluates
> > differently depending on where its being evaluated.
> I also have the same problem.
> is it abugof SP2 ?
> Alessio
Have either of you found anything on this?sql

Problem with Service Principle Name after new install

Hi all,
I installed a SQL Server 2000 on a Win2003 machine, running the SQL Server
service under a domain user account.
When the SQL Server starts, I find a warning in the event log:
Source: MSSQLServer EventID: 19011
Description: SuperSocket info: (SpnRegister) : Error 8344.
After reading several KB articles I understand that the service account
tries to register the Service Principle Name on startup and fails because it
does not have the rights the register the SPN in Active Directory.
I put the account in the local admin group on the server and created a SPN
with setspn.exe from Win2000 resource kit, which points to at the domain
account. Does not fix the warning message.
I do not want to put the account into domain admin group, which would fix
the problem I think, because domain admins have all permissions to register
the SPN.
Does someone have a hint for me?
Thanks in advance
Regards
Christian
If your server should always work using same tcp port, you may ignore this
message.
If server works under LocalSystem or other account which has such
permissions (by default - only Domain Admins), he registers SPN at startup
and unregisters at shutdown. So in your case if you change tcp/ip settings
for server, you will have to reregister SPN manually. Or you may give such
rights to service account - see this article for permissions info:
http://technet2.microsoft.com/Window...e47441033.mspx
WBR, Evergray
Words mean nothing...
"Christian Guntsche" <christian.guntsche@.docuware.com> wrote in message
news:OxLkQH1RGHA.1688@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I installed a SQL Server 2000 on a Win2003 machine, running the SQL Server
> service under a domain user account.
> When the SQL Server starts, I find a warning in the event log:
> Source: MSSQLServer EventID: 19011
> Description: SuperSocket info: (SpnRegister) : Error 8344.
> After reading several KB articles I understand that the service account
> tries to register the Service Principle Name on startup and fails because
> it does not have the rights the register the SPN in Active Directory.
> I put the account in the local admin group on the server and created a SPN
> with setspn.exe from Win2000 resource kit, which points to at the domain
> account. Does not fix the warning message.
> I do not want to put the account into domain admin group, which would fix
> the problem I think, because domain admins have all permissions to
> register the SPN.
> Does someone have a hint for me?
> Thanks in advance
> Regards
> Christian
>
|||Thanks for reply,
at least you pointed us in the right direction.
I read the article, but again MS describes not which rights an account needs
in order to register the SPN at startup. All information you get is, that it
works with domain admin rights and with local system.
Nonetheless, the information, that a special function is executed in Active
Directory let us search through the Advanced Active Directory permission
settings and we found that giving the permission to "write public
information" to the SQL Service Account solves the problem.
This prevents us from assigning domain admin rights.
Strange, that Microsoft does not point out which specific permissions have
to be set for a normal user account, but in the other tells you to not use a
admin account.
Anyway this is solved for us.
Regards
Christian
"Oleksandr Chuchko" <forlists@.mail.ru> schrieb im Newsbeitrag
news:%23JIEvO5RGHA.5036@.TK2MSFTNGP12.phx.gbl...
> If your server should always work using same tcp port, you may ignore this
> message.
> If server works under LocalSystem or other account which has such
> permissions (by default - only Domain Admins), he registers SPN at startup
> and unregisters at shutdown. So in your case if you change tcp/ip settings
> for server, you will have to reregister SPN manually. Or you may give such
> rights to service account - see this article for permissions info:
> http://technet2.microsoft.com/Window...e47441033.mspx
> --
> WBR, Evergray
> --
> Words mean nothing...
>
> "Christian Guntsche" <christian.guntsche@.docuware.com> wrote in message
> news:OxLkQH1RGHA.1688@.TK2MSFTNGP11.phx.gbl...
>

Problem with Service Principle Name after new install

Hi all,
I installed a SQL Server 2000 on a Win2003 machine, running the SQL Server
service under a domain user account.
When the SQL Server starts, I find a warning in the event log:
Source: MSSQLServer EventID: 19011
Description: SuperSocket info: (SpnRegister) : Error 8344.
After reading several KB articles I understand that the service account
tries to register the Service Principle Name on startup and fails because it
does not have the rights the register the SPN in Active Directory.
I put the account in the local admin group on the server and created a SPN
with setspn.exe from Win2000 resource kit, which points to at the domain
account. Does not fix the warning message.
I do not want to put the account into domain admin group, which would fix
the problem I think, because domain admins have all permissions to register
the SPN.
Does someone have a hint for me?
Thanks in advance
Regards
ChristianIf your server should always work using same tcp port, you may ignore this
message.
If server works under LocalSystem or other account which has such
permissions (by default - only Domain Admins), he registers SPN at startup
and unregisters at shutdown. So in your case if you change tcp/ip settings
for server, you will have to reregister SPN manually. Or you may give such
rights to service account - see this article for permissions info:
http://technet2.microsoft.com/Windo...de47441033.mspx
WBR, Evergray
--
Words mean nothing...
"Christian Guntsche" <christian.guntsche@.docuware.com> wrote in message
news:OxLkQH1RGHA.1688@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I installed a SQL Server 2000 on a Win2003 machine, running the SQL Server
> service under a domain user account.
> When the SQL Server starts, I find a warning in the event log:
> Source: MSSQLServer EventID: 19011
> Description: SuperSocket info: (SpnRegister) : Error 8344.
> After reading several KB articles I understand that the service account
> tries to register the Service Principle Name on startup and fails because
> it does not have the rights the register the SPN in Active Directory.
> I put the account in the local admin group on the server and created a SPN
> with setspn.exe from Win2000 resource kit, which points to at the domain
> account. Does not fix the warning message.
> I do not want to put the account into domain admin group, which would fix
> the problem I think, because domain admins have all permissions to
> register the SPN.
> Does someone have a hint for me?
> Thanks in advance
> Regards
> Christian
>|||Thanks for reply,
at least you pointed us in the right direction.
I read the article, but again MS describes not which rights an account needs
in order to register the SPN at startup. All information you get is, that it
works with domain admin rights and with local system.
Nonetheless, the information, that a special function is executed in Active
Directory let us search through the Advanced Active Directory permission
settings and we found that giving the permission to "write public
information" to the SQL Service Account solves the problem.
This prevents us from assigning domain admin rights.
Strange, that Microsoft does not point out which specific permissions have
to be set for a normal user account, but in the other tells you to not use a
admin account.
Anyway this is solved for us.
Regards
Christian
"Oleksandr Chuchko" <forlists@.mail.ru> schrieb im Newsbeitrag
news:%23JIEvO5RGHA.5036@.TK2MSFTNGP12.phx.gbl...
> If your server should always work using same tcp port, you may ignore this
> message.
> If server works under LocalSystem or other account which has such
> permissions (by default - only Domain Admins), he registers SPN at startup
> and unregisters at shutdown. So in your case if you change tcp/ip settings
> for server, you will have to reregister SPN manually. Or you may give such
> rights to service account - see this article for permissions info:
> http://technet2.microsoft.com/Windo...de47441033.mspx
> --
> WBR, Evergray
> --
> Words mean nothing...
>
> "Christian Guntsche" <christian.guntsche@.docuware.com> wrote in message
> news:OxLkQH1RGHA.1688@.TK2MSFTNGP11.phx.gbl...
>sql

Problem with Service Principle Name after new install

Hi all,
I installed a SQL Server 2000 on a Win2003 machine, running the SQL Server
service under a domain user account.
When the SQL Server starts, I find a warning in the event log:
Source: MSSQLServer EventID: 19011
Description: SuperSocket info: (SpnRegister) : Error 8344.
After reading several KB articles I understand that the service account
tries to register the Service Principle Name on startup and fails because it
does not have the rights the register the SPN in Active Directory.
I put the account in the local admin group on the server and created a SPN
with setspn.exe from Win2000 resource kit, which points to at the domain
account. Does not fix the warning message.
I do not want to put the account into domain admin group, which would fix
the problem I think, because domain admins have all permissions to register
the SPN.
Does someone have a hint for me?
Thanks in advance
Regards
ChristianIf your server should always work using same tcp port, you may ignore this
message.
If server works under LocalSystem or other account which has such
permissions (by default - only Domain Admins), he registers SPN at startup
and unregisters at shutdown. So in your case if you change tcp/ip settings
for server, you will have to reregister SPN manually. Or you may give such
rights to service account - see this article for permissions info:
http://technet2.microsoft.com/WindowsServer/en/Library/8127f5ed-4e05-4822-bfa9-402ceede47441033.mspx
--
WBR, Evergray
--
Words mean nothing...
"Christian Guntsche" <christian.guntsche@.docuware.com> wrote in message
news:OxLkQH1RGHA.1688@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I installed a SQL Server 2000 on a Win2003 machine, running the SQL Server
> service under a domain user account.
> When the SQL Server starts, I find a warning in the event log:
> Source: MSSQLServer EventID: 19011
> Description: SuperSocket info: (SpnRegister) : Error 8344.
> After reading several KB articles I understand that the service account
> tries to register the Service Principle Name on startup and fails because
> it does not have the rights the register the SPN in Active Directory.
> I put the account in the local admin group on the server and created a SPN
> with setspn.exe from Win2000 resource kit, which points to at the domain
> account. Does not fix the warning message.
> I do not want to put the account into domain admin group, which would fix
> the problem I think, because domain admins have all permissions to
> register the SPN.
> Does someone have a hint for me?
> Thanks in advance
> Regards
> Christian
>|||Thanks for reply,
at least you pointed us in the right direction. :)
I read the article, but again MS describes not which rights an account needs
in order to register the SPN at startup. All information you get is, that it
works with domain admin rights and with local system.
Nonetheless, the information, that a special function is executed in Active
Directory let us search through the Advanced Active Directory permission
settings and we found that giving the permission to "write public
information" to the SQL Service Account solves the problem.
This prevents us from assigning domain admin rights.
Strange, that Microsoft does not point out which specific permissions have
to be set for a normal user account, but in the other tells you to not use a
admin account.
Anyway this is solved for us.
Regards
Christian
"Oleksandr Chuchko" <forlists@.mail.ru> schrieb im Newsbeitrag
news:%23JIEvO5RGHA.5036@.TK2MSFTNGP12.phx.gbl...
> If your server should always work using same tcp port, you may ignore this
> message.
> If server works under LocalSystem or other account which has such
> permissions (by default - only Domain Admins), he registers SPN at startup
> and unregisters at shutdown. So in your case if you change tcp/ip settings
> for server, you will have to reregister SPN manually. Or you may give such
> rights to service account - see this article for permissions info:
> http://technet2.microsoft.com/WindowsServer/en/Library/8127f5ed-4e05-4822-bfa9-402ceede47441033.mspx
> --
> WBR, Evergray
> --
> Words mean nothing...
>
> "Christian Guntsche" <christian.guntsche@.docuware.com> wrote in message
> news:OxLkQH1RGHA.1688@.TK2MSFTNGP11.phx.gbl...
>> Hi all,
>> I installed a SQL Server 2000 on a Win2003 machine, running the SQL
>> Server service under a domain user account.
>> When the SQL Server starts, I find a warning in the event log:
>> Source: MSSQLServer EventID: 19011
>> Description: SuperSocket info: (SpnRegister) : Error 8344.
>> After reading several KB articles I understand that the service account
>> tries to register the Service Principle Name on startup and fails because
>> it does not have the rights the register the SPN in Active Directory.
>> I put the account in the local admin group on the server and created a
>> SPN with setspn.exe from Win2000 resource kit, which points to at the
>> domain account. Does not fix the warning message.
>> I do not want to put the account into domain admin group, which would fix
>> the problem I think, because domain admins have all permissions to
>> register the SPN.
>> Does someone have a hint for me?
>> Thanks in advance
>> Regards
>> Christian
>

Problem with service of the SQL server 2005

Hello, I have a problem: I accede to the SQL server 2005 having installed the SQL server locally but it does not allow me to initiate, to stop nor to reinitiate the service, that only happens to my user, however with another one if it allows. the network is with work group, that podria to be? thanks for its attentionYou need to log in to your computer as a member of the Windows Administrators group to start or stop the SQL Server service. When you are logged in as an administrator, you can use the SQL Server Configuration Manager tool to start and stop the service or change service startup properties.

problem with Server Management Studio Express and diagrames

so I have had a database in Sql Server 2000, in my DB i have made database diagrams.

now I have installed on other PC(where does't install sql 2000) Sql Server Management Studio Express where I have opened my db , bat db diagrams does't work.

what can I do? how can I solve this problem?

enyone can explain me?

thanks.

Management Studio can't open SQL 2000 diagrams, if you click on the diagrams branch of the tree it should ask if you want to install diagram support, once this is done you can create new diagrams.|||ok, bat when I opend diagrams branch of the tree, it doesn't ask if I want or not to install diagram|||

hi,

usually you have to first import the database to the new SQL Server 2005 instance (as you already did)..

then modify the compatibility level to 90 via the SSMSE, database properties (options tab), and finally set the database owner to a valid principal, again SSMSE, database properties (files tab, "owner" peroperty )...

then you should be able to access database diagrams..

regards

Problem with sample databases

I have installed SQL Express 2005 together with VS 2005. After a while I found out that the sample databases (Northwind and Pubs) were missing, so I installed them. According to the 'Readme', which comes with the installation I could choose between attaching the db to the Server or running a SQL script.

Neither works. I've read this link about remote connections (http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx). My development machine is just a local single computer and I still get this error message:

'An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact under the default settings SQL Server does not allow remote connections.'

I' ve opened TCP/IP and Named Pipes and I get the same result when trying to connect from the Server Explorer in VS.

Thanks for your help.

Hey,

SQL Server 2005 doesn't install with the sample databases anymore; I am having training on it, and that is what I just found out. Also, to setup remote connections, you can do so in the SQL Server Surface Area Configuration.

Brian

|||

Hey,

TCP/IP and Named Pipes are only selectable if you allow remote connections in the SQL Server Surface Area Configuration.

RTFT.

Anybody else coming up with an idea?

Problem with Reporting Services 2005

I installed SQL SERVER 2005 with RS2005 - it worked great.
Cause of a problem we had to re-installed the IIS so the virtual directories
of RS where gone...
To continue with errors i deleted the DB of RS
So now i try to re-install the RS but i get this error:
Reason: Your upgrade is blocked. For more information about upgrade support,
see the "Version and Edition Upgrades" and "Hardware and Software
Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books
Online.
Build version check:
Your upgrade is blocked because the existing component is a later version
than the version you are trying to upgrade to. To modify an existing SQL
Server component, go to Add or Remove Programs in Control Panel, select the
component you would like to modify, and then click Change/Remove.
So what should i do?when i try to it from Add/Remove it also don't work...
My version is :
Microsoft SQL Server Management Studio 9.00.2047.00
But when it try to install the RS it say : 9.1.2047.00
So what's the problem?Can you just try recreating the virtual directories and the databases using
Reporting services configuration manager instead of a complete reinstall?
--
Ramu
This posting is provided "AS IS" with no warranties, and confers no rights.
"ש×?×?×?" wrote:
> I installed SQL SERVER 2005 with RS2005 - it worked great.
> Cause of a problem we had to re-installed the IIS so the virtual directories
> of RS where gone...
> To continue with errors i deleted the DB of RS
> So now i try to re-install the RS but i get this error:
> Reason: Your upgrade is blocked. For more information about upgrade support,
> see the "Version and Edition Upgrades" and "Hardware and Software
> Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books
> Online.
> Build version check:
> Your upgrade is blocked because the existing component is a later version
> than the version you are trying to upgrade to. To modify an existing SQL
> Server component, go to Add or Remove Programs in Control Panel, select the
> component you would like to modify, and then click Change/Remove.
>
> So what should i do?when i try to it from Add/Remove it also don't work...
> My version is :
> Microsoft SQL Server Management Studio 9.00.2047.00
> But when it try to install the RS it say : 9.1.2047.00
> So what's the problem?
>|||thanks,it helped
what amazing tool!!!
"Ramu_MSFT" wrote:
> Can you just try recreating the virtual directories and the databases using
> Reporting services configuration manager instead of a complete reinstall?
> --
> Ramu
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "ש×?×?×?" wrote:
> > I installed SQL SERVER 2005 with RS2005 - it worked great.
> > Cause of a problem we had to re-installed the IIS so the virtual directories
> > of RS where gone...
> > To continue with errors i deleted the DB of RS
> > So now i try to re-install the RS but i get this error:
> >
> > Reason: Your upgrade is blocked. For more information about upgrade support,
> > see the "Version and Edition Upgrades" and "Hardware and Software
> > Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books
> > Online.
> >
> > Build version check:
> > Your upgrade is blocked because the existing component is a later version
> > than the version you are trying to upgrade to. To modify an existing SQL
> > Server component, go to Add or Remove Programs in Control Panel, select the
> > component you would like to modify, and then click Change/Remove.
> >
> >
> > So what should i do?when i try to it from Add/Remove it also don't work...
> >
> > My version is :
> > Microsoft SQL Server Management Studio 9.00.2047.00
> > But when it try to install the RS it say : 9.1.2047.00
> >
> > So what's the problem?
> >

Problem with Report Services Integration in MOSS 2007

Specifics:
First machine: SharePoint single server Farm
Second machine: SQL 2005 with Report Services
Installed SP2 and RS Add-in, added SQL pc to farm, and followed steps to set
up integration, including changing SQL service accounts to domain accounts.
Everything went smoothly until we clicked on â'Set Server Defaultsâ' under
Reporting Services in SharePoint Central Admin and we got an error message:
An unexpected error occurred while connecting to the report server. Verify
that the report server is available and configured for SharePoint integrated
mode. --> Server was unable to process request. --> The request failed with
HTTP status 401: Unauthorized.
Nothing in the Event Log on the MOSS server but on the SQL server there is
an Event ID 529 â' unknown user name or bad password. This error message also
shows that the Logon Process and the Authentication Package are Kerberos.
We have beaten our heads against the wall trying to solve. Any help would be
appreciated.Did you check your Service Accounts in IIS and the Reporting Services setup
in SQL server. We had the same issue and it turned out to be we had missed
some of the accounts in Central Admin and IIS.
"AlisonZ" wrote:
> Specifics:
> First machine: SharePoint single server Farm
> Second machine: SQL 2005 with Report Services
> Installed SP2 and RS Add-in, added SQL pc to farm, and followed steps to set
> up integration, including changing SQL service accounts to domain accounts.
> Everything went smoothly until we clicked on â'Set Server Defaultsâ' under
> Reporting Services in SharePoint Central Admin and we got an error message:
> An unexpected error occurred while connecting to the report server. Verify
> that the report server is available and configured for SharePoint integrated
> mode. --> Server was unable to process request. --> The request failed with
> HTTP status 401: Unauthorized.
> Nothing in the Event Log on the MOSS server but on the SQL server there is
> an Event ID 529 â' unknown user name or bad password. This error message also
> shows that the Logon Process and the Authentication Package are Kerberos.
> We have beaten our heads against the wall trying to solve. Any help would be
> appreciated.
>