Wednesday, March 7, 2012
Assessing needs to install one more SQL server for MOM
the scenario, please let me know if I have justification to buy a SQL server
license to install MOM on local computer or I can use this on my MainSQL
server instead:
a) I need to configure such SQL server for MOM and MOM best practices
require to allow only "Windows authentication". I have virtually dozens of
third-party applications that rely on that SQL server and I do not know if
by changing configuration to "Windows authentication only" to satisfy MOM
setup that could eventually break something down the road.
b) I have to enable IIS on such SQL server box. CUrrently MainSQL server has
no IIS enabled. That would be just a security issue, but I guess so many
applications require to have IIS installed these days...
Do you think the above is enough to make me buy a SQL server license
dedicated for MOM ?And a poster kindly reminded that instances would do work here and allow me
to configure the "Windows authentication only". From reading the SQL help
files, I see that instances are generally not recommended for SQL-production
environment (this is my case here, I will be using MOM in production
environment).
If you have any input on how SQL instances are doing in real world, please
let me know.
"Marlon Brown" <marlon_brown@.hotmail.com> wrote in message
news:eBkAAqU4EHA.708@.TK2MSFTNGP11.phx.gbl...
>I am trying to avoid installing more SQL servers than what I need. This is
> the scenario, please let me know if I have justification to buy a SQL
> server
> license to install MOM on local computer or I can use this on my MainSQL
> server instead:
> a) I need to configure such SQL server for MOM and MOM best practices
> require to allow only "Windows authentication". I have virtually dozens of
> third-party applications that rely on that SQL server and I do not know if
> by changing configuration to "Windows authentication only" to satisfy MOM
> setup that could eventually break something down the road.
> b) I have to enable IIS on such SQL server box. CUrrently MainSQL server
> has
> no IIS enabled. That would be just a security issue, but I guess so many
> applications require to have IIS installed these days...
> Do you think the above is enough to make me buy a SQL server license
> dedicated for MOM ?
>|||They are harder to manage because now you have two sets of executibles that
must be serviced and could be corrupted by OS fixes including two sets of
perf counters, etc., etc., etc.
I'd consider running MOM on another server that's less used. You should
never run the monitoring process on the item that you are monitoring. You
will affect the outcomes of those observations. Your management pieces
should always be on another host and do their monitoring remotely.
Sincerely,
Anthony Thomas
"Marlon Brown" <marlon_brownj@.hotmail.com> wrote in message
news:%230%23r8eY4EHA.2196@.TK2MSFTNGP14.phx.gbl...
And a poster kindly reminded that instances would do work here and allow me
to configure the "Windows authentication only". From reading the SQL help
files, I see that instances are generally not recommended for SQL-production
environment (this is my case here, I will be using MOM in production
environment).
If you have any input on how SQL instances are doing in real world, please
let me know.
"Marlon Brown" <marlon_brown@.hotmail.com> wrote in message
news:eBkAAqU4EHA.708@.TK2MSFTNGP11.phx.gbl...
>I am trying to avoid installing more SQL servers than what I need. This is
> the scenario, please let me know if I have justification to buy a SQL
> server
> license to install MOM on local computer or I can use this on my MainSQL
> server instead:
> a) I need to configure such SQL server for MOM and MOM best practices
> require to allow only "Windows authentication". I have virtually dozens of
> third-party applications that rely on that SQL server and I do not know if
> by changing configuration to "Windows authentication only" to satisfy MOM
> setup that could eventually break something down the road.
> b) I have to enable IIS on such SQL server box. CUrrently MainSQL server
> has
> no IIS enabled. That would be just a security issue, but I guess so many
> applications require to have IIS installed these days...
> Do you think the above is enough to make me buy a SQL server license
> dedicated for MOM ?
>|||I agree. I will buy a SQL server license now !!!.
"AnthonyThomas" <Anthony.Thomas@.CommerceBank.com> wrote in message
news:%23frmjIe4EHA.3864@.TK2MSFTNGP15.phx.gbl...
> They are harder to manage because now you have two sets of executibles
> that
> must be serviced and could be corrupted by OS fixes including two sets of
> perf counters, etc., etc., etc.
> I'd consider running MOM on another server that's less used. You should
> never run the monitoring process on the item that you are monitoring. You
> will affect the outcomes of those observations. Your management pieces
> should always be on another host and do their monitoring remotely.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Marlon Brown" <marlon_brownj@.hotmail.com> wrote in message
> news:%230%23r8eY4EHA.2196@.TK2MSFTNGP14.phx.gbl...
> And a poster kindly reminded that instances would do work here and allow
> me
> to configure the "Windows authentication only". From reading the SQL help
> files, I see that instances are generally not recommended for
> SQL-production
> environment (this is my case here, I will be using MOM in production
> environment).
> If you have any input on how SQL instances are doing in real world, please
> let me know.
>
> "Marlon Brown" <marlon_brown@.hotmail.com> wrote in message
> news:eBkAAqU4EHA.708@.TK2MSFTNGP11.phx.gbl...
>>I am trying to avoid installing more SQL servers than what I need. This is
>> the scenario, please let me know if I have justification to buy a SQL
>> server
>> license to install MOM on local computer or I can use this on my MainSQL
>> server instead:
>> a) I need to configure such SQL server for MOM and MOM best practices
>> require to allow only "Windows authentication". I have virtually dozens
>> of
>> third-party applications that rely on that SQL server and I do not know
>> if
>> by changing configuration to "Windows authentication only" to satisfy MOM
>> setup that could eventually break something down the road.
>> b) I have to enable IIS on such SQL server box. CUrrently MainSQL server
>> has
>> no IIS enabled. That would be just a security issue, but I guess so many
>> applications require to have IIS installed these days...
>> Do you think the above is enough to make me buy a SQL server license
>> dedicated for MOM ?
>>
>
Assessing needs to install one more SQL server for MOM
the scenario, please let me know if I have justification to buy a SQL server
license to install MOM on local computer or I can use this on my MainSQL
server instead:
a) I need to configure such SQL server for MOM and MOM best practices
require to allow only "Windows authentication". I have virtually dozens of
third-party applications that rely on that SQL server and I do not know if
by changing configuration to "Windows authentication only" to satisfy MOM
setup that could eventually break something down the road.
b) I have to enable IIS on such SQL server box. CUrrently MainSQL server has
no IIS enabled. That would be just a security issue, but I guess so many
applications require to have IIS installed these days...
Do you think the above is enough to make me buy a SQL server license
dedicated for MOM ?
And a poster kindly reminded that instances would do work here and allow me
to configure the "Windows authentication only". From reading the SQL help
files, I see that instances are generally not recommended for SQL-production
environment (this is my case here, I will be using MOM in production
environment).
If you have any input on how SQL instances are doing in real world, please
let me know.
"Marlon Brown" <marlon_brown@.hotmail.com> wrote in message
news:eBkAAqU4EHA.708@.TK2MSFTNGP11.phx.gbl...
>I am trying to avoid installing more SQL servers than what I need. This is
> the scenario, please let me know if I have justification to buy a SQL
> server
> license to install MOM on local computer or I can use this on my MainSQL
> server instead:
> a) I need to configure such SQL server for MOM and MOM best practices
> require to allow only "Windows authentication". I have virtually dozens of
> third-party applications that rely on that SQL server and I do not know if
> by changing configuration to "Windows authentication only" to satisfy MOM
> setup that could eventually break something down the road.
> b) I have to enable IIS on such SQL server box. CUrrently MainSQL server
> has
> no IIS enabled. That would be just a security issue, but I guess so many
> applications require to have IIS installed these days...
> Do you think the above is enough to make me buy a SQL server license
> dedicated for MOM ?
>
|||They are harder to manage because now you have two sets of executibles that
must be serviced and could be corrupted by OS fixes including two sets of
perf counters, etc., etc., etc.
I'd consider running MOM on another server that's less used. You should
never run the monitoring process on the item that you are monitoring. You
will affect the outcomes of those observations. Your management pieces
should always be on another host and do their monitoring remotely.
Sincerely,
Anthony Thomas
"Marlon Brown" <marlon_brownj@.hotmail.com> wrote in message
news:%230%23r8eY4EHA.2196@.TK2MSFTNGP14.phx.gbl...
And a poster kindly reminded that instances would do work here and allow me
to configure the "Windows authentication only". From reading the SQL help
files, I see that instances are generally not recommended for SQL-production
environment (this is my case here, I will be using MOM in production
environment).
If you have any input on how SQL instances are doing in real world, please
let me know.
"Marlon Brown" <marlon_brown@.hotmail.com> wrote in message
news:eBkAAqU4EHA.708@.TK2MSFTNGP11.phx.gbl...
>I am trying to avoid installing more SQL servers than what I need. This is
> the scenario, please let me know if I have justification to buy a SQL
> server
> license to install MOM on local computer or I can use this on my MainSQL
> server instead:
> a) I need to configure such SQL server for MOM and MOM best practices
> require to allow only "Windows authentication". I have virtually dozens of
> third-party applications that rely on that SQL server and I do not know if
> by changing configuration to "Windows authentication only" to satisfy MOM
> setup that could eventually break something down the road.
> b) I have to enable IIS on such SQL server box. CUrrently MainSQL server
> has
> no IIS enabled. That would be just a security issue, but I guess so many
> applications require to have IIS installed these days...
> Do you think the above is enough to make me buy a SQL server license
> dedicated for MOM ?
>
|||I agree. I will buy a SQL server license now !!!.
"AnthonyThomas" <Anthony.Thomas@.CommerceBank.com> wrote in message
news:%23frmjIe4EHA.3864@.TK2MSFTNGP15.phx.gbl...
> They are harder to manage because now you have two sets of executibles
> that
> must be serviced and could be corrupted by OS fixes including two sets of
> perf counters, etc., etc., etc.
> I'd consider running MOM on another server that's less used. You should
> never run the monitoring process on the item that you are monitoring. You
> will affect the outcomes of those observations. Your management pieces
> should always be on another host and do their monitoring remotely.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Marlon Brown" <marlon_brownj@.hotmail.com> wrote in message
> news:%230%23r8eY4EHA.2196@.TK2MSFTNGP14.phx.gbl...
> And a poster kindly reminded that instances would do work here and allow
> me
> to configure the "Windows authentication only". From reading the SQL help
> files, I see that instances are generally not recommended for
> SQL-production
> environment (this is my case here, I will be using MOM in production
> environment).
> If you have any input on how SQL instances are doing in real world, please
> let me know.
>
> "Marlon Brown" <marlon_brown@.hotmail.com> wrote in message
> news:eBkAAqU4EHA.708@.TK2MSFTNGP11.phx.gbl...
>
Saturday, February 25, 2012
Assembly ReportingServicesWebServer problem
From the service manager the report service is running, but i get the following error on http://localhost/ReportServer/
Server Error in '/ReportServer' Application.
Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.Parser Error Message: Could not load file or assembly 'ReportingServicesWebServer, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. Access is denied.
Source Error:
Line 27: <assemblies>Line 28: <clear />
Line 29: <add assembly="ReportingServicesWebServer" />
Line 30: </assemblies>
Line 31: </compilation>
Source File: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\web.config Line: 29
Assembly Load Trace: The following information can be helpful to determine why the assembly 'ReportingServicesWebServer' could not be loaded.
=== Pre-bind state information ===LOG: User = Unknown
LOG: DisplayName = ReportingServicesWebServer
(Partial)
LOG: Appbase = file:///C:/Program Files/Microsoft SQL Server/MSSQL.3/Reporting Services/ReportServer/
LOG: Initial PrivatePath = C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\bin
Calling assembly : (Unknown).
===
LOG: This bind starts in default load context.
LOG: Using application configuration file: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\web.config
LOG: Using host configuration file: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet.config
LOG: Using machine configuration file from C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\config\machine.config.
LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind).
LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/Temporary ASP.NET Files/reportserver/b7e1529c/70d36ced/ReportingServicesWebServer.DLL.
LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/Temporary ASP.NET Files/reportserver/b7e1529c/70d36ced/ReportingServicesWebServer/ReportingServicesWebServer.DLL.
LOG: Attempting download of new URL file:///C:/Program Files/Microsoft SQL Server/MSSQL.3/Reporting Services/ReportServer/bin/ReportingServicesWebServer.DLL.
LOG: Using application configuration file: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\web.config
LOG: Using host configuration file: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet.config
LOG: Using machine configuration file from C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\config\machine.config.
LOG: Post-policy reference: ReportingServicesWebServer, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91
ERR: Failed to complete setup of assembly (hr = 0x80070005). Probing terminated.
Hi!
I'm having the same problem, can someone help me?
Thank you!
|||I have the same problem ,can someone help me..|||xian_ve
xian_ve,
Can you verify the version SQL reporting services is .NET version 2.0, and that your application pool for reporting service is using "Network" logon?
Ham
|||That is so on my computer.
What is the solution?
Assembly ReportingServicesWebServer problem
From the service manager the report service is running, but i get the following error on http://localhost/ReportServer/
Server Error in '/ReportServer' Application.
Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.Parser Error Message: Could not load file or assembly 'ReportingServicesWebServer, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. Access is denied.
Source Error:
Line 27: <assemblies>Line 28: <clear />
Line 29: <add assembly="ReportingServicesWebServer" />
Line 30: </assemblies>
Line 31: </compilation>
Source File: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\web.config Line: 29
Assembly Load Trace: The following information can be helpful to determine why the assembly 'ReportingServicesWebServer' could not be loaded.
=== Pre-bind state information ===LOG: User = Unknown
LOG: DisplayName = ReportingServicesWebServer
(Partial)
LOG: Appbase = file:///C:/Program Files/Microsoft SQL Server/MSSQL.3/Reporting Services/ReportServer/
LOG: Initial PrivatePath = C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\bin
Calling assembly : (Unknown).
===
LOG: This bind starts in default load context.
LOG: Using application configuration file: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\web.config
LOG: Using host configuration file: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet.config
LOG: Using machine configuration file from C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\config\machine.config.
LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind).
LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/Temporary ASP.NET Files/reportserver/b7e1529c/70d36ced/ReportingServicesWebServer.DLL.
LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/Temporary ASP.NET Files/reportserver/b7e1529c/70d36ced/ReportingServicesWebServer/ReportingServicesWebServer.DLL.
LOG: Attempting download of new URL file:///C:/Program Files/Microsoft SQL Server/MSSQL.3/Reporting Services/ReportServer/bin/ReportingServicesWebServer.DLL.
LOG: Using application configuration file: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\web.config
LOG: Using host configuration file: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet.config
LOG: Using machine configuration file from C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\config\machine.config.
LOG: Post-policy reference: ReportingServicesWebServer, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91
ERR: Failed to complete setup of assembly (hr = 0x80070005). Probing terminated.
Hi!
I'm having the same problem, can someone help me?
Thank you!
|||I have the same problem ,can someone help me..|||xian_ve
xian_ve,
Can you verify the version SQL reporting services is .NET version 2.0, and that your application pool for reporting service is using "Network" logon?
Ham
|||That is so on my computer.
What is the solution?
|||I also have d same problem..can anybody tell me how to fix it?????Assembly ReportingServicesWebServer problem
From the service manager the report service is running, but i get the following error on http://localhost/ReportServer/
Server Error in '/ReportServer' Application.
Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.Parser Error Message: Could not load file or assembly 'ReportingServicesWebServer, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. Access is denied.
Source Error:
Line 27: <assemblies>Line 28: <clear />
Line 29: <add assembly="ReportingServicesWebServer" />
Line 30: </assemblies>
Line 31: </compilation>
Source File: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\web.config Line: 29
Assembly Load Trace: The following information can be helpful to determine why the assembly 'ReportingServicesWebServer' could not be loaded.
=== Pre-bind state information ===LOG: User = Unknown
LOG: DisplayName = ReportingServicesWebServer
(Partial)
LOG: Appbase = file:///C:/Program Files/Microsoft SQL Server/MSSQL.3/Reporting Services/ReportServer/
LOG: Initial PrivatePath = C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\bin
Calling assembly : (Unknown).
===
LOG: This bind starts in default load context.
LOG: Using application configuration file: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\web.config
LOG: Using host configuration file: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet.config
LOG: Using machine configuration file from C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\config\machine.config.
LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind).
LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/Temporary ASP.NET Files/reportserver/b7e1529c/70d36ced/ReportingServicesWebServer.DLL.
LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/Temporary ASP.NET Files/reportserver/b7e1529c/70d36ced/ReportingServicesWebServer/ReportingServicesWebServer.DLL.
LOG: Attempting download of new URL file:///C:/Program Files/Microsoft SQL Server/MSSQL.3/Reporting Services/ReportServer/bin/ReportingServicesWebServer.DLL.
LOG: Using application configuration file: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\web.config
LOG: Using host configuration file: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet.config
LOG: Using machine configuration file from C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\config\machine.config.
LOG: Post-policy reference: ReportingServicesWebServer, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91
ERR: Failed to complete setup of assembly (hr = 0x80070005). Probing terminated.
Hi!
I'm having the same problem, can someone help me?
Thank you!
|||I have the same problem ,can someone help me..|||xian_ve
xian_ve,
Can you verify the version SQL reporting services is .NET version 2.0, and that your application pool for reporting service is using "Network" logon?
Ham
|||That is so on my computer.
What is the solution?
Assembly ReportingServicesWebServer problem
From the service manager the report service is running, but i get the following error on http://localhost/ReportServer/
Server Error in '/ReportServer' Application.
Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.Parser Error Message: Could not load file or assembly 'ReportingServicesWebServer, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. Access is denied.
Source Error:
Line 27: <assemblies>Line 28: <clear />
Line 29: <add assembly="ReportingServicesWebServer" />
Line 30: </assemblies>
Line 31: </compilation>
Source File: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\web.config Line: 29
Assembly Load Trace: The following information can be helpful to determine why the assembly 'ReportingServicesWebServer' could not be loaded.
=== Pre-bind state information ===LOG: User = Unknown
LOG: DisplayName = ReportingServicesWebServer
(Partial)
LOG: Appbase = file:///C:/Program Files/Microsoft SQL Server/MSSQL.3/Reporting Services/ReportServer/
LOG: Initial PrivatePath = C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\bin
Calling assembly : (Unknown).
===
LOG: This bind starts in default load context.
LOG: Using application configuration file: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\web.config
LOG: Using host configuration file: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet.config
LOG: Using machine configuration file from C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\config\machine.config.
LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind).
LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/Temporary ASP.NET Files/reportserver/b7e1529c/70d36ced/ReportingServicesWebServer.DLL.
LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/Temporary ASP.NET Files/reportserver/b7e1529c/70d36ced/ReportingServicesWebServer/ReportingServicesWebServer.DLL.
LOG: Attempting download of new URL file:///C:/Program Files/Microsoft SQL Server/MSSQL.3/Reporting Services/ReportServer/bin/ReportingServicesWebServer.DLL.
LOG: Using application configuration file: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\web.config
LOG: Using host configuration file: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet.config
LOG: Using machine configuration file from C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\config\machine.config.
LOG: Post-policy reference: ReportingServicesWebServer, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91
ERR: Failed to complete setup of assembly (hr = 0x80070005). Probing terminated.
Hi!
I'm having the same problem, can someone help me?
Thank you!
|||I have the same problem ,can someone help me..|||xian_ve
xian_ve,
Can you verify the version SQL reporting services is .NET version 2.0, and that your application pool for reporting service is using "Network" logon?
Ham
|||That is so on my computer.
What is the solution?
|||I had a similar error, and it was some problems in c:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\rssrvpolicy.config, so check that that one looks correct.
Friday, February 24, 2012
aspnet_regsqlcache tool not found in my system
hi i am going to install the aspnet_regsqlcache tool in my system to create the notification tables for my database. while i am istalling in the .net framework command prompt, it tells like this,
"'aspnet_regsqlcache' is not recognized as an internal or external command"
what is the problem in my system...please any one help to solve this issues..
thanks in advance
The utility is now called aspnet_regsql.exe. It can be found here C:\WINDOWS\Microsoft.Net\Framework\v2.0.50727.
This was also discussed on the Wrox forum (in case you read about this in a book). http://p2p.wrox.com/TopicIndex/21996.htm
Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/
'aspnet_regiis' impact on classic ASP?
We want to install RS on a Windows 2003 / IIS 6 server.
Does it hurt our 'classic' (pre .net) ASP aps if we run aspnet_regiis -i
on this machine?
tanx,
Derk JanWe have classic ASP and ASP.NET running on the same server just fine. Since
ASP.NET uses different file extensions (aspx), it shouldn't hurt.
Nevertheless, a system backup -- or trying it first on a dev server -- is
always a good idea.
--
Cheers,
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"Derk Jan" <DerkJan@.discussions.microsoft.com> wrote in message
news:6BDE0622-F903-48D8-B419-4D6BD497FD0F@.microsoft.com...
> Hi,
> We want to install RS on a Windows 2003 / IIS 6 server.
> Does it hurt our 'classic' (pre .net) ASP aps if we run aspnet_regiis -i
> on this machine?
> tanx,
> Derk Jan
>
Monday, February 13, 2012
ASP.NET Problem installing SQL Server 2000 Reporting Services
e -i" and I have installed all necessary updates and restarted the server. I've even set ASP.NET version 1.1.4322 as the default version on the Default Web Site. It is still claiming that it's not installed or not configured.
I checked the help and it says:
Report Manager is an ASP.NET application. If you are installing Report Manager, you must have ASP.NET installed and configured. Setup requires that version 1.1.4322 of ASP.NET be registered with IIS. If you are installing Reporting Services on Windows Server 2003, ASP.NET must be running as Network Service. For information about installing and configuring ASP.NET, see the setup documentation
As far as I can tell, ASP.NET 1.1.4322 is installed and configured and running as the user Network Service. Am I missing anything?
If you have not done actual Asp.net development in this box you are missing a lot because Win2003 comes with IIS not installed and when you install it IIS comes to just render HTML which means all components needed to run Asp.net are disabled. Now to how you fix it first remove IIS if it is installed, then you go to add it in add/remove Windows component add IIS then click on details in that box you will see all the sub components needed to run Asp.net that are disabled. When you have finished that, go into IIS and remove all the security restrictions that makes IIS to run only HTML.
Now to what you need to get SQL Server to install Reporting services 2000 make sure you are running SQL Server 2000 and have at least service pack 3a or 4 and please don't answer questions Windows ask you during the installation only answer questions relevant to you. Post again if you still need help but follow my instructions and you will get through I just helped two people with similar problems.
|||I tried that and didn't quite get there. I uninstalled the .net framework 2.0 as that was the default version on IIS and I don't think anything was using it. I also ran aspnet_ regiis.exe -i -enable.It would have installed this morning but for the fact that SQL Server needed SP4 installing and everyone got in to work before I could get stuff installed!