Search results matching tags 'ASP Classic' and '500 internal server error'

Cannot connect to mysql db 5.1

Perryvanz — Tue, 17 Nov 2009 15:40:06 GMT

Hello,

Im using IIS 7.5 with Windows server 2008 r2. I want to open my database, so I used the next connectstring for opening the db:

connect_string = "Driver={MySQL ODBC 5.1 Driver}; Server=localhost; UID=username; PWD=pwd; Database=db"
set dbConn = server.createObject("ADODB.connection")
dbConn.open(connect_string)

I'm getting this error....

Microsoft OLE DB Provider for ODBC Drivers error '80004005'

[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

What do I have to do to connect to my db?

Perry

http 500. Help, my form mail in wrong

coma — Sun, 10 May 2009 20:28:29 GMT

I have vista premium home and IIS 7

I am using dreamweaver cs3 and i beginner to asp.

My problem is that the ie says http 500.

My code of the page is

<%
theSchema="http://schemas.microsoft.com/cdo/configuration/"
Set cdoConfig=server.CreateObject("CDO.Configuration")
cdoConfig.Fields.Item(theSchema & "sendusing")= 2
cdoConfig.Fields.Item(theSchema & "smtpserver")="smtp.gmail.com"
cdoConfig.Fields.Update
set cdoMessage=Server.CreateObject("CDO.Message")
cdoMessage.Configuration=cdoConfig

cdoMessage.From="yourname@yourserver.com"
cdoMessage.To="yourname@yourserver.com"
cdoMessage.Subject="This is the message subject"
cdoMessage.TextBody="This is the message body"
cdoMessage.Send

Set cdoMessage=Nothing
Set cdoConfig=Nothing
%>

where is my mistake, that ie says http 500?

i found the code in a book of tutorial asp.

thanks

Re: Create Object Error

rrubin128 — Thu, 19 Mar 2009 00:41:37 GMT

I'm still stuck. I am attempting to instantiate a custom object via Server.CreateObject( "ISDBCom.ISDBManager" ) in the Application_onStart in global.asa. This is working on several other Windows Server 2003 installations. I haven't figured out what's different about this one. I'm getting:

Microsoft JScript runtime error '800a01ad'
Automation server can't create object

The DLL is present, and regsvr32'ed successfully. Possibilities:

File system security related. I've used procmon in the past to troubleshoot file access issues. Using procmon, I see the ProcID is found in the registry. But I don't see where w3wp.exe even attempts to open the DLL. I do see the OPEN on the working servers. I've tried running the AppPool as "Local System", but it still fails.
Not all dependent components are present. Depends.exe returns similar results on both the working and non-working installations. If dependencies are missing will I even see an attempted open via procmon?

Any other troubleshooting ideas? Thanks in advance.

Robert

Server.CreateObject http 500 internal error

dm78741 — Tue, 24 Feb 2009 14:19:00 GMT

This is a basic createa text file problem. I used another path to avoid the vista user account permissions as opposed to the wwwroot file, it worked fine with another file "FirstFile.asp" from the book "ASP programming for the absolute beginner". As a beginner, I had to ask... been trying different things for a long time without actually digging to far into IIS programming... please help...

here's the code for the "SecondFile.asp"

<html>
<title>Working with the File Object</title>
<body>
<b>A second example of working with the File object!</b>
<hr>

<%
set TestFile=Server.CreateObject("Scripting.FileSystemObject")
set TFileStream=TestFile.CreateTextFile("c:\Dfiles\docs\
Test2File.txt")
TFileStream.WriteLine "Welcome to the File Object in ASP!"
TFileStream.WriteBlankLines(3)
TFileStream.WriteLine "Between this line and the opening line are
three blank lines. These blank lines were inserted using the
WriteLine method of the TextStream object. Now, let's write three
more blank lines before the next section of text is inserted."
TFileStream.WriteBlankLines(3)
TFileStream.WriteLine "Okay, that's better--three more blank lines
have just been inserted! I think you probably get the idea of how to
use the WriteLine method, so let's move on to more interesting things."
TFileStream.Close
%>
</body>
</html>