Error when trying to process cube after SP2

Hi Guys

Seems a nasty error started to appear after I installed SP2 on the corporate server and my machine and then trying to process a cube. Process goes through fine, but when I try to browse it a following error pops up. If anyone can help me with this, that would be great.

Parser: The end of the input was reached. (Microsoft SQL Server 2005 Analysis Services)

Program Location:

at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Microsoft.AnalysisServices.AdomdClient.AdomdConnection.IXmlaClientProviderEx.Discover(String requestType, String requestNamespace, IDictionary restrictions, InlineErrorHandlingType inlineErrorHandling)
at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.GetSchemaDataSet(String schemaName, String schemaNamespace, IDictionary adomdRestrictions, Boolean throwOnInlineErrors)
at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.GetSchemaDataSet(String schemaName, String schemaNamespace, AdomdRestrictionCollection restrictions, Boolean throwOnInlineErrors)
at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.GetSchemaDataSet(String schemaName, AdomdRestrictionCollection restrictions)
at Microsoft.AnalysisServices.Browse.CubeBrowser.BrowsableObjectsManager.Refresh()
at Microsoft.AnalysisServices.Browse.CubeBrowser.BrowsableObjectsManager.UpdateComboBox()
at Microsoft.AnalysisServices.Browse.CubeBrowser.UpdateAll(Boolean translate)
at Microsoft.AnalysisServices.Browse.CubeBrowser.ReconnectCanFail()
at Microsoft.AnalysisServices.Browse.CubeBrowser.SupportFunctionWhichCanFail(FunctionWhichCanFail function)

Thank you

Found a problem: the default measures were not set up in perspectives. Hmm... I thought the first one will be selected automatically.

Error when trying to create new databaase using SQL Server

Hi,

I have installed MS SQL server and I'm trying to create a database using the Web Matrix Project. I'm doing the following:

1. Click the Data tab in the Workspace pane.
2. Click on "Add Database Connection"
3. Select "SQL Server/MSDE Database" and click OK
4. Enter the following information:
server=localhost
Windows authentication is on
Database=somename

Click Ok

After I do all this, I get the following error:
Unable to connect to the database
SQL server does not exist or access denied.
ConnectionOpen (Connect()).

