Cannot find mdf files: sp1

Showing posts with label sp1. Show all posts

Sunday, March 25, 2012

Cannot reference Microsoft.SqlServer.Dts.DtsClient?

Reinstalled SqlServer 2005 and SP2. Reinstalled VS2005 and SP1. I add a reference to Microsoft.SqlServer.Dts.DtsClient. It automatically adds a line to web.config

I still cannot do

using Microsoft.SqlServer.Dts.DtsClient;

I can do

using Microsoft.SqlServer.Server;

I am thinking a config file or something is missing/corrupt somewhere to prevent me from being able to correctly reference this dll. Can anyone help please?

NoRemorse,

If you're trying to configure the Reporting Service you may find the following helpful: http://msdn2.microsoft.com/en-us/library/ms345250.aspx.

HTH,

Patrik

|||I just want to be able to run an SSIS package from code. I need to have that assembly in order to get at the DTS objects. I did what that article suggested anyway but it still doesn't work. Oddly, if I create a new Windows Form project I can reference the assembly fine, so the DLL seems to be regeistered ok. But in a Web project I cannot reference it.|||I uninstalled VS team system and now it works fine. Some incompatibility there

Cannot rebuild full text catalogs

Recently moved database and full text catalogs to new server with SQL Server
2000 sp3a/SBS 2003 sp1
I am having problems rebuilding and repopulating the fulltext catalogs
restored to the new server.
The message I encounter is "Error 7635: The Microsoft Search cannot be
administered under the present user account".
I understand from the link I have been referred to
"http://support.microsoft.com/default.aspx?scid=kb;en-us;277549" states that
the service logon was changed through the control panel instead of the
Enterprise Manager therefore the service login for SQL Server does not have
administrative priviledges over the MSSearch service.
None of the service logins were changed through the control panel
I have tried the workround as suggested in the link but I still get the same
error message when I try to rebuild the full text catalog.
Any of you MVP's with another approach or suggestions to solve this problem?What account is MSSearch running under? It must be running under the local
system account. If it is not change it, you can change it through the
services applet in Control panel - Administrative Tasks.
Check that the builtin\Admins group is in the sysadmin role, and if not do
the following
use master
go
exec sp_grantlogin N'NT Authority\System'
exec sp_defaultdb N'NT Authority\System', N'master'
exec sp_defaultlanguage N'NT Authority\System','us_english'
exec sp_addsrvrolemember N'NT Authority\System', sysadmin
goThen change the SQL Server account to a the local system account in
Enterprise manger, right click on it and select properties and then select
the security tab and make the modifcation here, bounce it and the repeat the
process to have it run under a local adminstrators account.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Jarvis Allen" <JarvisAllen@.discussions.microsoft.com> wrote in message
news:DA108BC7-E94F-4391-A71F-505CF6D42E0A@.microsoft.com...
> Recently moved database and full text catalogs to new server with SQL
> Server
> 2000 sp3a/SBS 2003 sp1
> I am having problems rebuilding and repopulating the fulltext catalogs
> restored to the new server.
> The message I encounter is "Error 7635: The Microsoft Search cannot be
> administered under the present user account".
> I understand from the link I have been referred to
> "http://support.microsoft.com/default.aspx?scid=kb;en-us;277549" states
> that
> the service logon was changed through the control panel instead of the
> Enterprise Manager therefore the service login for SQL Server does not
> have
> administrative priviledges over the MSSearch service.
> None of the service logins were changed through the control panel
> I have tried the workround as suggested in the link but I still get the
> same
> error message when I try to rebuild the full text catalog.
> Any of you MVP's with another approach or suggestions to solve this
> problem?|||"Hilary Cotter" wrote:
> What account is MSSearch running under? It must be running under the local
> system account. If it is not change it, you can change it through the
> services applet in Control panel - Administrative Tasks.
> Check that the builtin\Admins group is in the sysadmin role, and if not do
> the following
> use master
> go
> exec sp_grantlogin N'NT Authority\System'
> exec sp_defaultdb N'NT Authority\System', N'master'
> exec sp_defaultlanguage N'NT Authority\System','us_english'
> exec sp_addsrvrolemember N'NT Authority\System', sysadmin
> goThen change the SQL Server account to a the local system account in
> Enterprise manger, right click on it and select properties and then select
> the security tab and make the modifcation here, bounce it and the repeat the
> process to have it run under a local adminstrators account.
>
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Jarvis Allen" <JarvisAllen@.discussions.microsoft.com> wrote in message
> news:DA108BC7-E94F-4391-A71F-505CF6D42E0A@.microsoft.com...
> > Recently moved database and full text catalogs to new server with SQL
> > Server
> > 2000 sp3a/SBS 2003 sp1
> > I am having problems rebuilding and repopulating the fulltext catalogs
> > restored to the new server.
> > The message I encounter is "Error 7635: The Microsoft Search cannot be
> > administered under the present user account".
> >
> > I understand from the link I have been referred to
> > "http://support.microsoft.com/default.aspx?scid=kb;en-us;277549" states
> > that
> > the service logon was changed through the control panel instead of the
> > Enterprise Manager therefore the service login for SQL Server does not
> > have
> > administrative priviledges over the MSSearch service.
> > None of the service logins were changed through the control panel
> >
> > I have tried the workround as suggested in the link but I still get the
> > same
> > error message when I try to rebuild the full text catalog.
> >
> > Any of you MVP's with another approach or suggestions to solve this
> > problem?
> Thank you for your reply Hilary
The MS Search service is using the local system logon and built in admin has
the role of sydadmin.
I followed your instructions which was similiar to the instruction I
followed in the link i was reffered to inmy original message.
Unfortunately the your instructions I followed failed to cure the 7635 error
(cannot administer MS Search service under present user account).
Are ther any other slutions to try?
>|||"Jarvis Allen" wrote:
I have tried suggestions by Hilary and the problem still persists.
The MS Search is running under the local system account as it should which
seems to be the problem.
The problem seems to be getting the administer rights over the MS Search
service.
The SQL Server does start with the Domain Admin user.
For some reason the Domain Admin user can administer the MS Search service
even though I have used the suggested way to gain admin rights over the MS
Search!
Any other ideas from you SQL experts?
>
> "Hilary Cotter" wrote:
> > What account is MSSearch running under? It must be running under the local
> > system account. If it is not change it, you can change it through the
> > services applet in Control panel - Administrative Tasks.
> >
> > Check that the builtin\Admins group is in the sysadmin role, and if not do
> > the following
> >
> > use master
> > go
> > exec sp_grantlogin N'NT Authority\System'
> > exec sp_defaultdb N'NT Authority\System', N'master'
> > exec sp_defaultlanguage N'NT Authority\System','us_english'
> > exec sp_addsrvrolemember N'NT Authority\System', sysadmin
> > goThen change the SQL Server account to a the local system account in
> > Enterprise manger, right click on it and select properties and then select
> > the security tab and make the modifcation here, bounce it and the repeat the
> > process to have it run under a local adminstrators account.
> >
> >
> >
> > --
> > Hilary Cotter
> > Director of Text Mining and Database Strategy
> > RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> >
> > This posting is my own and doesn't necessarily represent RelevantNoise's
> > positions, strategies or opinions.
> >
> > Looking for a SQL Server replication book?
> > http://www.nwsu.com/0974973602.html
> >
> > Looking for a FAQ on Indexing Services/SQL FTS
> > http://www.indexserverfaq.com
> >
> >
> >
> > "Jarvis Allen" <JarvisAllen@.discussions.microsoft.com> wrote in message
> > news:DA108BC7-E94F-4391-A71F-505CF6D42E0A@.microsoft.com...
> > > Recently moved database and full text catalogs to new server with SQL
> > > Server
> > > 2000 sp3a/SBS 2003 sp1
> > > I am having problems rebuilding and repopulating the fulltext catalogs
> > > restored to the new server.
> > > The message I encounter is "Error 7635: The Microsoft Search cannot be
> > > administered under the present user account".
> > >
> > > I understand from the link I have been referred to
> > > "http://support.microsoft.com/default.aspx?scid=kb;en-us;277549" states
> > > that
> > > the service logon was changed through the control panel instead of the
> > > Enterprise Manager therefore the service login for SQL Server does not
> > > have
> > > administrative priviledges over the MSSearch service.
> > > None of the service logins were changed through the control panel
> > >
> > > I have tried the workround as suggested in the link but I still get the
> > > same
> > > error message when I try to rebuild the full text catalog.
> > >
> > > Any of you MVP's with another approach or suggestions to solve this
> > > problem?
> >
> > Thank you for your reply Hilary
> The MS Search service is using the local system logon and built in admin has
> the role of sydadmin.
> I followed your instructions which was similiar to the instruction I
> followed in the link i was reffered to inmy original message.
> Unfortunately the your instructions I followed failed to cure the 7635 error
> (cannot administer MS Search service under present user account).
> Are ther any other slutions to try?
> >|||>
> "Jarvis Allen" wrote:
> I have tried suggestions by Hilary and the problem still persists.
> The MS Search is running under the local system account as it should which
> seems to be the problem.
> The problem seems to be getting the administer rights over the MS Search
> service.
> The SQL Server does start with the Domain Admin user.
> For some reason the Domain Admin user cannot administer the MS Search service
> even though I have used the suggested way to gain admin rights over the MS
> Search!
> Any other ideas from you SQL experts?
> >
> >
> > "Hilary Cotter" wrote:
> >
> > > What account is MSSearch running under? It must be running under the local
> > > system account. If it is not change it, you can change it through the
> > > services applet in Control panel - Administrative Tasks.
> > >
> > > Check that the builtin\Admins group is in the sysadmin role, and if not do
> > > the following
> > >
> > > use master
> > > go
> > > exec sp_grantlogin N'NT Authority\System'
> > > exec sp_defaultdb N'NT Authority\System', N'master'
> > > exec sp_defaultlanguage N'NT Authority\System','us_english'
> > > exec sp_addsrvrolemember N'NT Authority\System', sysadmin
> > > goThen change the SQL Server account to a the local system account in
> > > Enterprise manger, right click on it and select properties and then select
> > > the security tab and make the modifcation here, bounce it and the repeat the
> > > process to have it run under a local adminstrators account.
> > >
> > >
> > >
> > > --
> > > Hilary Cotter
> > > Director of Text Mining and Database Strategy
> > > RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> > >
> > > This posting is my own and doesn't necessarily represent RelevantNoise's
> > > positions, strategies or opinions.
> > >
> > > Looking for a SQL Server replication book?
> > > http://www.nwsu.com/0974973602.html
> > >
> > > Looking for a FAQ on Indexing Services/SQL FTS
> > > http://www.indexserverfaq.com
> > >
> > >
> > >
> > > "Jarvis Allen" <JarvisAllen@.discussions.microsoft.com> wrote in message
> > > news:DA108BC7-E94F-4391-A71F-505CF6D42E0A@.microsoft.com...
> > > > Recently moved database and full text catalogs to new server with SQL
> > > > Server
> > > > 2000 sp3a/SBS 2003 sp1
> > > > I am having problems rebuilding and repopulating the fulltext catalogs
> > > > restored to the new server.
> > > > The message I encounter is "Error 7635: The Microsoft Search cannot be
> > > > administered under the present user account".
> > > >
> > > > I understand from the link I have been referred to
> > > > "http://support.microsoft.com/default.aspx?scid=kb;en-us;277549" states
> > > > that
> > > > the service logon was changed through the control panel instead of the
> > > > Enterprise Manager therefore the service login for SQL Server does not
> > > > have
> > > > administrative priviledges over the MSSearch service.
> > > > None of the service logins were changed through the control panel
> > > >
> > > > I have tried the workround as suggested in the link but I still get the
> > > > same
> > > > error message when I try to rebuild the full text catalog.
> > > >
> > > > Any of you MVP's with another approach or suggestions to solve this
> > > > problem?
> > >
> > > Thank you for your reply Hilary
> > The MS Search service is using the local system logon and built in admin has
> > the role of sydadmin.
> > I followed your instructions which was similiar to the instruction I
> > followed in the link i was reffered to inmy original message.
> > Unfortunately the your instructions I followed failed to cure the 7635 error
> > (cannot administer MS Search service under present user account).
> > Are ther any other slutions to try?
> > >

