Thanks for your reply.
I tried the code:
$conn = oci_connect("hr", "hr_pw", "DB_Name");
if (!$conn)
{ print("Errors begin-->>");
$e = oci_error(); // For oci_connect errors pass no handle
echo htmlentities($e['message']);
print("<<---Errors end");
}
and got the result...
Warning: oci_connect() [function.oci-connect]: _oci_open_server: > in d:\Inetpub\wwwroot\dev\test.php on line 3
Errors begin-->><<---Errors end
I typically don't use the "@" to preceed my OCI_Connect statement (as your code suggested.) The error above is from an OCI_Connect statment w/o any "@" symbol. When I try @OCI_Connect, no error displays whatsoever, but the connection still fails.
Yesterday I turned on Windows Security Auditing for all failures (on the Web Server.) I found that every failed attempt to connect to the db results in four entries to the Windows Security Log. Three of the entries are of Object type: File, and one (below) is of type: Mutant.
Object Open:
Object Server: Security
Object type: Mutant
Object Name: \BaseNamedObjects\RasPbFile
New Handle ID: -
Operation ID: {0,13851125}
Process ID: 840
Primary User Name: IUSR_D55TOT21
Primary Domain: Desert120
Primary Logon ID: (0x0, 0xCA7B9A)
Client User Name: -
Client Domain: -
Client Logon ID: -
Accesses DELETE
READ_CONTROL
WRITE_DAC
WRITE_OWNER
SYNCHRONIZE
Query mutant state