The SQL Service Manager is running with the option "Distributed Transaction Coordinator" displaying on Services. (I'm new to SQL server).

What could be causing this to happen?

Thanks a lot."Add Database Connection" is for connecting to an existing database...

use SQL Enterprise Manager to create the database first.|||1. Check if the DNS entries for the database servers are correct. These could be one of the reasons.
2. You must also see if you have sysadmin previledges to create a database.

These are some of the points that come to mind.

Error when trying to create "datasources"

Brand new at this !

I'm running VB 2005 express edition installed from full MS download which included the SQL2005 express server V9.00.1116

Have used the Video tutorial (video 8 & 9) to create a database and have followed instructiions faithfully

Problem.

From the Data / Add New Datasource menu everything proceeds ok - that is a "dataset.xsd" file is created but then I get an error message

" Could not get type information for .........myfilename dataset "

and so the process is not completed properly and a datasource is not created.

I'm unsure what the type information is and have been unsuccesful turning up anything from the help files or forum so hoping someone can maybe tell me whats happening and how to fix this.

Thanks

I also ran into this problem and got it solved by removing the connection strings in 'My Project - Settings'. I hope this also works for you.

Harmen.|||

Thanks for that idea

For the record had trouble removing strings however -

My problems have been solved by accident when I created a new windows user account and ran VB express from there. I believe the problem was to do with the connection address because my system name has an " & " in the name(stupid me when I set up Windows XP ) the ampersand maybe an illegal character in a path name.

Here's the full path i used

Data Source=.\SQLEXPRESS;AttachDbFilename="C:\Documents and Settings\TB&MA\My Documents\Visual Studio 2005\Projects\MyDataBase\MyDataBase\Database1.mdf";Integrated Security=True;User Instance=True

I think this why running it from a new user account worked ok as the connection string would have new directory path name

Thanks again

sql

Error when trying to create "datasources"

Brand new at this !

I'm running VB 2005 express edition installed from full MS download which included the SQL2005 express server V9.00.1116

Have used the Video tutorial (video 8 & 9) to create a database and have followed instructiions faithfully

Problem.

From the Data / Add New Datasource menu everything proceeds ok - that is a "dataset.xsd" file is created but then I get an error message

" Could not get type information for .........myfilename dataset "

and so the process is not completed properly and a datasource is not created.

I'm unsure what the type information is and have been unsuccesful turning up anything from the help files or forum so hoping someone can maybe tell me whats happening and how to fix this.

Thanks

I also ran into this problem and got it solved by removing the connection strings in 'My Project - Settings'. I hope this also works for you.

Harmen.
|||

Thanks for that idea

For the record had trouble removing strings however -

My problems have been solved by accident when I created a new windows user account and ran VB express from there. I believe the problem was to do with the connection address because my system name has an " & " in the name(stupid me when I set up Windows XP ) the ampersand maybe an illegal character in a path name.

Here's the full path i used

Data Source=.\SQLEXPRESS;AttachDbFilename="C:\Documents and Settings\TB&MA\My Documents\Visual Studio 2005\Projects\MyDataBase\MyDataBase\Database1.mdf";Integrated Security=True;User Instance=True

I think this why running it from a new user account worked ok as the connection string would have new directory path name

Thanks again

Error when trying to access http://localhost/Reports

Hello,

I just recently installed SQL Express 2005 Reporting Services on a new OS "Vista Ultimate". I used for reference the video # 10 Getting Started with Reporting Services found in

SQL Server Videos - SQL Server 2005 Express for Beginners. I was finally able to install everthing, including creating a new project using Report Server Project Wizard.

The only problem I recieve when fallowing the video is opening IE and enteringhttp://localhost/Reports. What I recieve is an error"The report server is not responding. Verify that the report server is running and can be accessed from this computer."

I checked to see if the SQL Server Reporting Services was running which it was. I also checked the Default Web Site in IIS manger which was also running.

Any help would be much appreciated

Regards

Karl

May be the problem is just configuration check this link it might help you

http://www.microsoft.com/technet/prodtechnol/sql/2005/usingssrswithsqlexpress.mspx

Error when running RedGate SQL Backup Job in SQL Server 2005

I have 4 SQL Server 2005 production servers that I installed RedGate SQL Bac
k
up on. All but one run fine. The one that doesn't I get the below error.
Executed as user : AD-DomainName\UserName. SQL Backup job failed with
exitcode 0 SQL Error code 18456[SQLState 42000] (Error 50000) The step f
ailed.
The back up is backing up to the AD server which is different than the
server the job runs on. It is a shared folder on the AD and the permissions
grant the owner of the job Full Access.
I do not know what else to do with this issue. It mirrors the other 3 that
work fine.
Any and all help is appreciated.
-ChrisChris,
SQL Server caches login information from active directory. The one
troublesome machine has apparently cached out of date AD information. In
David Grey's BLOG he discusses a similar problem (not with Red Gate) that
may help you resolve.
http://www.codefounders.com/communi...entication.aspx
RLF
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:2B7A5543-C258-4BA2-8CF4-BF2A7F4F1434@.microsoft.com...
>I have 4 SQL Server 2005 production servers that I installed RedGate SQL
>Back
> up on. All but one run fine. The one that doesn't I get the below error.
> Executed as user : AD-DomainName\UserName. SQL Backup job failed with
> exitcode 0 SQL Error code 18456[SQLState 42000] (Error 50000) The step
> failed.
> The back up is backing up to the AD server which is different than the
> server the job runs on. It is a shared folder on the AD and the
> permissions
> grant the owner of the job Full Access.
> I do not know what else to do with this issue. It mirrors the other 3 that
> work fine.
> Any and all help is appreciated.
> -Chris
>

Error when opening Maintenance Plan in SQL 2000

I've recently installed SQL 2000 on a new server. Migrated production
databases and data from old SQL 6.5.
Everything checks out OK applications work fine, all data
came over no problem. However... when I try to open or create a
database maintenance plan I get is error:
Microsoft SQL-DMO (ODBC SQLState: 42S22)
Error 207: Invalid column name 'category_id'.
Invalid column name 'netsend_address'.
Invalid column name 'last_netsend_date'.
Invalid column name 'last_netsend_time'.
these colune names do not exist, do I need to create them and if so,
which table do they need to be in? Any help is greatly appreciated. Thanks
HI;
Columns mentioned below are in the sysoperators table in msdb database
netsend_address nvarchar 100 NOT NULL
last_netsend_date int 4 NULL
last_netsend_time int 4 NULL
category_id int 4 NULL
IT Looks to me that something happend to your msdb database.
Do you have a backup to restore it from before migration?
Danijel Novak
"Lisa Hoffman" <LisaHoffman@.reish.com> wrote in message
news:OH0vej2BGHA.3584@.TK2MSFTNGP11.phx.gbl...
> I've recently installed SQL 2000 on a new server. Migrated production
> databases and data from old SQL 6.5.
> Everything checks out OK applications work fine, all data
> came over no problem. However... when I try to open or create a
> database maintenance plan I get is error:
> Microsoft SQL-DMO (ODBC SQLState: 42S22)
> Error 207: Invalid column name 'category_id'.
> Invalid column name 'netsend_address'.
> Invalid column name 'last_netsend_date'.
> Invalid column name 'last_netsend_time'.
> these colune names do not exist, do I need to create them and if so, which
> table do they need to be in? Any help is greatly appreciated. Thanks
>
|||Hi Lisa
You may want to run a DBCC CHECKCATALOG or DBCC CHECKDB on your MSDB database.
If you need to restore MSDB check out
http://msdn.microsoft.com/library/de...kprst_2w1f.asp
John
"Lisa Hoffman" wrote:

> I've recently installed SQL 2000 on a new server. Migrated production
> databases and data from old SQL 6.5.
> Everything checks out OK applications work fine, all data
> came over no problem. However... when I try to open or create a
> database maintenance plan I get is error:
> Microsoft SQL-DMO (ODBC SQLState: 42S22)
> Error 207: Invalid column name 'category_id'.
> Invalid column name 'netsend_address'.
> Invalid column name 'last_netsend_date'.
> Invalid column name 'last_netsend_time'.
> these colune names do not exist, do I need to create them and if so,
> which table do they need to be in? Any help is greatly appreciated. Thanks
>
>
|||The MS article states "The model and msdb databases can only be restored
from backups created on a Microsoft? SQL Server? 2000 server. Restore of
backups of these databases made on SQL Server version 7.0 or earlier is
not supported."
This was a migration from 6.5 (and I do not have access to this db
anymore). Any other suggestions?
John Bell wrote:
[vbcol=seagreen]
> Hi Lisa
> You may want to run a DBCC CHECKCATALOG or DBCC CHECKDB on your MSDB database.
> If you need to restore MSDB check out
> http://msdn.microsoft.com/library/de...kprst_2w1f.asp
> John
> "Lisa Hoffman" wrote:
>
|||Hi
I would assume that MSDB was backed up after your installation and therefore
it could be resumed to it's previous state? Any jobs etc should be reviewed
and manually re-created.
John
"Lisa Hoffman" wrote:

> The MS article states "The model and msdb databases can only be restored
> from backups created on a Microsoft? SQL Server? 2000 server. Restore of
> backups of these databases made on SQL Server version 7.0 or earlier is
> not supported."
> This was a migration from 6.5 (and I do not have access to this db
> anymore). Any other suggestions?
> John Bell wrote:
>

Error when opening Maintenance Plan in SQL 2000

I've recently installed SQL 2000 on a new server. Migrated production
databases and data from old SQL 6.5.
Everything checks out OK applications work fine, all data
came over no problem. However... when I try to open or create a
database maintenance plan I get is error:
Microsoft SQL-DMO (ODBC SQLState: 42S22)
Error 207: Invalid column name 'category_id'.
Invalid column name 'netsend_address'.
Invalid column name 'last_netsend_date'.
Invalid column name 'last_netsend_time'.
these colune names do not exist, do I need to create them and if so,
which table do they need to be in? Any help is greatly appreciated. ThanksHI;
Columns mentioned below are in the sysoperators table in msdb database
netsend_address nvarchar 100 NOT NULL
last_netsend_date int 4 NULL
last_netsend_time int 4 NULL
category_id int 4 NULL
IT Looks to me that something happend to your msdb database.
Do you have a backup to restore it from before migration?
Danijel Novak
"Lisa Hoffman" <LisaHoffman@.reish.com> wrote in message
news:OH0vej2BGHA.3584@.TK2MSFTNGP11.phx.gbl...
> I've recently installed SQL 2000 on a new server. Migrated production
> databases and data from old SQL 6.5.
> Everything checks out OK applications work fine, all data
> came over no problem. However... when I try to open or create a
> database maintenance plan I get is error:
> Microsoft SQL-DMO (ODBC SQLState: 42S22)
> Error 207: Invalid column name 'category_id'.
> Invalid column name 'netsend_address'.
> Invalid column name 'last_netsend_date'.
> Invalid column name 'last_netsend_time'.
> these colune names do not exist, do I need to create them and if so, which
> table do they need to be in? Any help is greatly appreciated. Thanks
>|||Hi Lisa
You may want to run a DBCC CHECKCATALOG or DBCC CHECKDB on your MSDB databas
e.
If you need to restore MSDB check out
http://msdn.microsoft.com/library/d... />
t_2w1f.asp
John
"Lisa Hoffman" wrote:

> I've recently installed SQL 2000 on a new server. Migrated production
> databases and data from old SQL 6.5.
> Everything checks out OK applications work fine, all data
> came over no problem. However... when I try to open or create a
> database maintenance plan I get is error:
> Microsoft SQL-DMO (ODBC SQLState: 42S22)
> Error 207: Invalid column name 'category_id'.
> Invalid column name 'netsend_address'.
> Invalid column name 'last_netsend_date'.
> Invalid column name 'last_netsend_time'.
> these colune names do not exist, do I need to create them and if so,
> which table do they need to be in? Any help is greatly appreciated. Than
ks
>
>|||The MS article states "The model and msdb databases can only be restored
from backups created on a Microsoft? SQL Server? 2000 server. Restore of
backups of these databases made on SQL Server version 7.0 or earlier is
not supported."
This was a migration from 6.5 (and I do not have access to this db
anymore). Any other suggestions?
John Bell wrote:
[vbcol=seagreen]
> Hi Lisa
> You may want to run a DBCC CHECKCATALOG or DBCC CHECKDB on your MSDB datab
ase.
> If you need to restore MSDB check out
> http://msdn.microsoft.com/library/d...>
rst_2w1f.asp
> John
> "Lisa Hoffman" wrote:
>|||Hi
I would assume that MSDB was backed up after your installation and therefore
it could be resumed to it's previous state? Any jobs etc should be reviewed
and manually re-created.
John
"Lisa Hoffman" wrote:

> The MS article states "The model and msdb databases can only be restored
> from backups created on a Microsoft? SQL Server? 2000 server. Restore o
f
> backups of these databases made on SQL Server version 7.0 or earlier is
> not supported."
> This was a migration from 6.5 (and I do not have access to this db
> anymore). Any other suggestions?
> John Bell wrote:
>
>

Error when opening Maintenance Plan in SQL 2000

I've recently installed SQL 2000 on a new server. Migrated production
databases and data from old SQL 6.5.
Everything checks out OK applications work fine, all data
came over no problem. However... when I try to open or create a
database maintenance plan I get is error:
Microsoft SQL-DMO (ODBC SQLState: 42S22)
Error 207: Invalid column name 'category_id'.
Invalid column name 'netsend_address'.
Invalid column name 'last_netsend_date'.
Invalid column name 'last_netsend_time'.
these colune names do not exist, do I need to create them and if so,
which table do they need to be in? Any help is greatly appreciated. ThanksHI;
Columns mentioned below are in the sysoperators table in msdb database
netsend_address nvarchar 100 NOT NULL
last_netsend_date int 4 NULL
last_netsend_time int 4 NULL
category_id int 4 NULL
IT Looks to me that something happend to your msdb database.
Do you have a backup to restore it from before migration?
--
Danijel Novak
"Lisa Hoffman" <LisaHoffman@.reish.com> wrote in message
news:OH0vej2BGHA.3584@.TK2MSFTNGP11.phx.gbl...
> I've recently installed SQL 2000 on a new server. Migrated production
> databases and data from old SQL 6.5.
> Everything checks out OK applications work fine, all data
> came over no problem. However... when I try to open or create a
> database maintenance plan I get is error:
> Microsoft SQL-DMO (ODBC SQLState: 42S22)
> Error 207: Invalid column name 'category_id'.
> Invalid column name 'netsend_address'.
> Invalid column name 'last_netsend_date'.
> Invalid column name 'last_netsend_time'.
> these colune names do not exist, do I need to create them and if so, which
> table do they need to be in? Any help is greatly appreciated. Thanks
>|||Hi Lisa
You may want to run a DBCC CHECKCATALOG or DBCC CHECKDB on your MSDB database.
If you need to restore MSDB check out
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_bkprst_2w1f.asp
John
"Lisa Hoffman" wrote:
> I've recently installed SQL 2000 on a new server. Migrated production
> databases and data from old SQL 6.5.
> Everything checks out OK applications work fine, all data
> came over no problem. However... when I try to open or create a
> database maintenance plan I get is error:
> Microsoft SQL-DMO (ODBC SQLState: 42S22)
> Error 207: Invalid column name 'category_id'.
> Invalid column name 'netsend_address'.
> Invalid column name 'last_netsend_date'.
> Invalid column name 'last_netsend_time'.
> these colune names do not exist, do I need to create them and if so,
> which table do they need to be in? Any help is greatly appreciated. Thanks
>
>|||The MS article states "The model and msdb databases can only be restored
from backups created on a Microsoft® SQL Server� 2000 server. Restore of
backups of these databases made on SQL Server version 7.0 or earlier is
not supported."
This was a migration from 6.5 (and I do not have access to this db
anymore). Any other suggestions?
John Bell wrote:
> Hi Lisa
> You may want to run a DBCC CHECKCATALOG or DBCC CHECKDB on your MSDB database.
> If you need to restore MSDB check out
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_bkprst_2w1f.asp
> John
> "Lisa Hoffman" wrote:
>
>>I've recently installed SQL 2000 on a new server. Migrated production
>>databases and data from old SQL 6.5.
>>Everything checks out OK applications work fine, all data
>>came over no problem. However... when I try to open or create a
>>database maintenance plan I get is error:
>>Microsoft SQL-DMO (ODBC SQLState: 42S22)
>>Error 207: Invalid column name 'category_id'.
>>Invalid column name 'netsend_address'.
>>Invalid column name 'last_netsend_date'.
>>Invalid column name 'last_netsend_time'.
>>these colune names do not exist, do I need to create them and if so,
>>which table do they need to be in? Any help is greatly appreciated. Thanks
>>|||Hi
I would assume that MSDB was backed up after your installation and therefore
it could be resumed to it's previous state? Any jobs etc should be reviewed
and manually re-created.
John
"Lisa Hoffman" wrote:
> The MS article states "The model and msdb databases can only be restored
> from backups created on a Microsoft® SQL Server� 2000 server. Restore of
> backups of these databases made on SQL Server version 7.0 or earlier is
> not supported."
> This was a migration from 6.5 (and I do not have access to this db
> anymore). Any other suggestions?
> John Bell wrote:
> > Hi Lisa
> >
> > You may want to run a DBCC CHECKCATALOG or DBCC CHECKDB on your MSDB database.
> >
> > If you need to restore MSDB check out
> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_bkprst_2w1f.asp
> >
> > John
> >
> > "Lisa Hoffman" wrote:
> >
> >
> >>I've recently installed SQL 2000 on a new server. Migrated production
> >>databases and data from old SQL 6.5.
> >>Everything checks out OK applications work fine, all data
> >>came over no problem. However... when I try to open or create a
> >>database maintenance plan I get is error:
> >>
> >>Microsoft SQL-DMO (ODBC SQLState: 42S22)
> >>Error 207: Invalid column name 'category_id'.
> >>Invalid column name 'netsend_address'.
> >>Invalid column name 'last_netsend_date'.
> >>Invalid column name 'last_netsend_time'.
> >>
> >>these colune names do not exist, do I need to create them and if so,
> >>which table do they need to be in? Any help is greatly appreciated. Thanks
> >>
> >>
> >>
>

Error when open Report Manager

RS is installed on the same server with the WebServer. I run this from a
domain network PC:
http://WebServerName/Reports/Pages/Folder.aspx
and I receive this error:
The request failed with HTTP status 401: Unauthorized.
What I checked:
1.On the WebServer go in IIS , then Default Web Site, then Reports, then
Proprieties, then Security and ONLY Integrated Windows Authentication is
checked
2. The save as above for ReportService under Default Web Site
3. Open Windows Explorer on the Web Server and go to C:\Program
Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer where
ReportService.asmx file is located. In the same folder have a look in
web.config file and:
<authentication mode="Windows" />
<identity impersonate="false" />
4 IIS is version 6
5. Web Server is Windows 2003
6. Went in Logs for RS and this is what I found:
w3wp!ui!1860!17/02/2006-13:20:44:: e ERROR: The request failed with HTTP
status 401: Unauthorized.
w3wp!ui!1acc!17/02/2006-13:20:44:: e ERROR: The request failed with HTTP
status 401: Unauthorized.
w3wp!ui!1acc!17/02/2006-13:20:45:: e ERROR: HTTP status code --> 500
--Details--
System.Net.WebException: The request failed with HTTP status 401:
Unauthorized.
at
System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage
message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)
at
Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
at Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
at Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
at
Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
methodname)
at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
at
Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
level)
at Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
sender, EventArgs args)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Web.UI.Control.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain()
w3wp!ui!1860!17/02/2006-13:20:45:: e ERROR: HTTP status code --> 500
--Details--
7. Changed in IIS to use Anonymous access and then Report Manager opens
without error but there is no report there (only Home directory and that's
all).After working on this problem for a week, I found posting from Jonny W.
and it worked for me.
If anyone else is having the same problem this KB article applies:
http://support.microsoft.com/default.aspx/kb/896861/en-us
Eddy wrote:
> RS is installed on the same server with the WebServer. I run this from a
> domain network PC:
> http://WebServerName/Reports/Pages/Folder.aspx
> and I receive this error:
> The request failed with HTTP status 401: Unauthorized.
> What I checked:
> 1.On the WebServer go in IIS , then Default Web Site, then Reports, then
> Proprieties, then Security and ONLY Integrated Windows Authentication is
> checked
> 2. The save as above for ReportService under Default Web Site
> 3. Open Windows Explorer on the Web Server and go to C:\Program
> Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer where
> ReportService.asmx file is located. In the same folder have a look in
> web.config file and:
> <authentication mode="Windows" />
> <identity impersonate="false" />
> 4 IIS is version 6
> 5. Web Server is Windows 2003
> 6. Went in Logs for RS and this is what I found:
> w3wp!ui!1860!17/02/2006-13:20:44:: e ERROR: The request failed with HTTP
> status 401: Unauthorized.
> w3wp!ui!1acc!17/02/2006-13:20:44:: e ERROR: The request failed with HTTP
> status 401: Unauthorized.
> w3wp!ui!1acc!17/02/2006-13:20:45:: e ERROR: HTTP status code --> 500
> --Details--
> System.Net.WebException: The request failed with HTTP status 401:
> Unauthorized.
> at
> System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage
> message, WebResponse response, Stream responseStream, Boolean asyncCall)
> at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> methodName, Object[] parameters)
> at
> Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
> at Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
> at Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
> at
> Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
> methodname)
> at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
> at
> Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
> level)
> at Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
> sender, EventArgs args)
> at System.EventHandler.Invoke(Object sender, EventArgs e)
> at System.Web.UI.Control.OnInit(EventArgs e)
> at System.Web.UI.Control.InitRecursive(Control namingContainer)
> at System.Web.UI.Page.ProcessRequestMain()
> w3wp!ui!1860!17/02/2006-13:20:45:: e ERROR: HTTP status code --> 500
> --Details--
> 7. Changed in IIS to use Anonymous access and then Report Manager opens
> without error but there is no report there (only Home directory and that's
> all).