Tuesday, March 20, 2012

Cannot open offline cube

Hi,

I created an offline cube file (.cub) using SSAS 2005 sp1. I tried to open the cube file by following these steps:

1. Open excel 2003. On the toolbar, click on Data and select PivotTable and PivotChart report.

2. Select External data source as the data you want to analyze then click on next.

3. Click on the Get Data button on the next step.

4. Choose the OLAP Cubes tab on the pop-up window, select <New Data Source> and Click OK.

5. Type "Sales" as the name of the data source.

6.Choose Microsoft OLE DB Provider for Analysis Services 9.0 as the OLAP provider. Click on Connect button

7. Select the cube file option and browse for the location of the cube file. Click Finish.

8. On the fourth step (here comes the problem),on the Select the Cube that contains the data you want list, nothing is available in the dropdown list. And since I cannot finish this step, the OK button remains disabled and I was not able to open the cube file.

Can any one help me on this?

Thanks in advance,

Destry

I have exactly the same problem, as a matter of fact I was about to ask that question.

Should you find a workaround on your own, I would appreciate it if you could post it here as well too. Tia.

|||

There are several things can be going wrong. Here are several ideas for you to try.

1. Try and use Microsoft OLE DB Provider for Analysis Services 8.0 to connect to your local cube.

2. Try and use MDXSample application. In the connection dialog, as server name specify a path to your local cube file. Something like c:\my cubes\cube1.cub. If you can connect and but cant see cube name there, most likely something wrong with your local cube file.

