If I have 2 MS SQL Databases, one as Production and the other as Backup. The Production updates the data on the Backup. WHat I want to do is to test the the Production database is still online and if not I want to change the connection string to point to the Backup. I want to this via ASP.
I'm running IIS under windows XP, and developing an ASP web page locally. My problem is that I can't get it to work without connecting to the internet. Am I doing something wrong, or does ASP require a redundant connection in order to run?
I have a page that simply displays the current time. If I'm connected and press the refresh button the displayed time is updated. If I disconnect, then the time displayed remains unchanged even after hitting the refresh button.
I have a page where I am connecting to more than one server. I want to set it up so that if one of those connection fails it does not kill the whole page.
The page would still load but just display a little error message about the one failure - the other connection and code would still be executed... is this possible?
I'm running IIS under windows XP, and developing an ASP web page locally. My problem is that I can't get it to work without connecting to the internet. Am I doing something wrong, or does ASP require a redundant connection in order to run?
I have a page that simply displays the current time. If I'm connected and press the refresh button the displayed time is updated. If I disconnect, then the time displayed remains unchanged even after hitting the refresh button.
How do test my web application for concurrent users (how much concurent user connect at a time and how traffice will be affected and what will the response time?) and how it is done, how long it will takes, does it interfere with current site, etc.?
Reagarding the number of users the site will accomodate is it based on where it's hosted
test my app? it's still in development but it's very much usable. i'm looking for few good object oriented souls that can look at this. i'm still adding few functions so don't be surprised if it goes down for a VERY short time (minutes really).
I need to revisit cookie testing. On the home page and every product page I write a cookie. I do this because some users enter by direct links to product pages.
<% Response.Cookies("cookietest") = ("49") Response.Cookies("cookietest").Expires = Date + 2 %>
On the cart page I test for the cookie...
<% If Request.Cookies("cookietest") <"49" Then Response.Redirect("err.asp?e=1") End If %>
I have a user that insists he has cookies enabled, yet he keeps getting redirected to my error page which suggests he does not have cookies enabled. What could cause this? Is the above too simple for all circumstances?
Is there more extensive code that I could setup on a hidden page where I can send users to get read out on how they actually have their browsers setup? i.e. Run a test on their browser and the results are emailed to me.
I know very little about ASP and ASPX pagfes but i inherited a web site done by a guy who knew just a little more than me and I've worked around things with my knowledge of HTML and Javascript, as well as added on to the web site using Cold Fusion. But I am at a point that I need to be able to do more.
I have a ASPX page with a Log In button that I don't want see if a certain cookie exists. Is there a way to test for that cookie on the page and display or not display something based on that test?
my system is at testing phase. how do i test my system to check its security especially at the login page? i am running it at localhost. i have tried sql injection but nothing happened. i just saw the invalid login username or password error only.
I have created a page that will allow all web based errors generated to be logged, like IIS errors 404, 403,401, 400.
I am now testing to see if the correct files are being displayed when the errors occur. I am able to replicate the 404 err as well as the 403 error, bu I cannot test the 401 or 400 errors. Does anyone know how to do this?
I tried using err.raise, but it doesnt seem to work, unless i m doing something wrong.
I need to test ASP pages at home before uploading them (no net connectiona t home, only here at uni and I need the site owrking before I transfer it). The ASP pages are written, PWS is installed (except for some file that had an error - but that didn't install last time and everything worked fine then). Where do I put the ASP pages and DB and how do I set up a connection between them? The pages run in IE at the moment but no data is pulled onto them from the DB.
I've been given a task to develop an automated unit testing framework for a project I'm workin on...
I've spotted ASPUnit on sourcesafe... but it doesn't seem to handle situations when we have global variables, session stuff etc...
I was thinking of doing something to a screenscrape and just do a file comparison... actually, there ARE ways to do this aren't there? I've heard/read about that before.. some HTTP objects or something that would allow me to call an asp page, and grab the output as a string.. rather than have the output go to a screen... anyone able to point me i the direction of this kinda stuff?
I need to test if cookies are enabled in the browser. I disabled cookies in my browser and rebooted my browser, yet the below code still writes a cookie and reads it correctly.
<% Response.Cookies("smcookietest") = ("8") Response.Cookies("smcookietest").Expires = Date + 2 %> <% If Request.Cookies("smcookietest") <> "8" Then Response.Redirect("error.asp?error=19") End If %> <%=Request.Cookies("smcookietest")%>
I am developing a Testing Checklist for the Programmers in my company. As i am not a programmer, Can you guys help me.
I am looking for some common Code testing steps which a programmer should do when he is testing his web application
These testing checklist could include common mistakes programmers do or any special coding error which they might receive when they are testing their web application.
I had a mild hack of the default windows web page in inetpub because I was running IIS whilst my DSL connection was on. Ever since,I have disconnected the DSL before running IIS.
Could anyone give me advice on running IIS safely as a local testing server (for asp pages) whilst online? I have to admit that I run an admin account (win2000) so I know this is one thing I should change
I have built a testing app that, if the wrong answer is selected will display the section of a manual that the question/answers come from as well as the correct answer (this is how the bosses wanted it) and then they have to answer the question correctly before moving on to the next question.
Now they have changed their minds slightly. After the person misses it the first time it only displays the section of the manual. If they miss it a second time it displays the manual and the correct answer.
I am a tester trying to test a web based application designed in ASP. I want to know ways I can test that ASP page.What are the ASP related issues that I should keep in mind.
What ASP or Javascripts should I put in URL or anywhere so that I can generate errors. Dont tell now to go to Testing forum because I want ASP professional to guide me out because they are best who know how to deal with the ASp codes.
In ASP (vbscript) is there a way to check to see if a SQL server is online before trying to open a connection?
I have a situation where we have a SQL server that may be offline for a couple minutes and right the ASP page returns:
Microsoft OLE DB Provider for SQL Server error '80004005'
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
I'd like to be able to first check to make sure the server is available and if NOT, then skip the database connection on that page altogether. Or, at least load the page without showing the error. I have on error resume next but it still displays this error.
I have been teaching myself ASP for several months now and seem to have a pretty good handle on it. All along, I have been uploading changed files directly to the website and refreshing to test.
However, today I will be at a location with no internet access and would still like to be able to work and test my programming. How do I go about testing ASP pages on my local computer without an internet connection?
For now I am not worried about testing any databases or anything, just layout and design.
If it is useful, I am running Windows XP Home edition and I use Dreamweaver to write the ASP.
I am working on a site to provide displaying and navigation of images from several groups and have the following code that changes to displayed gif based on the query string passed in:
Call: <a href="ShowImage.asp?group=01&image=01&max=28">Group 01, Image 04, Max 28</a> Code:
I'm using Dreamweaver for a number of ASP sites and long ago set up testing servers for each, which worked fine. Now they don't - I just get a 404 message. I've double-checked the testing server address and HTTP address and nothing's changed, so I'm wondering if the address of localhost can have been altered? I've forgotten how to check it, though. Can anyone point me in the right direction?I should say that the only thing that has changed since I last did some testing is that I've downloaded IE7 - is that a clue?
I would like to test two recordsets to determine if they have the same number of records, and that those records are identical for the equivalent rows.
Is there an elegant way to do this? My only solution so far involves some rather inefficient looping. Even a solution using a clever query in a stored procedure would be nice.
I trying to run a sample asp web application, using IIS as a localhost testing server. I have created a virual directory called global with path C:/global/asp/. I also have a another website sitting in the default root folder in intpub/wwwroot. then i use localhost my old website home page starts up not my virtual directory site global if I type localhost/global/asp/filename.asp, I get cant find.
What am I doing wrong, what do I have to do to get virtual directory site to run and not the old site in wwwroot folder. I start and stop IIS from the right click from the default web site.
anyways, after i installed IIS (i'm running XP SP2) everything seemed to go good, until i tested ASP, i get a 500 error / page cannot be displayed.
but this is the real error -2147467259 (0x80004005)
i have no idea what this means, and i did a bit of a search on google on this, but i didn't find anything helpful - so i ran a search for asp forums and this came up - so here i am.
in case you want to know, my web server is running (i CAN see html files via the localhost url) but asp just won't go (i'm trying to view the default asp file) and i have no idea what's wrong (i DID restart my PC, and all services that might be related to anything internet are turned ON)
I was working on an asp and it was working fine. I came back to it a few days later and it was no longer working... When I submit a form through the ASP page, it only spits back the raw code, but doesn't write to access as it was before... I don't know what has chenged. Any suggestions? Code:
I have a SQL server db set up locally. I have a local DSN set up. I have DW connected to the SQL server db and can create Bindings and use Server Behaviors without any problem. When I try to test the site locally in the browser, I get the following error:
"Microsoft OLE DB Provider for ODBC Drivers (0x80004005) [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database "xxxxxxx" requested by the login. The login failed."