error when migrating cubes

i have analysis server 2000 on my server and have just installed a new instance of analysis server 2005. i tried the migration wizard but get this error:

Unable to cast COM object of type 'System.__ComObject' to interface type 'Interop.Dso.IDbGroup90Ex'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{CE55E9E9-9597-4214-B21F-30C7683467B1}' failed due
to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).

what does that mean? i have no idea how to debug that and google has yeilded no results.

Try installing "Microsoft SQL Server 2005 Backward Compatibility Components " package from http://www.microsoft.com/downloads/details.aspx?familyid=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en

If that wouldnt help, try re-installing AS2005.

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

Error when installing SQL server 200 on SBS 2003 in Windows Small Business Server 2003

Hi,
I am trying to install SQL 2000 sevrer on my SBS 2003 server (I own the SBS
2003 server Premium).
I installed the OS lately and made all the Microsoft update.
I am now trying to install the SQL 2000 server and get this error message:
(It is the english translation of what I get on my screen)
Error message: "A previous installation program created operation files
waiting for Installtion on your computer. You have to reboot it before
executing the installation."
Of course I rebooted my server, but nothing happened.
Any idea of what to do ?
Thank you for your help
Did you try installing again after the reboot? Was there an error code
listed?
From KB Article 257716:
Q. What should I do if the installation of SQL Server 2000 is unsuccessful?
A. If you have an unsuccessful installation, you can examine two files to
help determine what went wrong. The Sqlstp.log file, which is located in the
Windows directory, gives detailed information on what setup is doing and
contains all errors encountered during setup. Reviewing this file will give
you a better understanding of where setup fails and why.
During the configuration portion of setup, SQL Server setup runs an
application called Cnfgsvr.exe to configure the SQL Server. This application
starts SQL Server, connects to it, and then runs the initial installation
scripts. Any error encountered during this process is also written to the
Sqlstp.log file; however, you should also review the SQL Server error log,
named "Errorlog" with no file extension, located by default in the Program
Files\Microsoft SQL Server\Mssql\Log directory. This error log contains
errors that SQL Server encounters when setup attempts to start SQL Server,
which may provide further insight into the failure.
If you cannot determine the cause of the Setup failure, save the two files
just mentioned and call Microsoft Product Support Services (PSS) to speak to
a SQL Server Support Professional who will help you to resolve your problem.
Note that when the Setup application fails, it rolls back all changes to the
file system, which includes removing any copied files and changes that were
made to the registry.
HTH
Jerry
"Alambiki" <alambiki@.yahoo.com> wrote in message
news:dj5qnl$ok9$1@.reader1.imaginet.fr...
> Hi,
> I am trying to install SQL 2000 sevrer on my SBS 2003 server (I own the
> SBS
> 2003 server Premium).
> I installed the OS lately and made all the Microsoft update.
> I am now trying to install the SQL 2000 server and get this error message:
> (It is the english translation of what I get on my screen)
> Error message: "A previous installation program created operation files
> waiting for Installtion on your computer. You have to reboot it before
> executing the installation."
> Of course I rebooted my server, but nothing happened.
> Any idea of what to do ?
> Thank you for your help
>
|||Yes I tried to reinstall after reboot.
I found the Sqlstp.log file, but am not able to understand it.
If someone has an idea...
"Jerry Spivey" <jspivey@.vestas-awt.com> a crit dans le message de news:
enXaUuM1FHA.1264@.tk2msftngp13.phx.gbl...
> Did you try installing again after the reboot? Was there an error code
> listed?
> From KB Article 257716:
> Q. What should I do if the installation of SQL Server 2000 is
> unsuccessful?
> A. If you have an unsuccessful installation, you can examine two files to
> help determine what went wrong. The Sqlstp.log file, which is located in
> the Windows directory, gives detailed information on what setup is doing
> and contains all errors encountered during setup. Reviewing this file will
> give you a better understanding of where setup fails and why.
> During the configuration portion of setup, SQL Server setup runs an
> application called Cnfgsvr.exe to configure the SQL Server. This
> application starts SQL Server, connects to it, and then runs the initial
> installation scripts. Any error encountered during this process is also
> written to the Sqlstp.log file; however, you should also review the SQL
> Server error log, named "Errorlog" with no file extension, located by
> default in the Program Files\Microsoft SQL Server\Mssql\Log directory.
> This error log contains errors that SQL Server encounters when setup
> attempts to start SQL Server, which may provide further insight into the
> failure.
> If you cannot determine the cause of the Setup failure, save the two files
> just mentioned and call Microsoft Product Support Services (PSS) to speak
> to a SQL Server Support Professional who will help you to resolve your
> problem. Note that when the Setup application fails, it rolls back all
> changes to the file system, which includes removing any copied files and
> changes that were made to the registry.
>
> HTH
> Jerry
> "Alambiki" <alambiki@.yahoo.com> wrote in message
> news:dj5qnl$ok9$1@.reader1.imaginet.fr...
>
|||What were the last few successful entries? Do you have an installation that
WAS successful that you can compare it to?
"aLAMBIKI" <alambiki@.yahoo.com> wrote in message
news:4356ae9a$0$4336$626a54ce@.news.free.fr...
> Yes I tried to reinstall after reboot.
> I found the Sqlstp.log file, but am not able to understand it.
> If someone has an idea...
> "Jerry Spivey" <jspivey@.vestas-awt.com> a crit dans le message de news:
> enXaUuM1FHA.1264@.tk2msftngp13.phx.gbl...
>
|||I already installed SBS + SQL on this server. It is the second time I
install it on this server. The only thing that changes is that I updated
with the latest ms update + installed symantec lifestate...
here is the log of SQLstp.log
19:00:30 Begin Setup
19:00:30 8.00.194
19:00:30 Mode = Normal
19:00:30 ModeType = NORMAL
19:00:30 GetDefinitionEx returned: 0, Extended: 0x0
19:00:30 ValueFTS returned: 1
19:00:30 ValuePID returned: 1
19:00:30 ValueLic returned: 1
19:00:30 System: Small Business Server
19:00:30 SQL Server ProductType: Standard Edition [0x2]
19:00:30 Begin Action: SetupInitialize
19:00:30 End Action SetupInitialize
19:00:30 Begin Action: SetupInstall
19:00:30 Reading Software\Microsoft\Windows\CurrentVersion\CommonFi lesDir
...
19:00:30 CommonFilesDir=C:\Program Files\Fichiers communs
19:00:30 Windows Directory=C:\WINDOWS\
19:00:30 Program Files=C:\Program Files\
19:00:30 TEMPDIR=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\
19:00:30 Begin Action: SetupInstall
19:00:30 Begin Action: CheckFixedRequirements
19:00:30 Platform ID: 0xf000
19:00:30 Version: 5.2.3790
19:00:30 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.3790.2523
19:00:31 End Action: CheckFixedRequirements
19:00:31 Begin Action: ShowDialogs
19:00:31 Initial Dialog Mask: 0x183000f7, Disable Back=0x1
19:00:31 Begin Action ShowDialogsHlpr: 0x1
19:00:31 Begin Action: DialogShowSdWelcome
19:00:32 End Action DialogShowSdWelcome
19:00:32 Dialog 0x1 returned: 1
19:00:32 End Action ShowDialogsHlpr
19:00:32 ShowDialogsGetDialog returned: nCurrent=0x2,index=1
19:00:32 Begin Action ShowDialogsHlpr: 0x2
19:00:32 Begin Action: DialogShowSdMachineName
19:01:07 ShowDlgMachine returned: -1
19:01:07 ShowDlgMachine: GetLastError returned: 0
19:01:07 Opration russie.
19:01:07 End Action DialogShowSdMachineName
19:01:07 End Action ShowDialogs
19:01:07 Action CleanUpInstall:
19:01:07 StatsGenerate returned: 2
19:01:07 StatsGenerate (0x0,0x0,0xf000,0x0,1036,0,0x0,0x0,0,0,0
19:01:07 StatsGenerate -1,)
19:01:07 Installation Failed.
"Jerry Spivey" <jspivey@.vestas-awt.com> a crit dans le message de news:
OdVtGSP1FHA.560@.TK2MSFTNGP12.phx.gbl...
> What were the last few successful entries? Do you have an installation
> that WAS successful that you can compare it to?
> "aLAMBIKI" <alambiki@.yahoo.com> wrote in message
> news:4356ae9a$0$4336$626a54ce@.news.free.fr...
>
|||I'm sure one of the MS guys will jump in here somewhere and give you more
than I can. Can you remove the Symantic product as a test?
HTH
Jerry
"aLAMBIKI" <alambiki@.yahoo.com> wrote in message
news:4356c190$1$4337$626a54ce@.news.free.fr...
>I already installed SBS + SQL on this server. It is the second time I
>install it on this server. The only thing that changes is that I updated
>with the latest ms update + installed symantec lifestate...
> here is the log of SQLstp.log
> 19:00:30 Begin Setup
> 19:00:30 8.00.194
> 19:00:30 Mode = Normal
> 19:00:30 ModeType = NORMAL
> 19:00:30 GetDefinitionEx returned: 0, Extended: 0x0
> 19:00:30 ValueFTS returned: 1
> 19:00:30 ValuePID returned: 1
> 19:00:30 ValueLic returned: 1
> 19:00:30 System: Small Business Server
> 19:00:30 SQL Server ProductType: Standard Edition [0x2]
> 19:00:30 Begin Action: SetupInitialize
> 19:00:30 End Action SetupInitialize
> 19:00:30 Begin Action: SetupInstall
> 19:00:30 Reading Software\Microsoft\Windows\CurrentVersion\CommonFi lesDir
> ...
> 19:00:30 CommonFilesDir=C:\Program Files\Fichiers communs
> 19:00:30 Windows Directory=C:\WINDOWS\
> 19:00:30 Program Files=C:\Program Files\
> 19:00:30 TEMPDIR=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\
> 19:00:30 Begin Action: SetupInstall
> 19:00:30 Begin Action: CheckFixedRequirements
> 19:00:30 Platform ID: 0xf000
> 19:00:30 Version: 5.2.3790
> 19:00:30 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.3790.2523
> 19:00:31 End Action: CheckFixedRequirements
> 19:00:31 Begin Action: ShowDialogs
> 19:00:31 Initial Dialog Mask: 0x183000f7, Disable Back=0x1
> 19:00:31 Begin Action ShowDialogsHlpr: 0x1
> 19:00:31 Begin Action: DialogShowSdWelcome
> 19:00:32 End Action DialogShowSdWelcome
> 19:00:32 Dialog 0x1 returned: 1
> 19:00:32 End Action ShowDialogsHlpr
> 19:00:32 ShowDialogsGetDialog returned: nCurrent=0x2,index=1
> 19:00:32 Begin Action ShowDialogsHlpr: 0x2
> 19:00:32 Begin Action: DialogShowSdMachineName
> 19:01:07 ShowDlgMachine returned: -1
> 19:01:07 ShowDlgMachine: GetLastError returned: 0
> 19:01:07 Opration russie.
> 19:01:07 End Action DialogShowSdMachineName
> 19:01:07 End Action ShowDialogs
> 19:01:07 Action CleanUpInstall:
> 19:01:07 StatsGenerate returned: 2
> 19:01:07 StatsGenerate (0x0,0x0,0xf000,0x0,1036,0,0x0,0x0,0,0,0
> 19:01:07 StatsGenerate -1,)
> 19:01:07 Installation Failed.
>
> "Jerry Spivey" <jspivey@.vestas-awt.com> a crit dans le message de news:
> OdVtGSP1FHA.560@.TK2MSFTNGP12.phx.gbl...
>