Edward Melomed.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Monday, March 19, 2012

Cannot open database "SharePointSharedServices" requested by the l

Environment: Windows Server 2003 SP1, SQL Server 2005 (no SP)
Up until a few days ago a Maintenance Plan and a dependent job have started
to fail with the following error.
[298] SQLServer Error: 18456, Login failed for user 'XXXXX\yyyyyyyy'.
[SQLSTATE 28000]
[298] SQLServer Error: 4060, Cannot open database "SharePointSharedServi
ces"
requested by the login. The login failed. [SQLSTATE 42000]
The Maintenance Plan backs up the user & system databases, and transaction
files.
The "SharePointSharedServices" database does not exist. Checked
sys.databases to verify.
Other Sharepoint databases exist on the server.
Bounced SQL Server Agent but get the same error.
The Login account is valid. Reset password on server but get the same error.
Modified the MP to backup the non-SharePoint databases but get the same erro
r.
Any suggestions?I would suggest dropping and recreating the maintenance plan.
"mg" wrote:

> Environment: Windows Server 2003 SP1, SQL Server 2005 (no SP)
> Up until a few days ago a Maintenance Plan and a dependent job have starte
d
> to fail with the following error.
> [298] SQLServer Error: 18456, Login failed for user 'XXXXX\yyyyyyyy'.
> [SQLSTATE 28000]
> [298] SQLServer Error: 4060, Cannot open database "SharePointSharedSer
vices"
> requested by the login. The login failed. [SQLSTATE 42000]
> The Maintenance Plan backs up the user & system databases, and transaction
> files.
> The "SharePointSharedServices" database does not exist. Checked
> sys.databases to verify.
> Other Sharepoint databases exist on the server.
> Bounced SQL Server Agent but get the same error.
> The Login account is valid. Reset password on server but get the same erro
r.
> Modified the MP to backup the non-SharePoint databases but get the same er
ror.
> Any suggestions?
>

