I am not sure if its possible, hopefully it is. I would like to create a custom page for one of my clients to log into and access information from their SQL server. If I have all the connection information, i.e user id and password etc. Can this be done. I know how to connect to an SQL server locally. If anyone can give me a point in the right direction, it would be greatly appreciative.
If this is possible, I am looking at adding a button on this page to allow the client to transfer records that meet specific criteria in a column in their database into a designated database on my server.
I just installed SQL Server for the first time on a windows 2003 OS which is on its on server. Then, I installed the client tools on my local computer. Now how do I connect to the sql server with my client tools? What I wanted to do is from my local computer use the enterprise manager and pull up the databases that are located on the server that contains the sql server.
OK, I'm stumped and could do with some help. I have a laptop running Vista (64bit) with the SQL 2005 client tools. At home, I have SQL Server 2000 running on Windows Server 2003. I cannot get the SQL 2005 to talk to the SQL Server 2000. At work, we have SQL 2000 running on NT 5.0 and it connects fine. I also have a second laptop with SQL 2000 client tools running on XP SP2 which conects fine to the SQL 2000 instance on the 2003 box.
The vista laptop talks to the 2003 server, so it's not simpy that there is no connection. Any ideas why I keep getting an error stating that the Server might not be accepting remote connections every time I try to connect the Vista machine to the SQL 2000 server? I can't connect either from the SQL management tool, nor via ODBC.
I need to connect to a SQL server thats running in say abc.trident.com and also sits in a shared environment..
I have couple of questions
1) That SQL server is accessible from my network, yet when I swtich on my enterprise manager I am unable to view that in the list of running SQL servers in the populated list.
Is it because its sitting in a shared environment I am unable to view that?
2) What is the connection striing I should use to connect to the server..When I try to configure a SQL server registrations it normally asks for SQL Server name along with the user authentication
Should I mention fill the Server: field as
abc.trident.com
or
// abc.trident.com/abc.trident.com
to connect to the clustered server.
Can some one tell me the proper connection string if both aforementioned ones are incorrect?
I am getting this message. On the actual server I can pull up the report builder, but from a client on the network when trying to connect to the sql report builder I get this message:
PLATFORM VERSION INFO Windows : 5.1.2600.131072 (Win32NT) Common Language Runtime : 2.0.50727.42 System.Deployment.dll : 2.0.50727.42 (RTM.050727-4200) mscorwks.dll : 2.0.50727.42 (RTM.050727-4200) dfdll.dll : 2.0.50727.42 (RTM.050727-4200) dfshim.dll : 2.0.50727.42 (RTM.050727-4200)
ERROR SUMMARY Below is a summary of the errors, details of these errors are listed later in the log. * Activation of http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application resulted in exception. Following failure messages were detected: + Downloading http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application did not succeed. + The remote server returned an error: (401) Unauthorized.
COMPONENT STORE TRANSACTION FAILURE SUMMARY No transaction error was detected.
WARNINGS There were no warnings during this operation.
OPERATION PROGRESS STATUS * [3/16/2006 10:10:28 AM] : Activation of http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application has started.
ERROR DETAILS Following errors were detected during this operation. * [3/16/2006 10:10:28 AM] System.Deployment.Application.DeploymentDownloadException (Unknown subtype) - Downloading http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application did not succeed. - Source: System.Deployment - Stack trace: at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next) at System.Deployment.Application.SystemNetDownloader.DownloadAllFiles() at System.Deployment.Application.FileDownloader.Download(SubscriptionState subState) at System.Deployment.Application.DownloadManager.DownloadManifestAsRawFile(Uri& sourceUri, String targetPath, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation) at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestDirectBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation) at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options) at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut) at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state) --- Inner Exception --- System.Net.WebException - The remote server returned an error: (401) Unauthorized. - Source: System - Stack trace: at System.Net.HttpWebRequest.GetResponse() at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)
COMPONENT STORE TRANSACTION DETAILS No transaction information is available.
Remote connections is enabled and I am connecting as the servers admin. Any suggestions. I think it might be a user thing, but I am not sure. Do I need to add a user to the report builder folder in iss or what.
I am trying to connect to reporting services with the SQL client (SQL server management studio), I get an error message saying
The machine could not be found (Microsoft.SqlServer.Management.UI.RSClient)
This is a new install of reporting services, I can connect to the reporting services reports site without a problem. I am working with the DBA, he can connect through the SQL client and on the sql/rs server side i have system admin. But i still cannot connect.
If you add me on to the system admin of the OS i can connect but i dont need that permissions. Ive tried just about everything. Any suggestions?
I have configured reporting services to be connected from client with the help of http://msdn2.microsoft.com/en-us/library/ms365170.aspx KB article and I can connect locally in the server without any error. I've configured report service correctly since I can execute http://servername/reportserver or http://servername/reports . When I try to connect report service from my client Im getting the below error, can anyone help me to correct this.
Machine could not be found(Microsoft.sqlserver.management.UI.rsclient)
This is urgent since our developers are unable to connect from client
I want to know what are the configuration I need for the client side to connect to SQL Server Express 2005. Because i'm studying Network Application using SQL Server Express 2005.
Please help me guys, i really appriciated everything.
I currently develop/maintain VB 05' apps for PDA's and desktops. I've got a scanner app that scans labels to build/transmit orders via an HTTP byte stream. I'm currently building an inventory app that resides at the remote client (windows not web) and can eventually connect to my SQL Server @ corp. At this point SQL 2005 endpoints work on the internal network but fail to resolve remotely. I've read about connecting to a SQL Server via HTTP with ip specs embedded in the connect string but havnt been able to find an example. Outside of creating a VPN for connectivity, can anyone recommend connection ideas for my scenario? Is it true that endpoints are only recommended for intranet consumption?
I have created a DTS package that pulls data in from Oracle into SQLServer. When I run it directly on the server (from EnterpriseManager), it works fine. When I run it from Enterprise Manager on aclient machine that does not have the Oracle client software, it doesnot run, giving me the error: "The Oracle client and networkingcomponents were not found...". I was hoping I wouldn't need to havethe client software installed on a machine other than the server whereSql Server is running. The problem here is that there are a number ofmachines from where I would like to execute this DTS package that I donot want to install/configure the Oracle client software. I don'tquite understand why the configuration of the client is importanthere. In my mind, when I am using enterprise manager from a clientmachine, I am using it sort of like a terminal services client toconnect to the server. I guess there is a lot more happening in thebackground.Thanks for any feedback,Marcus
I have installed SQL Server 2005 Enterprise Edition on a W2K3 server that already has a SQL Server 2000 default instance installed. The installation appears to be a success. The problem is that having installed the client tools, and trying to connect, I get the following error message in a dialog:
"Cannot connect server SERVERNAMEINSTANCENAME 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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)(Microsoft SQL Server)"
The funny thing is that I can connect to the SQL Server 2000 default instance that is on that server. So it's obviously not a connection problem per se at my end i.e. bad dns etc which might stop me resolving the server name.
Googling for this error text gives the following advice on various web sites:
1. Check that the remote server allows connections.
It does, as other colleagues in my team have successfully installed the tools and can connect with no problems.
2. Check that the SQL Browser service is running.
It is, as without this running, my colleagues would not be able to connect either.
3. Open SQL Server Configuration Manager. Select "SQL Server 2005 Network Configuration | Protocols for MSSQLSERVER" then enable the protocols you need.
The required protocol (TCP/IP) is enabled. Named pipes is also enabled, although I don't think that we're using that. And shared memory is also enabled by default.
4. Open the firewall and add exceptions for sqlbrowser.exe or UDP port 1434
There is no firewall running at either end of the connection and as mentioned I can connect to the SS2K default instance.
5. Make sure that the server machine is reachable.
I can connect to the SS2K default instance so it must be reachable. I can't see that I would need to change any configuration settings as my colleagues are using exactly the same default settings for their connections and they work fine.
The only thing that I have done differently is that I originally installed the client tools using someone else's privileged account as I didn't have admin rights on my box. The client tools didn't work, so I got admin rights to my box, uninstalled the client tools and then reinstalled them using my account. Still no luck. Not sure if something is still hanging around after the uninstallation that would cause me a problem.
To help, I've also filled out the following questionnaire:
[1] Client side: > What is the connection string in you app or DSN? There isn't one. I'm trying to connect from the SQL Server Management Studio | 'Connect to Server' dialog. > If client fails to connect, what is the client error messages? "Cannot connect server Y 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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)(Microsoft SQL Server)" Is the client remote or local to the SQL server machine? Remote Can you ping your server? YES Can you telnet to your SQL Server? YES What is your client database provider? [SNAC | MDAC | ADO.NET1.0 | ADO.NET2.0| other (please specify] N/A What is your client application? SQL Management Studio Is your client computer in the same domain as the Server computer? Different domains What protocol the client enabled? [Shared Memory | TCPIP | Named Pipes]. All 3 protocols are enabled Do you have aliases configured that match the server name portion of your connection string? No Do you select force encryption on server and/or client? No
[2] Server side: What is the MS SQL version? SQL Server 2005 What is the SKU of MS SQL? Enterprise What is the SQL Server Protocol enabled? [Shared Memory | TCPIP | Named Pipes ]. All 3 Does the server start successfully? YES. Other people can connect to the same instance. If SQL Server is a named instance, is the SQL browser enabled? YES What is the account that the SQL Server is running under? Domain Account Do you make firewall exception for your SQL server TCP port if you want connect remotely through TCP provider? N/A. Firewall not running. Do you make firewall exception for SQL Browser UDP port 1434? N/A. Firewall not running. What tool or Application are you using to connect to SQL Server SQL Server Management Studio
[3] Platform: What is the OS version? Windows 2003 (Server side), Windows XP Pro Version 2002 SP 2 Do you have third party antivirus, anti-spareware software installed? Symantec AntiVirus
[4] Misc: If you have certificate configuration issue: N/A
Has anybody else come across this problem, as I've run out of ideas.
On Windows XP systems I get the following issue when trying to browse the MSDB folder in SSIS
Client unable to establish connection Encryption not supported on SQL Server. (Microsoft SQL Native Client)
I have noticed another post where several others have noticed the same issue. It appears to only occur on Windows XP installations. Is there a workaround or fix for this?
Product: Microsoft SQL Server 2005 -- Error 29515. SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Encryption not supported on the client. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
I have SQL2000 installed as the default instance, and now I'm trying to install SQL 2005 standard edition as a named instance.
I receive this error : SQL Server could not connect to database service for server configuration.. [SQL Native client] Encryption not supported on the client. However I'm able to install client tools
The setup works fine on other box with the same config : SQL 2000/Windows XP, is there any work around for this issue ?
In my SQL 2000 client network utilty "Force proctocol encryption " is desabled and did not find the setting for SQL 2005 !
Hello,Is it necessary to upgrade the Client Connectivity Tools on all clientmachines after the SQL Server database server is upgraded from Version7.0 to 2000?Thank you in advance!Eddy
I have tried this on several different operating systems (VISTA and XP ) and several versions of SQL NATIVE CLIENT including 2005.90.3042.0
I have a 64 bit "SQL NATIVE CLIENT" connection that fails. The exact same connection and code succeeds on 32 bit. My customer and I prepend "oledb:" to the connection string and it starts working.
FAILS on 64 bit: Provider=SQLNCLI.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=Wrigley_Test;Data Source=MONGO;Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=RIPTIDE;Use Encryption for Data=False;Tag with column collation when possible=False;MARS Connection=False;DataTypeCompatibility=0;Trust Server Certificate=False
WORKS oledb:Provider=SQLNCLI.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=Wrigley_Test;Data Source=MONGO;Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=RIPTIDE;Use Encryption for Data=False;Tag with column collation when possible=False;MARS Connection=False;DataTypeCompatibility=0;Trust Server Certificate=False
I debugged my code to the point that I know it is happening when I call CreateAccessor for my SQL statement.
My site works fine in VWD2008 express, but I get this error when I try to use it on my live website. 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. According to this article: http://support.microsoft.com/kb/914277 I am supposed to:
1. Click Start, point to Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, and then click SQL Server Surface Area Configuration. Ok, there is no such program in this folder. The only thing in there is "SQL Server Error and Usage Reporting"... The other thing I am greatly concerned with is this: All is want is for my webpages to be able to access my database for user authentication. I DO NOT want to grant the internet rights to remote connect to my database.
Windows 2003 Server and all client PCs are all on the same network. I installed SQL 2005 std version on windows server 2003 and created a database and tables in it.
I have two users, who want to connect to SQL server 2005 from their PCs (they have windows XP):
These are two things that I need to facilitate:
1) They want to be able to write queries using Query Designer and run from their PCs.
2) I created an MS Access database on my PC, I want to use Access database as a front end to the SQL server database. I will create queries, forms in Access DB, and I want to be able to get the data from SQL server Database to do this. I guess I can use ODBC to connect to tables in SQL server database.
3) I want to connect SQL server to Oracle database, and run oracle stored procedures. I want to load the results of oracle stored procedures into SQL server database tables. I guess I will use IIS for this.
Any suggestions are appreciated, especially with item number 1.
I am trying to install SQL Server Express - (the non ADV version) and get the following error.
"An installation package for the product Microsoft SQL Server Native Client cannot be found. Try the installation again using a valid copy of the installation package 'sqlncli_x64.msi'".
I have 64 bit Vista Ultimate running on an HP dv9000.
I am using the download from the bottom of the download page for SSX where it says 64 bit version.
Prior to this I got the. "64-bit ASP.net is registered. Required 32-bit ASP.NET to install Microsoft Reporting services 2005(32-bit)." messagd during the pre-install scan. From what I gather in the posts, the reporting issue is different from my installation package problem.
I have been trying to prove a point to friends about how far you can go with SSX but am having no luck installing it. This whole process took 1 hour in XP but I've been stymied for 2 days.
I would appreciate being pointed at the right downloads for what seems to be a simple install.
I have installed SQL server 2005 enterprise edition on Windows 2003 virtual PC (full installation). The installation went through successfully. However, after install completed, I cannot find any of the client tools under the start menu -> all programs -> Microsoft SQL server 2005 menu. The only item listed under the SQL server 2005 is Configuration Tools, which is used to configure the database server.
I have tried to install the client component again (in case I didn't install them at the first place) but the installation process cannot be started since it detected that the client components have been installed already. I can also see the sql server native client running in the services.
The server engine is working fine since I can connect to that sql server using another machine where I have the client tool (SQL server management studio).
One of my friends has exactly the same problem. He installed the sql server 2005 Standard edition on windows 2003 server (full installation), but the client tools are not showing up in the start menu either.
I also checked the location for the SQL server management studio (Microsoft SQL server/90/Tools/Binn/VSShell/Common7/IDE), there is only one folder called publicAssemblies listed under. Is this correct or something is missing?
Hello,This is hopefully just a quick question. I'm looking to re-jig our in-house development infrastructure and part of that will be some sort of SQL Server product, and I'm hoping it will be the Developer edition.My question is, how many copies of the Developer edition would I need to purchase, if I have one Windows 2003 server (which will server the databases) and two client machines which will use it.My initial thought is 2 copies, one for each user (as the license states). But what about the server? Do I just install one of the two copies onto the server and the license covers the two client connections?This might seem a silly question with an obvious answer to you guys. However, am I right? I just need to get this clear in my head.Thanks in advance..
What is the ideal method that I can build client/server application by using IIS when I make my programme by using VB2005.net and SQL Server 2005 as database
Does SQL Server have a client tool similiar to Oracle's SQL Plus? If so, how do I set that up?
I have installed a desktop edition on my server, and I want to use some client to connect so that I can run queries from another machine. Am I set up correctly, or do I need to install the Enterprise edition on the server to do something like that.
I was thinking of writing a web-based client, but I can't seem to find the time. Plus, I wouldn't want to do that if a solution already exists.
Hi, A quick Q for all the Sql Server 2000 beta testers out there. Does anyone know of any problems associated with using SS2000 Enterprise Manager with a SS7 backend running SP2? In particular, I'm keen to try out the Tsql debugger features, if they'll work with SS7.
Many thanks in advance, Jon Reade, Sql Server 7 DBA NEC Technologies (UK) Ltd Telford, Shropshire.
I recently had configured my Web Server based on Windows 2003 Server and IIS 5x. I'd also installed SQL Server 2005 into this. Now I want toc onfigure this SQL Server, so that my client can access their database through a DNS name. I request you all for your kind support in this regard. Thanks in advance.
I recently have configured my Web Server based on Windows 2003 Server and IIS 5x. I'd also installed SQL Server 2005 into this. Now I want toc onfigure this SQL Server, so that my client can access their database through a DNS name. I request you all for your kind support in this regard. Thanks in advance.
I have recently configured a Web Server based on Windows 2003 Server and IIS 5x. I'd also installed SQL Server 2005 into this. Now I want toc onfigure this SQL Server, so that my client can access their database through a DNS name. I request you all for your kind support in this regard. Thanks in advance.
I get the following error and have been trying to figure out why I keep getting it. Initially, I had placed my project under wwwroot folder and ran it under IIS and it gave this error. Then I moved it to my local C drive and same thing. I am sharing this project with two other co-workers and all our config files and code files are same...they don't get this error but I do. I checked that SQL Server Client Network Utility has TCP/IP and the 'Named Pipes' enabled. I thought maybe I have setting in the Visual Studio 2005 that I'm not aware of that's causing this problem...it can't be the server since my co-workers aren't having this error and can't be anything in the code since all of us are sharing this project through vss. I dont' think using different version of .net framework can create this error. I changed the version from 2.0 to use 1.1x and it gave same error... Any help would be greatly appreciated. Thanks in advance.
Server Error in '/RBOdev' Application.
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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: 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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace:
[SqlException (0x80131904): 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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)] System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +739123 System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +188 System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject) +685966 System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject) +109 System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart) +383 System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +181 System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +170 System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +130 System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +28 System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +424 System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +66 System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +496 System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +82 System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105 System.Data.SqlClient.SqlConnection.Open() +111 System.Web.DataAccess.SqlConnectionHolder.Open(HttpContext context, Boolean revertImpersonate) +84 System.Web.DataAccess.SqlConnectionHelper.GetConnection(String connectionString, Boolean revertImpersonation) +197 System.Web.UI.WebControls.WebParts.SqlPersonalizationProvider.GetConnectionHolder() +16 System.Web.UI.WebControls.WebParts.SqlPersonalizationProvider.LoadPersonalizationBlobs(WebPartManager webPartManager, String path, String userName, Byte[]& sharedDataBlob, Byte[]& userDataBlob) +195 System.Web.UI.WebControls.WebParts.PersonalizationProvider.LoadPersonalizationState(WebPartManager webPartManager, Boolean ignoreCurrentUser) +95 System.Web.UI.WebControls.WebParts.WebPartPersonalization.Load() +105 System.Web.UI.WebControls.WebParts.WebPartManager.OnInit(EventArgs e) +497 System.Web.UI.Control.InitRecursive(Control namingContainer) +321 System.Web.UI.Control.InitRecursive(Control namingContainer) +198 System.Web.UI.Control.InitRecursive(Control namingContainer) +198 System.Web.UI.Control.InitRecursive(Control namingContainer) +198 System.Web.UI.Control.InitRecursive(Control namingContainer) +198 System.Web.UI.Control.InitRecursive(Control namingContainer) +198 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +692
Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET Version:2.0.50727.832