Error when installing SQL server 200 on SBS 2003 in Windows Small Business Server 2003

Hi,
I am trying to install SQL 2000 sevrer on my SBS 2003 server (I own the SBS
2003 server Premium).
I installed the OS lately and made all the Microsoft update.
I am now trying to install the SQL 2000 server and get this error message:
(It is the english translation of what I get on my screen)
Error message: "A previous installation program created operation files
waiting for Installtion on your computer. You have to reboot it before
executing the installation."
Of course I rebooted my server, but nothing happened.
Any idea of what to do ?
Thank you for your helpDid you try installing again after the reboot? Was there an error code
listed?
From KB Article 257716:
Q. What should I do if the installation of SQL Server 2000 is unsuccessful?
A. If you have an unsuccessful installation, you can examine two files to
help determine what went wrong. The Sqlstp.log file, which is located in the
Windows directory, gives detailed information on what setup is doing and
contains all errors encountered during setup. Reviewing this file will give
you a better understanding of where setup fails and why.
During the configuration portion of setup, SQL Server setup runs an
application called Cnfgsvr.exe to configure the SQL Server. This application
starts SQL Server, connects to it, and then runs the initial installation
scripts. Any error encountered during this process is also written to the
Sqlstp.log file; however, you should also review the SQL Server error log,
named "Errorlog" with no file extension, located by default in the Program
Files\Microsoft SQL Server\Mssql\Log directory. This error log contains
errors that SQL Server encounters when setup attempts to start SQL Server,
which may provide further insight into the failure.
If you cannot determine the cause of the Setup failure, save the two files
just mentioned and call Microsoft Product Support Services (PSS) to speak to
a SQL Server Support Professional who will help you to resolve your problem.
Note that when the Setup application fails, it rolls back all changes to the
file system, which includes removing any copied files and changes that were
made to the registry.
HTH
Jerry
"Alambiki" <alambiki@.yahoo.com> wrote in message
news:dj5qnl$ok9$1@.reader1.imaginet.fr...
> Hi,
> I am trying to install SQL 2000 sevrer on my SBS 2003 server (I own the
> SBS
> 2003 server Premium).
> I installed the OS lately and made all the Microsoft update.
> I am now trying to install the SQL 2000 server and get this error message:
> (It is the english translation of what I get on my screen)
> Error message: "A previous installation program created operation files
> waiting for Installtion on your computer. You have to reboot it before
> executing the installation."
> Of course I rebooted my server, but nothing happened.
> Any idea of what to do ?
> Thank you for your help
>|||Yes I tried to reinstall after reboot.
I found the Sqlstp.log file, but am not able to understand it.
If someone has an idea...
"Jerry Spivey" <jspivey@.vestas-awt.com> a crit dans le message de news:
enXaUuM1FHA.1264@.tk2msftngp13.phx.gbl...
> Did you try installing again after the reboot? Was there an error code
> listed?
> From KB Article 257716:
> Q. What should I do if the installation of SQL Server 2000 is
> unsuccessful?
> A. If you have an unsuccessful installation, you can examine two files to
> help determine what went wrong. The Sqlstp.log file, which is located in
> the Windows directory, gives detailed information on what setup is doing
> and contains all errors encountered during setup. Reviewing this file will
> give you a better understanding of where setup fails and why.
> During the configuration portion of setup, SQL Server setup runs an
> application called Cnfgsvr.exe to configure the SQL Server. This
> application starts SQL Server, connects to it, and then runs the initial
> installation scripts. Any error encountered during this process is also
> written to the Sqlstp.log file; however, you should also review the SQL
> Server error log, named "Errorlog" with no file extension, located by
> default in the Program Files\Microsoft SQL Server\Mssql\Log directory.
> This error log contains errors that SQL Server encounters when setup
> attempts to start SQL Server, which may provide further insight into the
> failure.
> If you cannot determine the cause of the Setup failure, save the two files
> just mentioned and call Microsoft Product Support Services (PSS) to speak
> to a SQL Server Support Professional who will help you to resolve your
> problem. Note that when the Setup application fails, it rolls back all
> changes to the file system, which includes removing any copied files and
> changes that were made to the registry.
>
> HTH
> Jerry
> "Alambiki" <alambiki@.yahoo.com> wrote in message
> news:dj5qnl$ok9$1@.reader1.imaginet.fr...
>|||What were the last few successful entries? Do you have an installation that
WAS successful that you can compare it to?
"aLAMBIKI" <alambiki@.yahoo.com> wrote in message
news:4356ae9a$0$4336$626a54ce@.news.free.fr...
> Yes I tried to reinstall after reboot.
> I found the Sqlstp.log file, but am not able to understand it.
> If someone has an idea...
> "Jerry Spivey" <jspivey@.vestas-awt.com> a crit dans le message de news:
> enXaUuM1FHA.1264@.tk2msftngp13.phx.gbl...
>|||I already installed SBS + SQL on this server. It is the second time I
install it on this server. The only thing that changes is that I updated
with the latest ms update + installed symantec lifestate...
here is the log of SQLstp.log
19:00:30 Begin Setup
19:00:30 8.00.194
19:00:30 Mode = Normal
19:00:30 ModeType = NORMAL
19:00:30 GetDefinitionEx returned: 0, Extended: 0x0
19:00:30 ValueFTS returned: 1
19:00:30 ValuePID returned: 1
19:00:30 ValueLic returned: 1
19:00:30 System: Small Business Server
19:00:30 SQL Server ProductType: Standard Edition [0x2]
19:00:30 Begin Action: SetupInitialize
19:00:30 End Action SetupInitialize
19:00:30 Begin Action: SetupInstall
19:00:30 Reading Software\Microsoft\Windows\CurrentVersio
n\CommonFilesDir
...
19:00:30 CommonFilesDir=C:\Program Files\Fichiers communs
19:00:30 Windows Directory=C:\WINDOWS\
19:00:30 Program Files=C:\Program Files\
19:00:30 TEMPDIR=C:\DOCUME~1\ADMINI~1\LOCALS~1\Te
mp\1\
19:00:30 Begin Action: SetupInstall
19:00:30 Begin Action: CheckFixedRequirements
19:00:30 Platform ID: 0xf000
19:00:30 Version: 5.2.3790
19:00:30 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.3790.2523
19:00:31 End Action: CheckFixedRequirements
19:00:31 Begin Action: ShowDialogs
19:00:31 Initial Dialog Mask: 0x183000f7, Disable Back=0x1
19:00:31 Begin Action ShowDialogsHlpr: 0x1
19:00:31 Begin Action: DialogShowSdWelcome
19:00:32 End Action DialogShowSdWelcome
19:00:32 Dialog 0x1 returned: 1
19:00:32 End Action ShowDialogsHlpr
19:00:32 ShowDialogsGetDialog returned: nCurrent=0x2,index=1
19:00:32 Begin Action ShowDialogsHlpr: 0x2
19:00:32 Begin Action: DialogShowSdMachineName
19:01:07 ShowDlgMachine returned: -1
19:01:07 ShowDlgMachine: GetLastError returned: 0
19:01:07 Opration russie.
19:01:07 End Action DialogShowSdMachineName
19:01:07 End Action ShowDialogs
19:01:07 Action CleanUpInstall:
19:01:07 StatsGenerate returned: 2
19:01:07 StatsGenerate (0x0,0x0,0xf000,0x0,1036,0,0x0,0x0,0,0,0
19:01:07 StatsGenerate -1,)
19:01:07 Installation Failed.
"Jerry Spivey" <jspivey@.vestas-awt.com> a crit dans le message de news:
OdVtGSP1FHA.560@.TK2MSFTNGP12.phx.gbl...
> What were the last few successful entries? Do you have an installation
> that WAS successful that you can compare it to?
> "aLAMBIKI" <alambiki@.yahoo.com> wrote in message
> news:4356ae9a$0$4336$626a54ce@.news.free.fr...
>|||I'm sure one of the MS guys will jump in here somewhere and give you more
than I can. Can you remove the Symantic product as a test?
HTH
Jerry
"aLAMBIKI" <alambiki@.yahoo.com> wrote in message
news:4356c190$1$4337$626a54ce@.news.free.fr...
>I already installed SBS + SQL on this server. It is the second time I
>install it on this server. The only thing that changes is that I updated
>with the latest ms update + installed symantec lifestate...
> here is the log of SQLstp.log
> 19:00:30 Begin Setup
> 19:00:30 8.00.194
> 19:00:30 Mode = Normal
> 19:00:30 ModeType = NORMAL
> 19:00:30 GetDefinitionEx returned: 0, Extended: 0x0
> 19:00:30 ValueFTS returned: 1
> 19:00:30 ValuePID returned: 1
> 19:00:30 ValueLic returned: 1
> 19:00:30 System: Small Business Server
> 19:00:30 SQL Server ProductType: Standard Edition [0x2]
> 19:00:30 Begin Action: SetupInitialize
> 19:00:30 End Action SetupInitialize
> 19:00:30 Begin Action: SetupInstall
> 19:00:30 Reading Software\Microsoft\Windows\CurrentVersio
n\CommonFilesDir
> ...
> 19:00:30 CommonFilesDir=C:\Program Files\Fichiers communs
> 19:00:30 Windows Directory=C:\WINDOWS\
> 19:00:30 Program Files=C:\Program Files\
> 19:00:30 TEMPDIR=C:\DOCUME~1\ADMINI~1\LOCALS~1\Te
mp\1\
> 19:00:30 Begin Action: SetupInstall
> 19:00:30 Begin Action: CheckFixedRequirements
> 19:00:30 Platform ID: 0xf000
> 19:00:30 Version: 5.2.3790
> 19:00:30 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.3790.2523
> 19:00:31 End Action: CheckFixedRequirements
> 19:00:31 Begin Action: ShowDialogs
> 19:00:31 Initial Dialog Mask: 0x183000f7, Disable Back=0x1
> 19:00:31 Begin Action ShowDialogsHlpr: 0x1
> 19:00:31 Begin Action: DialogShowSdWelcome
> 19:00:32 End Action DialogShowSdWelcome
> 19:00:32 Dialog 0x1 returned: 1
> 19:00:32 End Action ShowDialogsHlpr
> 19:00:32 ShowDialogsGetDialog returned: nCurrent=0x2,index=1
> 19:00:32 Begin Action ShowDialogsHlpr: 0x2
> 19:00:32 Begin Action: DialogShowSdMachineName
> 19:01:07 ShowDlgMachine returned: -1
> 19:01:07 ShowDlgMachine: GetLastError returned: 0
> 19:01:07 Opration russie.
> 19:01:07 End Action DialogShowSdMachineName
> 19:01:07 End Action ShowDialogs
> 19:01:07 Action CleanUpInstall:
> 19:01:07 StatsGenerate returned: 2
> 19:01:07 StatsGenerate (0x0,0x0,0xf000,0x0,1036,0,0x0,0x0,0,0,0
> 19:01:07 StatsGenerate -1,)
> 19:01:07 Installation Failed.
>
> "Jerry Spivey" <jspivey@.vestas-awt.com> a crit dans le message de news:
> OdVtGSP1FHA.560@.TK2MSFTNGP12.phx.gbl...
>