Cannot open database "SharePointSharedServices" requested by the l

Environment: Windows Server 2003 SP1, SQL Server 2005 (no SP)
Up until a few days ago a Maintenance Plan and a dependent job have started
to fail with the following error.
[298] SQLServer Error: 18456, Login failed for user 'XXXXX\yyyyyyyy'.
[SQLSTATE 28000]
[298] SQLServer Error: 4060, Cannot open database "SharePointSharedServices"
requested by the login. The login failed. [SQLSTATE 42000]
The Maintenance Plan backs up the user & system databases, and transaction
files.
The "SharePointSharedServices" database does not exist. Checked
sys.databases to verify.
Other Sharepoint databases exist on the server.
Bounced SQL Server Agent but get the same error.
The Login account is valid. Reset password on server but get the same error.
Modified the MP to backup the non-SharePoint databases but get the same error.
Any suggestions?
I would suggest dropping and recreating the maintenance plan.
"mg" wrote:

> Environment: Windows Server 2003 SP1, SQL Server 2005 (no SP)
> Up until a few days ago a Maintenance Plan and a dependent job have started
> to fail with the following error.
> [298] SQLServer Error: 18456, Login failed for user 'XXXXX\yyyyyyyy'.
> [SQLSTATE 28000]
> [298] SQLServer Error: 4060, Cannot open database "SharePointSharedServices"
> requested by the login. The login failed. [SQLSTATE 42000]
> The Maintenance Plan backs up the user & system databases, and transaction
> files.
> The "SharePointSharedServices" database does not exist. Checked
> sys.databases to verify.
> Other Sharepoint databases exist on the server.
> Bounced SQL Server Agent but get the same error.
> The Login account is valid. Reset password on server but get the same error.
> Modified the MP to backup the non-SharePoint databases but get the same error.
> Any suggestions?
>

