November 23, 2008 at 10:47 pm
Dom thanks for replying. After a little reading here
http://msdn.microsoft.com/en-us/library/ms143736.aspx
I still did not have success, so I decided to use one of my MS partner tickets. I was on the phone for 4+ hours on Friday and its still FUBAR. I had the guy stumped. We were able to work around the 401 problem, but now it looks like some sort of a DNS or IP routing problem.
BTW - beware of aspnet_RegIIS I think this hosed a website on this box that it .Net 1.1. It's been a disaster. The website works but the rendering of Treeview controls is hosed. I need an urgent fix for this now.
Tomorrow, I will talk to my MS tech support guy and see what's up. The current problem is that report manager times out trying to reach report server, even though I can browse Report server directly? it makes no sense.
On top of this, i have 2 other servers where it works great. Hang on for more updates.
Doug
November 23, 2008 at 11:04 pm
As a FYI, before you go and try aspnet_regiis on anything other than a test server the postings at the link below. The command looks benin, but as usual, there are unknown side effects depending on what's running on the box.
http://geekswithblogs.net/paulmehner/archive/2005/08/03/48970.aspx
They recommend that you use:
aspnet_regiis -ir -enable - Installs ASP.NET version with root and enables it.
aspnet_regiis -s path - Registers script map for our Application.
Hope this helps
:Whistling:
November 24, 2008 at 2:38 am
Thanks Doug for sharing this with me,
I'll have a look into the comments and links you provided when I get a mo'.
regards,
dom
December 2, 2008 at 11:09 am
Dom, I'm still working on this with my new friends at Microsoft. I will post back when I have an update.
December 12, 2008 at 10:59 am
Ok, Dom I got my problem resolved but I don't have a great explanation of how I fixed it. Send me some particulars of your problem and I'll try to squeeze out some time to respond.
Some how the custom HTTP headers on the web site contained a HTTP definition (I think this was when I ran the .NET registration utility). When the Reports manager site got loaded, it called the report server site (via Web services I presume) and when IIS put the HTML type in the header (if overrode the XML type) and the page got a 500 error (Server not responding) in the logs.
For Days we believed the URL was wrong, yet we could browse there in IE. Turned off custom HTTP headers and report manager page loads right up.
Good Luck
March 18, 2009 at 5:37 am
Hi Doug,
I've eventually come back to this....tried a fresh install on another PC...Windows 2000, SQL Server 2005 SP2 Developer version. All seems to install fine.
Reporting Services Configuration - fine
PC running as a web server - fine
SSMS - fine (both ReportServer and ReportServerTempDB installed)
BUT, cannot access Reporting Services through SSMS - operation timed out
nor, using SAC for features, under Reporting Services, when cliking on the Windows Integrated Security option, it freezes and doesn't respond.
nor, going to http://machinename/reports I get the message Server Application Unavailable.
Here are a couple of logs:
Reporting Services Log:
ReportingServicesService!library!4!18/03/2009-10:26:07:: i INFO: Initializing ConnectionType to '0' as specified in Configuration file.
ReportingServicesService!library!4!18/03/2009-10:26:07:: i INFO: Initializing IsSchedulingService to 'True' as specified in Configuration file.
ReportingServicesService!library!4!18/03/2009-10:26:07:: i INFO: Initializing IsNotificationService to 'True' as specified in Configuration file.
ReportingServicesService!library!4!18/03/2009-10:26:07:: i INFO: Initializing IsEventService to 'True' as specified in Configuration file.
ReportingServicesService!library!4!18/03/2009-10:26:07:: i INFO: Initializing PollingInterval to '10' second(s) as specified in Configuration file.
ReportingServicesService!library!4!18/03/2009-10:26:07:: i INFO: Initializing WindowsServiceUseFileShareStorage to 'False' as specified in Configuration file.
ReportingServicesService!library!4!18/03/2009-10:26:07:: i INFO: Initializing MemoryLimit to '60' percent as specified in Configuration file.
ReportingServicesService!library!4!18/03/2009-10:26:07:: i INFO: Initializing RecycleTime to '720' minute(s) as specified in Configuration file.
ReportingServicesService!library!4!18/03/2009-10:26:07:: i INFO: Initializing MaximumMemoryLimit to '80' percent as specified in Configuration file.
ReportingServicesService!library!4!18/03/2009-10:26:07:: i INFO: Initializing MaxAppDomainUnloadTime to '30' minute(s) as specified in Configuration file.
ReportingServicesService!library!4!18/03/2009-10:26:07:: i INFO: Initializing MaxQueueThreads to '0' thread(s) as specified in Configuration file.
ReportingServicesService!library!4!18/03/2009-10:26:07:: i INFO: Initializing IsWebServiceEnabled to 'True' as specified in Configuration file.
ReportingServicesService!configmanager!4!18/03/2009-10:26:07:: w WARN: WebServiceAccount is not specified in the config file. Using default: EDU6006654\ASPNET
ReportingServicesService!library!4!18/03/2009-10:26:07:: i INFO: Initializing MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
ReportingServicesService!library!4!18/03/2009-10:26:07:: i INFO: Initializing MaxScheduleWait to '5' second(s) as specified in Configuration file.
ReportingServicesService!library!4!18/03/2009-10:26:07:: i INFO: Initializing DatabaseQueryTimeout to '120' second(s) as specified in Configuration file.
ReportingServicesService!library!4!18/03/2009-10:26:07:: i INFO: Initializing ProcessRecycleOptions to '0' as specified in Configuration file.
ReportingServicesService!library!4!18/03/2009-10:26:07:: i INFO: Initializing RunningRequestsScavengerCycle to '60' second(s) as specified in Configuration file.
ReportingServicesService!library!4!18/03/2009-10:26:07:: i INFO: Initializing RunningRequestsDbCycle to '60' second(s) as specified in Configuration file.
ReportingServicesService!library!4!18/03/2009-10:26:07:: i INFO: Initializing RunningRequestsAge to '30' second(s) as specified in Configuration file.
ReportingServicesService!library!4!18/03/2009-10:26:07:: i INFO: Initializing CleanupCycleMinutes to '10' minute(s) as specified in Configuration file.
ReportingServicesService!library!4!18/03/2009-10:26:07:: i INFO: Initializing DailyCleanupMinuteOfDay to default value of '120' minutes since midnight because it was not specified in Configuration file.
ReportingServicesService!library!4!18/03/2009-10:26:07:: i INFO: Initializing WatsonFlags to '1064' as specified in Configuration file.
ReportingServicesService!library!4!18/03/2009-10:26:07:: i INFO: Initializing WatsonDumpOnExceptions to 'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException' as specified in Configuration file.
ReportingServicesService!library!4!18/03/2009-10:26:07:: i INFO: Initializing WatsonDumpExcludeIfContainsExceptions to 'System.Data.SqlClient.SqlException,System.Threading.ThreadAbortException' as specified in Configuration file.
ReportingServicesService!library!4!18/03/2009-10:26:07:: i INFO: Initializing SecureConnectionLevel to '0' as specified in Configuration file.
ReportingServicesService!library!4!18/03/2009-10:26:07:: i INFO: Initializing DisplayErrorLink to 'True' as specified in Configuration file.
ReportingServicesService!library!4!18/03/2009-10:26:07:: i INFO: Initializing WebServiceUseFileShareStorage to 'False' as specified in Configuration file.
ReportingServicesService!resourceutilities!4!18/03/2009-10:26:08:: i INFO: Reporting Services starting SKU: Developer
ReportingServicesService!resourceutilities!4!18/03/2009-10:26:08:: i INFO: Evaluation copy: 0 days left
ReportingServicesService!library!8!18/03/2009-10:26:14:: i INFO: Catalog SQL Server Edition = Developer
ReportingServicesService!crypto!8!18/03/2009-10:26:14:: i INFO: Initializing crypto as user: NT AUTHORITY\SYSTEM
ReportingServicesService!crypto!8!18/03/2009-10:26:14:: i INFO: Exporting public key
ReportingServicesService!crypto!8!18/03/2009-10:26:15:: i INFO: Performing sku validation
ReportingServicesService!crypto!8!18/03/2009-10:26:15:: i INFO: Importing existing encryption key
ReportingServicesService!dbpolling!8!03/18/2009-10:26:15:: i INFO: EventPolling polling service started
ReportingServicesService!dbpolling!a!18/03/2009-10:26:15:: i INFO: EventPolling heartbeat thread started.
ReportingServicesService!dbpolling!8!03/18/2009-10:26:15:: i INFO: NotificationPolling polling service started
ReportingServicesService!dbpolling!b!18/03/2009-10:26:15:: i INFO: NotificationPolling heartbeat thread started.
ReportingServicesService!dbpolling!8!03/18/2009-10:26:15:: i INFO: SchedulePolling polling service started
ReportingServicesService!dbpolling!8!03/18/2009-10:26:15:: i INFO: UpgradePolling polling service started
ReportingServicesService!dbpolling!c!18/03/2009-10:26:15:: i INFO: Polling started
ReportingServicesService!runningjobs!8!03/18/2009-10:26:15:: i INFO: Database Cleanup (NT Service) timer enabled: Next Event: 600 seconds. Cycle: 600 seconds
ReportingServicesService!runningjobs!8!03/18/2009-10:26:15:: i INFO: Running Requests Scavenger timer enabled: Next Event: 60 seconds. Cycle: 60 seconds
ReportingServicesService!runningjobs!8!03/18/2009-10:26:15:: i INFO: Running Requests DB timer enabled: Next Event: 60 seconds. Cycle: 60 seconds
ReportingServicesService!runningjobs!8!03/18/2009-10:26:15:: i INFO: Execution Log Entry Expiration timer enabled: Next Event: 56024 seconds. Cycle: 86400 seconds
ReportingServicesService!runningjobs!8!03/18/2009-10:26:15:: i INFO: Memory stats update timer enabled: Next Event: 60 seconds. Cycle: 60 seconds
ReportingServicesService!runningjobs!8!03/18/2009-10:26:15:: i INFO: SQM timer timer enabled: Next Event: 59624 seconds. Cycle: 86400 seconds
ReportingServicesService!library!4!18/03/2009-10:36:16:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs, 0 persisted streams
ReportingServicesService!dbpolling!c!18/03/2009-10:36:46:: e ERROR: Polling caught an exception, restarting polling. Error Message System.Data.SqlClient.SqlException: A transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider, error: 0 - The pipe is being closed.)
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.TdsParserStateObject.WriteSni()
at System.Data.SqlClient.TdsParserStateObject.WritePacket(Byte flushMode)
at System.Data.SqlClient.TdsParserStateObject.ExecuteFlush()
at System.Data.SqlClient.TdsParser.TdsExecuteSQLBatch(String text, Int32 timeout, SqlNotificationRequest notificationRequest, TdsParserStateObject stateObj)
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.ReportingServices.Library.InstrumentedSqlCommand.ExecuteReader()
at Microsoft.ReportingServices.Library.DBPoll.PollingFunction()
at Microsoft.ReportingServices.Library.DBPoll.PollingStartFunction().
ReportingServicesService!library!c!18/03/2009-10:37:02:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseUnavailableException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseUnavailableException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. ---> System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner, Boolean& failoverDemandDone, String host, String failoverPartner, String protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject, Boolean aliasLookup)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.ReportingServices.Library.ConnectionManager.OpenConnection()
--- End of inner exception stack trace ---
ReportingServicesService!dbpolling!c!18/03/2009-10:37:02:: e ERROR: Polling caught an exception, restarting polling. Error Message Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseUnavailableException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. ---> System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner, Boolean& failoverDemandDone, String host, String failoverPartner, String protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject, Boolean aliasLookup)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.ReportingServices.Library.ConnectionManager.OpenConnection()
--- End of inner exception stack trace ---
at Microsoft.ReportingServices.Library.ConnectionManager.OpenConnection()
at Microsoft.ReportingServices.Library.ConnectionManager.ConnectStorage()
at Microsoft.ReportingServices.Library.DBPoll.PollingFunction()
at Microsoft.ReportingServices.Library.DBPoll.PollingStartFunction().
ReportingServicesService!library!c!18/03/2009-10:37:09:: i INFO: Polling started again.
ReportingServicesService!dbpolling!4!18/03/2009-10:37:48:: i INFO: EventPolling polling service stopped
ReportingServicesService!dbpolling!a!18/03/2009-10:37:48:: i INFO: EventPolling heartbeat thread exiting for stop.
ReportingServicesService!dbpolling!4!18/03/2009-10:37:48:: i INFO: NotificationPolling polling service stopped
ReportingServicesService!dbpolling!b!18/03/2009-10:37:48:: i INFO: NotificationPolling heartbeat thread exiting for stop.
ReportingServicesService!dbpolling!4!18/03/2009-10:37:48:: i INFO: SchedulePolling polling service stopped
ReportingServicesService!dbpolling!4!18/03/2009-10:37:48:: i INFO: UpgradePolling polling service stopped
ReportingServicesService!servicecontroller!4!18/03/2009-10:37:48:: i INFO: Service controller exiting.
IIS Log:
#Software: Microsoft Internet Information Services 5.0
#Version: 1.0
#Date: 2009-03-18 11:19:00
#Fields: time c-ip cs-method cs-uri-stem sc-status
11:19:00 10.171.5.201 GET /iisstart.asp 302
11:19:00 10.171.5.201 GET /localstart.asp 401
11:19:00 10.171.5.201 GET /win2000.gif 304
11:19:00 10.171.5.201 GET /warning.gif 304
11:19:00 10.171.5.201 GET /localstart.asp 200
11:19:00 10.171.5.201 GET /web.gif 304
11:19:00 10.171.5.201 GET /mmc.gif 304
11:19:00 10.171.5.201 GET /help.gif 304
11:19:00 10.171.5.201 GET /print.gif 304
11:19:00 127.0.0.1 GET /iishelp/Default.htm 304
11:19:00 127.0.0.1 GET /iishelp/iis/misc/default.asp 200
11:19:00 127.0.0.1 GET /iishelp/iis/misc/contents.asp 200
11:19:00 127.0.0.1 GET /iishelp/iis/misc/navbar.asp 200
11:19:00 127.0.0.1 GET /iishelp/iis/misc/navpad.gif 304
11:19:00 127.0.0.1 GET /iishelp/iis/htm/core/iiwltop.htm 304
11:19:00 127.0.0.1 GET /iishelp/iis/misc/MS_logo.gif 304
11:19:00 127.0.0.1 GET /iishelp/iis/misc/ismhd.gif 304
11:19:00 127.0.0.1 GET /iishelp/iis/misc/Cont.gif 304
11:19:00 127.0.0.1 GET /iishelp/iis/misc/NoIndex.gif 304
11:19:00 127.0.0.1 GET /iishelp/iis/misc/NoSearch.gif 304
11:19:00 127.0.0.1 GET /iishelp/iis/misc/print.gif 304
11:19:00 127.0.0.1 GET /iishelp/iis/misc/synch.gif 304
11:19:00 127.0.0.1 GET /iishelp/iis/misc/cohhc.hhc 304
11:19:00 127.0.0.1 GET /iishelp/common/coua.css 304
11:19:00 127.0.0.1 GET /iishelp/iis/htm/core/iis_banr.gif 304
11:19:10 10.171.5.201 GET /reports/ 302
11:25:17 10.171.5.201 GET /reports/Home.aspx 302
11:27:52 10.171.5.201 GET /reports/Pages/Folder.aspx 500
11:27:52 127.0.0.1 POST /ReportServer/ReportService2005.asmx 500
i'm at a loss....and fed up!
thanks,
dom
March 19, 2009 at 3:36 pm
Dom, check out those exceptions and notice the named pipes and shared memory parts of the message. It appears the the transport level connection types need to be tweaked (for starters). I would think that you need to specify TCP/IP instead of named pipes/shared memory. It appears to be trying to connect and the transport is disabled or blocked somehow.
I will try to figure out how to set and verify this.
March 19, 2009 at 3:47 pm
Dom here's another thing. You have a service acount running the report server (probably nt Authority\System) in your ReportServer database you MUST have that service account as a user. So open SQL EM and look in security\users and see what's there.
On my machine [NT Authority\System] is the service account and it has the RSExecRole checked in Role Membship.
the SQL server config manager should show the client protocols enabled.
FYI - I have found that the exception error messages are very vague, but they point to the general direction where you find touble. Don't bother with the other advice to reimage the OS, this is a waste of time at this point. There is something else out of whack that can be cleaned up or explained.
I feel your pain...
March 19, 2009 at 4:10 pm
I cannot comprehend why you are running SQL Server 2005 in Windows 2000 but I am assuming you have run run aspnet_regiis in your c drive. So go to the location below and run this utility.
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
Kind regards,
Gift Peddie
March 20, 2009 at 4:11 am
why can't you comprehend?!
.net frameworks already updated
March 20, 2009 at 4:13 am
Thanks Doug for your valued contributions....I will look into your suggestions when I have a moment (time constraints at work are limiting me at the mo'!)
Dom
March 20, 2009 at 6:34 am
ReportingServicesService!configmanager!4!18/03/2009-10:26:07:: w WARN: WebServiceAccount is not specified in the config file. Using default: EDU6006654\ASPNET
I think Doug is right about checking out the account. Does this account have access to the rs database?
If W2003 (or W2008) is an option, you might want to consider it. IIS improves with each one, and both of these were built with .Net frameworks in mind. I agree with Doug's thought about not reimaging, but from a support standpoint, you might be in better shape on a newer OS.
Greg E
March 20, 2009 at 6:54 am
why can't you comprehend?!
.net frameworks already updated
That is not what aspnet_regiis is for and I am now telling you that you cannot run Asp.net 2.0 dependent SSRS 2005 without running that utility even with new operating system.
Kind regards,
Gift Peddie
March 20, 2009 at 10:22 am
I'd be very surprised if SQL 2005 Report services was not supported in Win 2000 server. If this was the case I think the install program would have caught this. It does not hurt to check.
The IIS reg tool updates script maps so that IIS will allow website A can run .NET 1.1, website B can run .Net 20, and website C can run .Net 3.0. If you screwup the command line params on the IIS reg tool you will break websites that are NOT .NET 2.0 and it may cause more problems on the machine.
If the script maps are fubar you will get some exceptions right from the start the first time a .NET library (of the wrong version) is loaded and executed. here's a link that will give more info.
http://msdn.microsoft.com/en-us/library/k6h9cz8h(VS.80).aspx
You can check the script maps by looking at the properties of the web site to see what .NET framework is associated with the IIS website. If its mapped to .Net 2.0 this is easily checked before running the IIS reg tool and possibly breaking an existing website.
Since your exceptions are related to logins, lets start there and verify the service login accounts have permissions in the DB. So, once you've check for .NET 2.0 and logins, lets look at the excpetions and go from there. Google searches on the exceptions have been useful to me in the past.
It took me 2 weeks of back and forth with the MSFT techies before we found some obscure problem related to a security patch and handling of URLs. This is NOT your problem I'm 99.99% sure of that.
I feel your pain.
March 20, 2009 at 10:28 am
BTW - updates to windows server and IIS primarilly help with process isolation such that websites that crash will not break IIS or other websites. Win 2008 by far is the best if you plan to deploy in production.
However, your problem is basic connectivity to the reporting database, so your OS should be good enough to test or develop with.
Good luck
PS. I hope you're testing on the OS you plan to deploy with.
Viewing 15 posts - 16 through 30 (of 30 total)
You must be logged in to reply to this topic. Login to reply