Error when installing SQL server 200 on SBS 2003 in Windows Small Business Server 2003

Hi,
I am trying to install SQL 2000 sevrer on my SBS 2003 server (I own the SBS
2003 server Premium).
I installed the OS lately and made all the Microsoft update.
I am now trying to install the SQL 2000 server and get this error message:
(It is the english translation of what I get on my screen)
Error message: "A previous installation program created operation files
waiting for Installtion on your computer. You have to reboot it before
executing the installation."
Of course I rebooted my server, but nothing happened.
Any idea of what to do ?
Thank you for your helpDid you try installing again after the reboot? Was there an error code
listed?
From KB Article 257716:
Q. What should I do if the installation of SQL Server 2000 is unsuccessful?
A. If you have an unsuccessful installation, you can examine two files to
help determine what went wrong. The Sqlstp.log file, which is located in the
Windows directory, gives detailed information on what setup is doing and
contains all errors encountered during setup. Reviewing this file will give
you a better understanding of where setup fails and why.
During the configuration portion of setup, SQL Server setup runs an
application called Cnfgsvr.exe to configure the SQL Server. This application
starts SQL Server, connects to it, and then runs the initial installation
scripts. Any error encountered during this process is also written to the
Sqlstp.log file; however, you should also review the SQL Server error log,
named "Errorlog" with no file extension, located by default in the Program
Files\Microsoft SQL Server\Mssql\Log directory. This error log contains
errors that SQL Server encounters when setup attempts to start SQL Server,
which may provide further insight into the failure.
If you cannot determine the cause of the Setup failure, save the two files
just mentioned and call Microsoft Product Support Services (PSS) to speak to
a SQL Server Support Professional who will help you to resolve your problem.
Note that when the Setup application fails, it rolls back all changes to the
file system, which includes removing any copied files and changes that were
made to the registry.
HTH
Jerry
"Alambiki" <alambiki@.yahoo.com> wrote in message
news:dj5qnl$ok9$1@.reader1.imaginet.fr...
> Hi,
> I am trying to install SQL 2000 sevrer on my SBS 2003 server (I own the
> SBS
> 2003 server Premium).
> I installed the OS lately and made all the Microsoft update.
> I am now trying to install the SQL 2000 server and get this error message:
> (It is the english translation of what I get on my screen)
> Error message: "A previous installation program created operation files
> waiting for Installtion on your computer. You have to reboot it before
> executing the installation."
> Of course I rebooted my server, but nothing happened.
> Any idea of what to do ?
> Thank you for your help
>|||Yes I tried to reinstall after reboot.
I found the Sqlstp.log file, but am not able to understand it.
If someone has an idea...
"Jerry Spivey" <jspivey@.vestas-awt.com> a écrit dans le message de news:
enXaUuM1FHA.1264@.tk2msftngp13.phx.gbl...
> Did you try installing again after the reboot? Was there an error code
> listed?
> From KB Article 257716:
> Q. What should I do if the installation of SQL Server 2000 is
> unsuccessful?
> A. If you have an unsuccessful installation, you can examine two files to
> help determine what went wrong. The Sqlstp.log file, which is located in
> the Windows directory, gives detailed information on what setup is doing
> and contains all errors encountered during setup. Reviewing this file will
> give you a better understanding of where setup fails and why.
> During the configuration portion of setup, SQL Server setup runs an
> application called Cnfgsvr.exe to configure the SQL Server. This
> application starts SQL Server, connects to it, and then runs the initial
> installation scripts. Any error encountered during this process is also
> written to the Sqlstp.log file; however, you should also review the SQL
> Server error log, named "Errorlog" with no file extension, located by
> default in the Program Files\Microsoft SQL Server\Mssql\Log directory.
> This error log contains errors that SQL Server encounters when setup
> attempts to start SQL Server, which may provide further insight into the
> failure.
> If you cannot determine the cause of the Setup failure, save the two files
> just mentioned and call Microsoft Product Support Services (PSS) to speak
> to a SQL Server Support Professional who will help you to resolve your
> problem. Note that when the Setup application fails, it rolls back all
> changes to the file system, which includes removing any copied files and
> changes that were made to the registry.
>
> HTH
> Jerry
> "Alambiki" <alambiki@.yahoo.com> wrote in message
> news:dj5qnl$ok9$1@.reader1.imaginet.fr...
>> Hi,
>> I am trying to install SQL 2000 sevrer on my SBS 2003 server (I own the
>> SBS
>> 2003 server Premium).
>> I installed the OS lately and made all the Microsoft update.
>> I am now trying to install the SQL 2000 server and get this error
>> message:
>> (It is the english translation of what I get on my screen)
>> Error message: "A previous installation program created operation files
>> waiting for Installtion on your computer. You have to reboot it before
>> executing the installation."
>> Of course I rebooted my server, but nothing happened.
>> Any idea of what to do ?
>> Thank you for your help
>|||What were the last few successful entries? Do you have an installation that
WAS successful that you can compare it to?
"aLAMBIKI" <alambiki@.yahoo.com> wrote in message
news:4356ae9a$0$4336$626a54ce@.news.free.fr...
> Yes I tried to reinstall after reboot.
> I found the Sqlstp.log file, but am not able to understand it.
> If someone has an idea...
> "Jerry Spivey" <jspivey@.vestas-awt.com> a écrit dans le message de news:
> enXaUuM1FHA.1264@.tk2msftngp13.phx.gbl...
>> Did you try installing again after the reboot? Was there an error code
>> listed?
>> From KB Article 257716:
>> Q. What should I do if the installation of SQL Server 2000 is
>> unsuccessful?
>> A. If you have an unsuccessful installation, you can examine two files to
>> help determine what went wrong. The Sqlstp.log file, which is located in
>> the Windows directory, gives detailed information on what setup is doing
>> and contains all errors encountered during setup. Reviewing this file
>> will give you a better understanding of where setup fails and why.
>> During the configuration portion of setup, SQL Server setup runs an
>> application called Cnfgsvr.exe to configure the SQL Server. This
>> application starts SQL Server, connects to it, and then runs the initial
>> installation scripts. Any error encountered during this process is also
>> written to the Sqlstp.log file; however, you should also review the SQL
>> Server error log, named "Errorlog" with no file extension, located by
>> default in the Program Files\Microsoft SQL Server\Mssql\Log directory.
>> This error log contains errors that SQL Server encounters when setup
>> attempts to start SQL Server, which may provide further insight into the
>> failure.
>> If you cannot determine the cause of the Setup failure, save the two
>> files just mentioned and call Microsoft Product Support Services (PSS) to
>> speak to a SQL Server Support Professional who will help you to resolve
>> your problem. Note that when the Setup application fails, it rolls back
>> all changes to the file system, which includes removing any copied files
>> and changes that were made to the registry.
>>
>> HTH
>> Jerry
>> "Alambiki" <alambiki@.yahoo.com> wrote in message
>> news:dj5qnl$ok9$1@.reader1.imaginet.fr...
>> Hi,
>> I am trying to install SQL 2000 sevrer on my SBS 2003 server (I own the
>> SBS
>> 2003 server Premium).
>> I installed the OS lately and made all the Microsoft update.
>> I am now trying to install the SQL 2000 server and get this error
>> message:
>> (It is the english translation of what I get on my screen)
>> Error message: "A previous installation program created operation files
>> waiting for Installtion on your computer. You have to reboot it before
>> executing the installation."
>> Of course I rebooted my server, but nothing happened.
>> Any idea of what to do ?
>> Thank you for your help
>>
>|||I already installed SBS + SQL on this server. It is the second time I
install it on this server. The only thing that changes is that I updated
with the latest ms update + installed symantec lifestate...
here is the log of SQLstp.log
19:00:30 Begin Setup
19:00:30 8.00.194
19:00:30 Mode = Normal
19:00:30 ModeType = NORMAL
19:00:30 GetDefinitionEx returned: 0, Extended: 0x0
19:00:30 ValueFTS returned: 1
19:00:30 ValuePID returned: 1
19:00:30 ValueLic returned: 1
19:00:30 System: Small Business Server
19:00:30 SQL Server ProductType: Standard Edition [0x2]
19:00:30 Begin Action: SetupInitialize
19:00:30 End Action SetupInitialize
19:00:30 Begin Action: SetupInstall
19:00:30 Reading Software\Microsoft\Windows\CurrentVersion\CommonFilesDir
...
19:00:30 CommonFilesDir=C:\Program Files\Fichiers communs
19:00:30 Windows Directory=C:\WINDOWS\
19:00:30 Program Files=C:\Program Files\
19:00:30 TEMPDIR=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\
19:00:30 Begin Action: SetupInstall
19:00:30 Begin Action: CheckFixedRequirements
19:00:30 Platform ID: 0xf000
19:00:30 Version: 5.2.3790
19:00:30 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.3790.2523
19:00:31 End Action: CheckFixedRequirements
19:00:31 Begin Action: ShowDialogs
19:00:31 Initial Dialog Mask: 0x183000f7, Disable Back=0x1
19:00:31 Begin Action ShowDialogsHlpr: 0x1
19:00:31 Begin Action: DialogShowSdWelcome
19:00:32 End Action DialogShowSdWelcome
19:00:32 Dialog 0x1 returned: 1
19:00:32 End Action ShowDialogsHlpr
19:00:32 ShowDialogsGetDialog returned: nCurrent=0x2,index=1
19:00:32 Begin Action ShowDialogsHlpr: 0x2
19:00:32 Begin Action: DialogShowSdMachineName
19:01:07 ShowDlgMachine returned: -1
19:01:07 ShowDlgMachine: GetLastError returned: 0
19:01:07 Opération réussie.
19:01:07 End Action DialogShowSdMachineName
19:01:07 End Action ShowDialogs
19:01:07 Action CleanUpInstall:
19:01:07 StatsGenerate returned: 2
19:01:07 StatsGenerate (0x0,0x0,0xf000,0x0,1036,0,0x0,0x0,0,0,0
19:01:07 StatsGenerate -1,)
19:01:07 Installation Failed.
"Jerry Spivey" <jspivey@.vestas-awt.com> a écrit dans le message de news:
OdVtGSP1FHA.560@.TK2MSFTNGP12.phx.gbl...
> What were the last few successful entries? Do you have an installation
> that WAS successful that you can compare it to?
> "aLAMBIKI" <alambiki@.yahoo.com> wrote in message
> news:4356ae9a$0$4336$626a54ce@.news.free.fr...
>> Yes I tried to reinstall after reboot.
>> I found the Sqlstp.log file, but am not able to understand it.
>> If someone has an idea...
>> "Jerry Spivey" <jspivey@.vestas-awt.com> a écrit dans le message de news:
>> enXaUuM1FHA.1264@.tk2msftngp13.phx.gbl...
>> Did you try installing again after the reboot? Was there an error code
>> listed?
>> From KB Article 257716:
>> Q. What should I do if the installation of SQL Server 2000 is
>> unsuccessful?
>> A. If you have an unsuccessful installation, you can examine two files
>> to help determine what went wrong. The Sqlstp.log file, which is located
>> in the Windows directory, gives detailed information on what setup is
>> doing and contains all errors encountered during setup. Reviewing this
>> file will give you a better understanding of where setup fails and why.
>> During the configuration portion of setup, SQL Server setup runs an
>> application called Cnfgsvr.exe to configure the SQL Server. This
>> application starts SQL Server, connects to it, and then runs the initial
>> installation scripts. Any error encountered during this process is also
>> written to the Sqlstp.log file; however, you should also review the SQL
>> Server error log, named "Errorlog" with no file extension, located by
>> default in the Program Files\Microsoft SQL Server\Mssql\Log directory.
>> This error log contains errors that SQL Server encounters when setup
>> attempts to start SQL Server, which may provide further insight into the
>> failure.
>> If you cannot determine the cause of the Setup failure, save the two
>> files just mentioned and call Microsoft Product Support Services (PSS)
>> to speak to a SQL Server Support Professional who will help you to
>> resolve your problem. Note that when the Setup application fails, it
>> rolls back all changes to the file system, which includes removing any
>> copied files and changes that were made to the registry.
>>
>> HTH
>> Jerry
>> "Alambiki" <alambiki@.yahoo.com> wrote in message
>> news:dj5qnl$ok9$1@.reader1.imaginet.fr...
>> Hi,
>> I am trying to install SQL 2000 sevrer on my SBS 2003 server (I own the
>> SBS
>> 2003 server Premium).
>> I installed the OS lately and made all the Microsoft update.
>> I am now trying to install the SQL 2000 server and get this error
>> message:
>> (It is the english translation of what I get on my screen)
>> Error message: "A previous installation program created operation files
>> waiting for Installtion on your computer. You have to reboot it before
>> executing the installation."
>> Of course I rebooted my server, but nothing happened.
>> Any idea of what to do ?
>> Thank you for your help
>>
>>
>|||I'm sure one of the MS guys will jump in here somewhere and give you more
than I can. Can you remove the Symantic product as a test?
HTH
Jerry
"aLAMBIKI" <alambiki@.yahoo.com> wrote in message
news:4356c190$1$4337$626a54ce@.news.free.fr...
>I already installed SBS + SQL on this server. It is the second time I
>install it on this server. The only thing that changes is that I updated
>with the latest ms update + installed symantec lifestate...
> here is the log of SQLstp.log
> 19:00:30 Begin Setup
> 19:00:30 8.00.194
> 19:00:30 Mode = Normal
> 19:00:30 ModeType = NORMAL
> 19:00:30 GetDefinitionEx returned: 0, Extended: 0x0
> 19:00:30 ValueFTS returned: 1
> 19:00:30 ValuePID returned: 1
> 19:00:30 ValueLic returned: 1
> 19:00:30 System: Small Business Server
> 19:00:30 SQL Server ProductType: Standard Edition [0x2]
> 19:00:30 Begin Action: SetupInitialize
> 19:00:30 End Action SetupInitialize
> 19:00:30 Begin Action: SetupInstall
> 19:00:30 Reading Software\Microsoft\Windows\CurrentVersion\CommonFilesDir
> ...
> 19:00:30 CommonFilesDir=C:\Program Files\Fichiers communs
> 19:00:30 Windows Directory=C:\WINDOWS\
> 19:00:30 Program Files=C:\Program Files\
> 19:00:30 TEMPDIR=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\
> 19:00:30 Begin Action: SetupInstall
> 19:00:30 Begin Action: CheckFixedRequirements
> 19:00:30 Platform ID: 0xf000
> 19:00:30 Version: 5.2.3790
> 19:00:30 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.3790.2523
> 19:00:31 End Action: CheckFixedRequirements
> 19:00:31 Begin Action: ShowDialogs
> 19:00:31 Initial Dialog Mask: 0x183000f7, Disable Back=0x1
> 19:00:31 Begin Action ShowDialogsHlpr: 0x1
> 19:00:31 Begin Action: DialogShowSdWelcome
> 19:00:32 End Action DialogShowSdWelcome
> 19:00:32 Dialog 0x1 returned: 1
> 19:00:32 End Action ShowDialogsHlpr
> 19:00:32 ShowDialogsGetDialog returned: nCurrent=0x2,index=1
> 19:00:32 Begin Action ShowDialogsHlpr: 0x2
> 19:00:32 Begin Action: DialogShowSdMachineName
> 19:01:07 ShowDlgMachine returned: -1
> 19:01:07 ShowDlgMachine: GetLastError returned: 0
> 19:01:07 Opération réussie.
> 19:01:07 End Action DialogShowSdMachineName
> 19:01:07 End Action ShowDialogs
> 19:01:07 Action CleanUpInstall:
> 19:01:07 StatsGenerate returned: 2
> 19:01:07 StatsGenerate (0x0,0x0,0xf000,0x0,1036,0,0x0,0x0,0,0,0
> 19:01:07 StatsGenerate -1,)
> 19:01:07 Installation Failed.
>
> "Jerry Spivey" <jspivey@.vestas-awt.com> a écrit dans le message de news:
> OdVtGSP1FHA.560@.TK2MSFTNGP12.phx.gbl...
>> What were the last few successful entries? Do you have an installation
>> that WAS successful that you can compare it to?
>> "aLAMBIKI" <alambiki@.yahoo.com> wrote in message
>> news:4356ae9a$0$4336$626a54ce@.news.free.fr...
>> Yes I tried to reinstall after reboot.
>> I found the Sqlstp.log file, but am not able to understand it.
>> If someone has an idea...
>> "Jerry Spivey" <jspivey@.vestas-awt.com> a écrit dans le message de news:
>> enXaUuM1FHA.1264@.tk2msftngp13.phx.gbl...
>> Did you try installing again after the reboot? Was there an error code
>> listed?
>> From KB Article 257716:
>> Q. What should I do if the installation of SQL Server 2000 is
>> unsuccessful?
>> A. If you have an unsuccessful installation, you can examine two files
>> to help determine what went wrong. The Sqlstp.log file, which is
>> located in the Windows directory, gives detailed information on what
>> setup is doing and contains all errors encountered during setup.
>> Reviewing this file will give you a better understanding of where setup
>> fails and why.
>> During the configuration portion of setup, SQL Server setup runs an
>> application called Cnfgsvr.exe to configure the SQL Server. This
>> application starts SQL Server, connects to it, and then runs the
>> initial installation scripts. Any error encountered during this process
>> is also written to the Sqlstp.log file; however, you should also review
>> the SQL Server error log, named "Errorlog" with no file extension,
>> located by default in the Program Files\Microsoft SQL Server\Mssql\Log
>> directory. This error log contains errors that SQL Server encounters
>> when setup attempts to start SQL Server, which may provide further
>> insight into the failure.
>> If you cannot determine the cause of the Setup failure, save the two
>> files just mentioned and call Microsoft Product Support Services (PSS)
>> to speak to a SQL Server Support Professional who will help you to
>> resolve your problem. Note that when the Setup application fails, it
>> rolls back all changes to the file system, which includes removing any
>> copied files and changes that were made to the registry.
>>
>> HTH
>> Jerry
>> "Alambiki" <alambiki@.yahoo.com> wrote in message
>> news:dj5qnl$ok9$1@.reader1.imaginet.fr...
>> Hi,
>> I am trying to install SQL 2000 sevrer on my SBS 2003 server (I own
>> the SBS
>> 2003 server Premium).
>> I installed the OS lately and made all the Microsoft update.
>> I am now trying to install the SQL 2000 server and get this error
>> message:
>> (It is the english translation of what I get on my screen)
>> Error message: "A previous installation program created operation
>> files
>> waiting for Installtion on your computer. You have to reboot it before
>> executing the installation."
>> Of course I rebooted my server, but nothing happened.
>> Any idea of what to do ?
>> Thank you for your help
>>
>>
>>
>sql