Cannot open database "SharePointSharedServices" requested by the l

Environment: Windows Server 2003 SP1, SQL Server 2005 (no SP)
Up until a few days ago a Maintenance Plan and a dependent job have started
to fail with the following error.
[298] SQLServer Error: 18456, Login failed for user 'XXXXX\yyyyyyyy'.
[SQLSTATE 28000]
[298] SQLServer Error: 4060, Cannot open database "SharePointSharedServices"
requested by the login. The login failed. [SQLSTATE 42000]
The Maintenance Plan backs up the user & system databases, and transaction
files.
The "SharePointSharedServices" database does not exist. Checked
sys.databases to verify.
Other Sharepoint databases exist on the server.
Bounced SQL Server Agent but get the same error.
The Login account is valid. Reset password on server but get the same error.
Modified the MP to backup the non-SharePoint databases but get the same error.
Any suggestions?I would suggest dropping and recreating the maintenance plan.
"mg" wrote:
> Environment: Windows Server 2003 SP1, SQL Server 2005 (no SP)
> Up until a few days ago a Maintenance Plan and a dependent job have started
> to fail with the following error.
> [298] SQLServer Error: 18456, Login failed for user 'XXXXX\yyyyyyyy'.
> [SQLSTATE 28000]
> [298] SQLServer Error: 4060, Cannot open database "SharePointSharedServices"
> requested by the login. The login failed. [SQLSTATE 42000]
> The Maintenance Plan backs up the user & system databases, and transaction
> files.
> The "SharePointSharedServices" database does not exist. Checked
> sys.databases to verify.
> Other Sharepoint databases exist on the server.
> Bounced SQL Server Agent but get the same error.
> The Login account is valid. Reset password on server but get the same error.
> Modified the MP to backup the non-SharePoint databases but get the same error.
> Any suggestions?
>

Thursday, March 8, 2012

Cannot Launch DTA - Failed to open new connection

Installed SQL 2005 STD and installed SP1 for SQL on a Windows 2003 STD server.

I launch DTA and I am logged in with the same windows account which the SQL services use and I get the following message:

===================================

Failed to open a new connection.

===================================

Could not find stored procedure 'msdb..sp_DTA_help_session'. (.Net SqlClient Data Provider)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.2047&EvtSrc=MSSQLServer&EvtID=2812&LinkId=20476

Server Name: FHCMS,1433
Error Number: 2812
Severity: 16
State: 62
Line Number: 1

Program Location:

at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader()
at Microsoft.SqlServer.Management.DTA.Client.TuningServer.QuerySessions()
at Microsoft.SqlServer.Management.DTA.Client.TuningServer.InitializeConnection()
at Microsoft.SqlServer.Management.DTA.Client.TuningServer.Connect()
at Microsoft.SqlServer.Management.DTA.Shell.SessionMonitor.AddServerInternal(SqlConnectionInfo connectionInfo, SqlConnection connection)
at Microsoft.SqlServer.Management.DTA.Shell.SessionMonitor.AddServer(SqlConnectionInfo connectionInfo, SqlConnection connection)
at Microsoft.SqlServer.Management.DTA.Shell.SessionMonitor.OnConnect(Object sender, EventArgs e)

