Importing Asp.net files in Dreamweaver

I've created my website with Dreamweaver 8 under IIS root directory and I'm able
to test it on my local server. When I hit F12 on Dreamweaver a window pops up
and my website is running perfectly well:
http://localhost/mycoolwebsite/index.html

Ok, now I want to link a few of my webpages to some application I have created
using VWD. I have a few asp.net web pages (default.aspx, login.aspx...) on a
folder called webtools, also under my website folder. I have set up a testing
ASP.net server with drewmweaver but I'm unable to call any aspx pages and I get
the following error (see below) when I try to access them at
http://localhost/mycoolwebsite/webtools/nothing.aspx

Can anybody sed some light on that. Any help would be heartly appreciated.
Thanks in advance for taking some of your time off to help a newbie

Jeewai

 

Server Application Unavailable 

The web application you are attempting to access on this web server is currently
unavailable. Please hit the "Refresh" button in your web browser to
retry your request. 

Administrator Note: An error message detailing the cause of this specific
request failure can be found in the application event log of the web server.
Please review this log entry to discover what caused this error to occur.

Looks to me like your directory structure is wrong and the page is not being
found, also make sure you have deployed your BIN folder at the correct level,
can i ask where it is? (root or therwise)

Hope this helps

Thanks a lot TheFIsh for your quick help. After much shuffling around, I have
uploaded my website to the compagny's web server and encountered a brand new
error when trying to access an .aspx page.

Parser Error Message: It is an error to use a section registered as
allowDefinition='MachineToApplication' beyond application level.  This error can
be caused by a virtual directory not being configured as an application in IIS.

Source Error:





Line 18:             during development.
Line 19:         -->
Line 20:     <roleManager enabled="true" />
Line 21:     <compilation debug="true"/>
Line 22:     <!--

Source File: C:\Inetpub\newmedical\webtools\web.config    Line: 20 

Well, my application uses the default.aspx page as an entry portal and then
direct the user accordingly depending on the credentials entered on login.aspx.
I have used ASP.net admin tools to configure users and role. When in VWD, the
whole application runs without any hitches but then when accessed from the
website, this error appear.

Any ideas what went wrong. Thanks in advance for providing some much needed help
:)

JY

I'm guessing that you are using a hosted server which may be confirgure
differently from your localhost.

Do you have access to the live server directly or through a control panel?  If
you can access directly goto you IIS and select the site in question and make
sure you have started the application (righ click the site/folder name,
properties "Create".

HTH

Nice work indeed!the IT gurus have changed the permissions settings on the
company's webserver and I'm now able to access mu .aspx pages :-) However, the
authentication process is not going through. I can get to my default.aspx and
then when I hit the login button, my login.aspx page opens (in the website). But
upon entering the correct credentials, I get tghe following error message:

 
Server Error in '/newmedical/webtools' Application. 

Timeout expired.  The timeout period elapsed prior to completion of the
operation or the server is not responding.


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: Timeout expired.  The
timeout period elapsed prior to completion of the operation or the server is not
responding.

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): Timeout expired.  The timeout period elapsed prior
to completion of the operation or the server is not responding.]
   System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception,
Boolean breakConnection) +684883
   System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
stateObj) +207
   System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner,
Boolean& failoverDemandDone, String host, String failoverPartner, String
protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean
encrypt, Boolean integratedSecurity, SqlConnection owningObject, Boolean
aliasLookup) +890
   System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection
owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean
redirectedUserInstance) +601
   System.Data.SqlClient.SqlInternalConnectionTds..ctor(SqlConnectionString
connectionOptions, Object providerInfo, String newPassword, SqlConnection
owningObject, Boolean redirectedUserInstance) +159
  
System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions
options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection
owningConnection) +108
  
System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection
owningConnection, DbConnectionPool pool, DbConnectionOptions options) +28
   System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection
owningObject) +445
   System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection
owningObject) +66
   System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection
owningObject) +304
   System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection
owningConnection) +85
   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) +126
   System.Web.DataAccess.SqlConnectionHelper.GetConnection(String
connectionString, Boolean revertImpersonation) +239
   System.Web.Security.SqlMembershipProvider.GetPasswordWithFormat(String
username, Int32& status, String& password, Int32& passwordFormat,
String& passwordSalt, Int32& failedPasswordAttemptCount, Int32&
failedPasswordAnswerAttemptCount, Boolean& isApproved) +815
   System.Web.Security.SqlMembershipProvider.CheckPassword(String username,
String password, Boolean updateLastLoginActivityDate, Boolean failIfNotApproved,
String& salt, Int32& passwordFormat) +80
   System.Web.Security.SqlMembershipProvider.CheckPassword(String username,
String password, Boolean updateLastLoginActivityDate, Boolean failIfNotApproved)
+42
   System.Web.Security.SqlMembershipProvider.ValidateUser(String username,
String password) +78
   System.Web.UI.WebControls.Login.OnAuthenticate(AuthenticateEventArgs e) +161
   System.Web.UI.WebControls.Login.AttemptLogin() +94
   System.Web.UI.WebControls.Login.OnBubbleEvent(Object source, EventArgs e)
+101
   System.Web.UI.Control.RaiseBubbleEvent(Object source, EventArgs args) +35
   System.Web.UI.WebControls.Button.OnCommand(CommandEventArgs e) +115
   System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)
+134
  
System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBa
ckEvent(String eventArgument) +7
   System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl,
String eventArgument) +11
   System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +33
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint,
Boolean includeStagesAfterAsyncPoint) +5670

Does ASP.net website management (for roles and membership) create a db:
ASPNETDB.mdf ( for user credentials) only accessible by SQL server 2005? If
that's the case then no wonder the connection is timing out since the company's
server runs on Sql 2000 Entreprise. I can't install SQL server 2005 on the
server. Any idea to correct that problem?

Thanks in advance TheFIsh and others for your input.

JY