Error when installing Reporting Services in Virtual PC 2004

When I tried installing Reporting Services in Windows Server 2003 under
Virtual PC 2004 it displays a message "Error!". I have already installed
VS.NET 2003 and SQL Server 2000 with SP3. Please help.Hi Randy:
I've installed RS on a couple VPCs, so I don't think it would be a
general problem with VPC. I'm wondering what the problem could be. Do
you have 2003 configured as an application server (IIS, ASP.NET
enabled) before the install?
--
Scott
http://www.OdeToCode.com/blogs/scott/
On Wed, 3 Nov 2004 19:23:02 -0800, "Randy Gadingan" <Randy
Gadingan@.discussions.microsoft.com> wrote:
>When I tried installing Reporting Services in Windows Server 2003 under
>Virtual PC 2004 it displays a message "Error!". I have already installed
>VS.NET 2003 and SQL Server 2000 with SP3. Please help.|||Hi Scott:
I have configured Windows Server 2003 as an application server before
installing VS NET 2003 and SQL Reporting Services.
"Scott Allen" wrote:
> Hi Randy:
> I've installed RS on a couple VPCs, so I don't think it would be a
> general problem with VPC. I'm wondering what the problem could be. Do
> you have 2003 configured as an application server (IIS, ASP.NET
> enabled) before the install?
> --
> Scott
> http://www.OdeToCode.com/blogs/scott/
> On Wed, 3 Nov 2004 19:23:02 -0800, "Randy Gadingan" <Randy
> Gadingan@.discussions.microsoft.com> wrote:
> >When I tried installing Reporting Services in Windows Server 2003 under
> >Virtual PC 2004 it displays a message "Error!". I have already installed
> >VS.NET 2003 and SQL Server 2000 with SP3. Please help.
>