Any help would be appreciated.

Thanks,
Pete

are you using RTM or sp1 version? a MSFT guy told me that there are problems he has heard of with DTA in the RTM build...I would tell you that while I love the product, DTA has not been the most stable of components overall from my expereinces w/it.|||

I am using the SP1 version for SQL 2005, I didn't even check to see if DTA worked before that since it is a brand new server.

I saw a post that stated the user does not have sysadmin rights for SQL and that is what the error message means but I created a Domain Admin account for SQL and that is what I am logged on to the server with.

Thanks,
Pete

|||

have you checked all the usual log locations...

sql exception log

event log

unfortunetly i cannot be of any more help at this point.

|||

I have the same trouble.

Cannot Launch DTA - Failed to open new connection

Installed SQL 2005 STD and installed SP1 for SQL on a Windows 2003 STD server.

I launch DTA and I am logged in with the same windows account which the SQL services use and I get the following message:

===================================

Failed to open a new connection.

===================================

Could not find stored procedure 'msdb..sp_DTA_help_session'. (.Net SqlClient Data Provider)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.2047&EvtSrc=MSSQLServer&EvtID=2812&LinkId=20476

Server Name: FHCMS,1433
Error Number: 2812
Severity: 16
State: 62
Line Number: 1

Program Location:

Any help would be appreciated.

Thanks,
Pete

I am using the SP1 version for SQL 2005, I didn't even check to see if DTA worked before that since it is a brand new server.

Thanks,
Pete

|||

have you checked all the usual log locations...

sql exception log

event log

unfortunetly i cannot be of any more help at this point.

|||

I have the same trouble.

Saturday, February 25, 2012

Cannot install SQL 2000 Reporting Services on W2K3 server

Hi ALL,
I want to install SQL 2000 Reporting Services Component on a Windows Server
2003 with SP1 box. While I ran the SQL 2000 setup.exe, it prompted the error
message 'System Check Results --> ASP.NET is not installed or is not
registered with your Web Server". However, I'd checked the Web service
extensions and 'Active Server Pages', 'ASP.NET v1.1.4322' and 'ASP.NET
v2.0.50727' had been allowed. Do anyone have the same problem? Can I install
the Reporting Services Database on the SQL 2000 cluster?
TIA.Hi, I have the same problem, I "only" have the error that I dont have asp.net
installed or configured, despite that it is installed and configured, I have
both asp.net 1.1 and 2.0, I have tried to switch between both, but the result
is the same error, any ideas? Have you got a solution yet?
DQ
"M C" wrote:
> Hi ALL,
> I want to install SQL 2000 Reporting Services Component on a Windows Server
> 2003 with SP1 box. While I ran the SQL 2000 setup.exe, it prompted the error
> message 'System Check Results --> ASP.NET is not installed or is not
> registered with your Web Server". However, I'd checked the Web service
> extensions and 'Active Server Pages', 'ASP.NET v1.1.4322' and 'ASP.NET
> v2.0.50727' had been allowed. Do anyone have the same problem? Can I install
> the Reporting Services Database on the SQL 2000 cluster?
> TIA.
>
>|||SOLUTION that helped me!!
FIX: Error "ASP.NET v1.1 not Installed" while installing Sql Server 2000
Reporting Services
I finally had the chance to rebuild my dev machine with the RTM version of
Sql Server 200 Reporting Services [SQL2kRS] and ran into an unusual error.
During the "Check Prerequisites" stage of installation, it said that I didnt
have ASP.NET v1.1 installed on my PC. Considering that I do web-development
with VS.NET 2003 on this PC I was a bit perplexed why it said that.
After much digging and exploring, I finally discovered the problem. A
recent install of the new XP version of the Longhorn Command Shell had
installed the .NET Framework v2.0.31113.33 and set it as the Root Version of
the framework for ASP.NET.
So, the fix is pretty trivial, just update the RootVer registry value to
correctly (or temporarily) show v1.1.4322.573.
[\\HKLM\SOFTWARE\Microsoft\ASP.NET\RootVer] = "1.1.4322.573"
Strangely enough, this didnt seem to be affecting my ASP.NET applications.
*shrug*
None of this was documented in the verbose Help files that shipped with
SQL2kRS. This got me thinking about the nature of help files. Far too
often, I see FAQ's and "Common Issues" under the Troubleshooting section of
help files, yet rarely do I have those "common" problems.
I would much prefer a generic section on, "How to troubleshoot", "Where to
look for error clues", and provide deep lists of "Why an application or
installation might fail".
In this case, I actually did find a good reference in the Help entitled "Log
Files Used During Installation". This section explained how to locate the
log files created during installation, and this is how I eventually solved
the problem.
For reference, in SQL2kRS there are 3 main places to look for log files;
C:\Program Files\Microsoft SQL Server\80\RS Setup Bootstrap\Log\RSStp_.cab
(inside the CAB)
AND
%temp%\rsstp<integer>.log
(<integer> = number to make filename unique. e.g. rsstp2.log)
AND
%temp%\RSMSI<integer>.log
The latter 2 log files are the same ones that get copied into the CAB file
listed above, but its still useful knowledge in case something fails before
they get added to the CAB.
"DQ" wrote:
> Hi, I have the same problem, I "only" have the error that I dont have asp.net
> installed or configured, despite that it is installed and configured, I have
> both asp.net 1.1 and 2.0, I have tried to switch between both, but the result
> is the same error, any ideas? Have you got a solution yet?
> DQ
>
> "M C" wrote:
> > Hi ALL,
> >
> > I want to install SQL 2000 Reporting Services Component on a Windows Server
> > 2003 with SP1 box. While I ran the SQL 2000 setup.exe, it prompted the error
> > message 'System Check Results --> ASP.NET is not installed or is not
> > registered with your Web Server". However, I'd checked the Web service
> > extensions and 'Active Server Pages', 'ASP.NET v1.1.4322' and 'ASP.NET
> > v2.0.50727' had been allowed. Do anyone have the same problem? Can I install
> > the Reporting Services Database on the SQL 2000 cluster?
> >
> > TIA.
> >
> >
> >

Cannot install SP1 x86 - Windows XP Professional

Hi, I am trying to install SP1 on a Windows XP Professional - Version 2002 SP2.

but i got an Error, this is the error log :

(File : Redist9_Hotfix_KB913090.log )

05/18/2006 16:59:31.835 ================================================================================
05/18/2006 16:59:31.866 Hotfix package launched
05/18/2006 17:01:07.616 Attempting to install instance: SQL Server Native Client
05/18/2006 17:01:07.631 Attempting to install target: GDSA3367
05/18/2006 17:01:07.678 Attempting to install file: sqlncli.msi
05/18/2006 17:01:07.881 Attempting to install file: \\GDSA3367\c$\33b3e8d8202a1514eb8d3dbc\HotFixSqlncli\Files\sqlncli.msi
05/18/2006 17:01:07.928 Creating MSI install log file at: C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_sqlncli.msi.log
05/18/2006 17:01:07.959 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
05/18/2006 17:01:07.991 Failed to read registry key: Debug
05/18/2006 17:01:11.381 MSP returned 0: The action completed successfully.
05/18/2006 17:01:11.444 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
05/18/2006 17:01:11.475 Failed to read registry key: Debug
05/18/2006 17:01:11.491 Successfully installed file: \\GDSA3367\c$\33b3e8d8202a1514eb8d3dbc\HotFixSqlncli\Files\sqlncli.msi
05/18/2006 17:01:11.522 Successfully installed target: GDSA3367
05/18/2006 17:01:11.553 Successfully installed instance: SQL Server Native Client
05/18/2006 17:01:11.584
05/18/2006 17:01:11.600 Product Status Summary:
05/18/2006 17:01:11.631 Product: SQL Server Native Client
05/18/2006 17:01:11.662 SQL Server Native Client (RTM ) - Success
05/18/2006 17:01:11.694
05/18/2006 17:01:11.709 Product: Setup Support Files
05/18/2006 17:01:11.741 Setup Support Files (RTM ) - Not Applied
05/18/2006 17:01:11.756
05/18/2006 17:01:11.834 Product: Database Services
05/18/2006 17:01:11.928 Database Services (RTM 1399 ENU) - Not Applied
05/18/2006 17:01:11.975
05/18/2006 17:01:11.991 Product: Client Components
05/18/2006 17:01:12.022 Client Components (SP1 2047 ENU) - Not Applied
05/18/2006 17:01:12.053
05/18/2006 17:01:12.069 Product: MSXML 6.0 Parser
05/18/2006 17:01:12.116 MSXML 6.0 Parser (RTM ) - Not Applied
05/18/2006 17:01:12.147
05/18/2006 17:01:12.162 Product: SQLXML4
05/18/2006 17:01:12.194 SQLXML4 (RTM ) - Not Applied
05/18/2006 17:01:12.225
05/18/2006 17:01:12.272 Product: Backward Compatibility
05/18/2006 17:01:12.303 Backward Compatibility (RTM ) - Not Applied
05/18/2006 17:01:12.381
05/18/2006 17:01:12.412 Product: Microsoft SQL Server VSS Writer
05/18/2006 17:01:12.428 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
05/18/2006 17:01:12.459
-<EOF>