Error when deploying Report Model

I installed SQL Server 2005 on my laptop, this also contains my SQL Server 2000, so I couldnt use localhost and I used CreweAlex/SQLSERVER2005 as the hostname.

What do I need to fill in the field:

TargetServerURL

Because when I type http:\\localhost\ReportServer it doesn't work (as mentioned in the tutorial which I am following), also CreweAlex/SQLSERVER2005/ReportServer doesnt work.

I tried all kinds of combinations, but nothing works.

Everything is installed on my laptop, also the Reporting Server.

Try http://crewealex/reportserver$sqlserver2005|||

Thanks for the quick respons, but I still get an error:

Connection could not be made to the report server

The attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version. (Microsoft.ReportingServices.SemanticQueryDesign)

|||

When I type http://crewealex/reportserver in my browser then I can see that I log in into my Report Server, because this is the message that I get:

Microsoft SQL Server Reporting Services Version 9.00.1399.00

I typed http://crewealex/reportserver in my TargetServerURL and this works now. But my instance name is SQLSERVER2005. > Problem solved.

Error when deploying report builder model

I get the following error when I try to deploy a report builder model. The SQL Server 2005 "Reporting Services" are installed and running on the local machine.

TITLE: Microsoft Semantic Model Designer

A connection could not be made to the report server http://localhost/ReportServer.