...and this is the Error Report sends this info:

EventType : sqlsesetup P1 : sql9 P2 : 9 P3 : x86 P4 : null
P5 : null P6 : kb913090
P7 : _depot_sqlvault_setupmain_setup_sqlse_sqlsedll_copyengine.cpp - 856
P8 : null

Files:
C:\WINDOWS\Hotfix\HotFix.log
C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090.log
C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB913090.log
C:\WINDOWS\Hotfix\OLAP9\Logs\OLAP9_Hotfix_KB913090.log
C:\WINDOWS\Hotfix\NS9\Logs\NS9_Hotfix_KB913090.log
C:\WINDOWS\Hotfix\RS9\Logs\RS9_Hotfix_KB913090.log
C:\WINDOWS\Hotfix\DTS9\Logs\DTS9_Hotfix_KB913090.log
C:\WINDOWS\Hotfix\SQLTools9\Logs\SQLTools9_Hotfix_KB913090.log
C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_sqlncli.msi.log
C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_SqlSupport.msp.log
C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB913090_sqlrun_sql.msp.log
C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB913090_sqlrun_sql.msp.out

My Version of SQL is - Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86) Oct 14 2005 00:33:37 Copyright (c) 1988-2005 Microsoft Corporation Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2) .

Thanks.

Cristian Bianchi

I don't see anything interesting there. Can you look in the log files here:

%Program Files%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files

|||

Paul:

In the folder " %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files" there in not files dated when i made the instalation of the SP1. But i found in the log C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB913090_sqlrun_sql.msp.log , the next line :

MSI (s) (FC:F0) [17:21:26:030]: Product: Microsoft SQL Server 2005 - Update 'Service Pack 1 for SQL Server Database Services 2005 ENU (KB913090)' could not be installed. Error code 1603. Additional information is available in the log file C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB913090_sqlrun_sql.msp.log.

Thanks in advance.

Crsitan F. Bianchi

|||1603 is just "Fatal error during installation." The lines above that in the log should reveal something about the cause of the error.

Cannot install SP1 on SQL Server 2005 (64bit)

Hi,

I'm having problems installing SP1 on one of our servers.

If I try to install the x64 version of SP1 setup says it can not update my server and I should use x86 version. Trying to install the x86 version results in the message I should use x64 version....

Any ideas?

Regards, Jan

What version of SQL do you have on the machine? x64 or x86? And when are you getting the error?

Thanks,
Sam Lester (MSFT)

|||

Hi Sam,

version is Microsoft SQL Server Standard Edition (64-bit). I get this error after doubleclicking the service pack .exe file.

Regards,

Jan

|||

OK, just to confirm what is on the box, can you go to Add/Remove Programs, click on change, and then on Report. This will show everything that the discovery process finds associated with SQL Server. This may help us figure out why the detection is giving you the error.

Also, can you supply the package name that you're trying to run?

Thanks,
Sam

|||

Hi Sam,

here is the report:

SIAM

The following components are installed on this server

MSSQLSERVER

Analysis Services