ADDITIONAL INFORMATION:

Client found response content type of 'text/html; charset=utf-8', but expected 'text/xml'.
The request failed with the error message:
--
<html>
<head>
<title>
SQL Server Reporting Services
</title><meta name="Generator" content="Microsoft SQL Server Reporting Services 9.00.2047.00" />
<meta name="HTTP Status" content="500" />
<meta name="ProductLocaleID" content="9" />
<meta name="CountryLocaleID" content="1033" />
<meta name="StackTrace" content=" at Microsoft.ReportingServices.Diagnostics.RSConfiguration.Load()
at Microsoft.ReportingServices.Diagnostics.RSConfiguration.Construct(String configFileName)
at Microsoft.ReportingServices.Diagnostics.RSConfiguration..ctor(String configFileName, String location)
at Microsoft.ReportingServices.Diagnostics.RSConfigurationManager..ctor(String configFileName, String configLocation)
at Microsoft.ReportingServices.Library.Global.get_ConfigurationManager()
at Microsoft.ReportingServices.WebServer.Global.StartApp()
at Microsoft.ReportingServices.WebServer.Global.Application_BeginRequest(Object sender, EventArgs e)" />
<style>
BODY {FONT-FAMILY:Verdana; FONT-WEIGHT:normal; FONT-SIZE: 8pt; COLOR:black}
H1 {FONT-FAMILY:Verdana; FONT-WEIGHT:700; FONT-SIZE:15pt}
LI {FONT-FAMILY:Verdana; FONT-WEIGHT:normal; FONT-SIZE:8pt; DISPLAY:inline}
.ProductInfo {FONT-FAMILY:Verdana; FONT-WEIGHT:bold; FONT-SIZE: 8pt; COLOR:gray}
A:link {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLOR:#3366CC; TEXT-DECORATION:none}
A:hover {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLOR:#FF3300; TEXT-DECORATION:underline}
A:visited {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLOR:#3366CC; TEXT-DECORATION:none}
A:visited:hover {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; color:#FF3300; TEXT-DECORATION:underline}

</style>
</head><body bgcolor="white">
<h1>
Reporting Services Error<hr width="100%" size="1" color="silver" />
</h1><ul>
<li>The report server has encountered a configuration error. See the report server log files for more information. (rsServerConfigurationError) </li><ul>
<li>Access to the path 'C:\Program Files\Microsoft SQL Server\MSSQL.4\Reporting Services\ReportServer\RSReportServer.config' is denied.</li>
</ul>
</ul><hr width="100%" size="1" color="silver" /><span class="ProductInfo">SQL Server Reporting Services</span>
</body>
</html>
--. (Microsoft.ReportingServices.SemanticQueryDesign)

BUTTONS:

OKI ended up uninstalling SQL Server 2005, uninstalling the previously installed SQLExpress, and then reinstalling SQL Server 2005. This solved the problem.|||I had the same kind a problem and i started looking some other reporting tool .The very best one on the market in my opinion is Intelliview. It is very pricey

though! You can find it here: http://www.synaptris.com/products/reporting-analytics/index.html

Error when deploying report builder model

I get the following error when I try to deploy a report builder model. The SQL Server 2005 "Reporting Services" are installed and running on the local machine.

TITLE: Microsoft Semantic Model Designer

A connection could not be made to the report server http://localhost/ReportServer.

ADDITIONAL INFORMATION:

Client found response content type of 'text/html; charset=utf-8', but expected 'text/xml'.
The request failed with the error message:
--
<html>
<head>
<title>
SQL Server Reporting Services
</title><meta name="Generator" content="Microsoft SQL Server Reporting Services 9.00.2047.00" />
<meta name="HTTP Status" content="500" />
<meta name="ProductLocaleID" content="9" />
<meta name="CountryLocaleID" content="1033" />
<meta name="StackTrace" content=" at Microsoft.ReportingServices.Diagnostics.RSConfiguration.Load()
at Microsoft.ReportingServices.Diagnostics.RSConfiguration.Construct(String configFileName)
at Microsoft.ReportingServices.Diagnostics.RSConfiguration..ctor(String configFileName, String location)
at Microsoft.ReportingServices.Diagnostics.RSConfigurationManager..ctor(String configFileName, String configLocation)
at Microsoft.ReportingServices.Library.Global.get_ConfigurationManager()
at Microsoft.ReportingServices.WebServer.Global.StartApp()
at Microsoft.ReportingServices.WebServer.Global.Application_BeginRequest(Object sender, EventArgs e)" />
<style>
BODY {FONT-FAMILY:Verdana; FONT-WEIGHT:normal; FONT-SIZE: 8pt; COLOR:black}
H1 {FONT-FAMILY:Verdana; FONT-WEIGHT:700; FONT-SIZE:15pt}
LI {FONT-FAMILY:Verdana; FONT-WEIGHT:normal; FONT-SIZE:8pt; DISPLAY:inline}
.ProductInfo {FONT-FAMILY:Verdana; FONT-WEIGHT:bold; FONT-SIZE: 8pt; COLOR:gray}
A:link {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLOR:#3366CC; TEXT-DECORATION:none}
A:hover {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLOR:#FF3300; TEXT-DECORATION:underline}
A:visited {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLOR:#3366CC; TEXT-DECORATION:none}
A:visited:hover {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; color:#FF3300; TEXT-DECORATION:underline}

</style>
</head><body bgcolor="white">
<h1>
Reporting Services Error<hr width="100%" size="1" color="silver" />
</h1><ul>
<li>The report server has encountered a configuration error. See the report server log files for more information. (rsServerConfigurationError) </li><ul>
<li>Access to the path 'C:\Program Files\Microsoft SQL Server\MSSQL.4\Reporting Services\ReportServer\RSReportServer.config' is denied.</li>
</ul>
</ul><hr width="100%" size="1" color="silver" /><span class="ProductInfo">SQL Server Reporting Services</span>
</body>
</html>
--. (Microsoft.ReportingServices.SemanticQueryDesign)

BUTTONS:

OKI ended up uninstalling SQL Server 2005, uninstalling the previously installed SQLExpress, and then reinstalling SQL Server 2005. This solved the problem.|||I had the same kind a problem and i started looking some other reporting tool .The very best one on the market in my opinion is Intelliview. It is very pricey

though! You can find it here: http://www.synaptris.com/products/reporting-analytics/index.htmlsql

Error when creating new connection in DTS Designer

64b SQL2005 EE and all clent tools installed on the same server. Im trying to create a new connection in DTS Designer but after succesful test of the connection it errors out with

The new connection manager couldnt be created. Additional info : Exeption from HRESULT 0xC0010014

Any idea whats the problem here?

This might be caused by a problem described here:

http://support.microsoft.com/kb/913817

|||Im logged in with local admin account. Does that count? Still SSIS is running under Network Servise|||Usually the service does the component enumeration and caches the results, so this is performed without admin rights. You can check if this is an issue by temporary disabling the service, and trying this again (restart BIDS first). If this is caused by permission issue, you'll likely succeed because BIDS will do the component enumeration itself (this harms performance, but avoids Network Service restrictions).

error when connecting trhough enterprise manager

hi all ,
i've got an application with sql databse. it runs correctly on the server.
when i go to windows Xp and installed the appliaction and run the sql
enterprise manager to connect to the server, i get the following error:
message =: ExecuteReader requires an open and available connection. the
connection's current state is closed.
i've checked network connection ..it is ok.
the same application we've tested at office ...its working fine.
plz advise
kryshzt
Hi
Are you sure? This error's message is pretty clear, isn't it?
"kryshzt" <kryshzt@.discussions.microsoft.com> wrote in message
news:8636B1D3-80F7-40C7-A384-3DC1E6E9C8ED@.microsoft.com...
> hi all ,
> i've got an application with sql databse. it runs correctly on the server.
> when i go to windows Xp and installed the appliaction and run the sql
> enterprise manager to connect to the server, i get the following error:
> message =: ExecuteReader requires an open and available connection. the
> connection's current state is closed.
> i've checked network connection ..it is ok.
> the same application we've tested at office ...its working fine.
> plz advise
> kryshzt