error -2147467259 (0x80004005)

error -2147467259 (0x80004005)

am 24.11.2004 14:58:02 von Ahmed Onsi

Hello,
I recieve this code on my browser screen "-2147467259 (0x80004005)"
each time i load an ASP page; even the simplest one.
I even get the error for the http://localhost/

System : Windows XP Pro SP2 , IIS v5.1

Any Clue ?!
Thanks

Onsi

Re: error -2147467259 (0x80004005)

am 24.11.2004 15:24:45 von reb01501

Ahmed Onsi wrote:
> Hello,
> I recieve this code on my browser screen "-2147467259 (0x80004005)"
> each time i load an ASP page; even the simplest one.
> I even get the error for the http://localhost/
>
> System : Windows XP Pro SP2 , IIS v5.1
>
http://www.aspfaq.com/show.asp?id=2413

Bob Barrows
--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.

RE: error -2147467259 (0x80004005)

am 22.12.2004 23:15:03 von thomas

I got the same error, tried everything. All updates installed incl. JET,
MDAC, deinstalled IIS, installed it again. Copied the inetserv dir from
another one, rights checked, still got it. I think it is something with RPC,
because first time after reboot i got this message about RPC, sorry can't
reproduce at this time. I connect to Oracle, Mysql, MsSQL, Access, dbf all
kinds of rdbms'ss and always the same. So Inetserv or asp.dll is not the
problem I think. It has something to do with rpc*.dll in system32.
Got WinXP build 2600, no SP2 installed. I found that when it was patched it
did'nt work anymore, but don'nt when it started to fail for the first time?
if you do have a suggestion or solution, please advice.

"Ahmed Onsi" wrote:

> Hello,
> I recieve this code on my browser screen "-2147467259 (0x80004005)"
> each time i load an ASP page; even the simplest one.
> I even get the error for the http://localhost/
>
> System : Windows XP Pro SP2 , IIS v5.1
>
> Any Clue ?!
> Thanks
>
> Onsi
>
>
>

RE: error -2147467259 (0x80004005)

am 22.12.2004 23:21:01 von thomas

Yes sometime it shows:
The remote procedure call failed and did not execute
instead of -2147467259 (0x80004005), it occurs not only in IIS, but also
using MsSQL see other articles, so it must be something in common i think.
Focusing on IIS does't solve the problem for me.

"Thomas" wrote:

> I got the same error, tried everything. All updates installed incl. JET,
> MDAC, deinstalled IIS, installed it again. Copied the inetserv dir from
> another one, rights checked, still got it. I think it is something with RPC,
> because first time after reboot i got this message about RPC, sorry can't
> reproduce at this time. I connect to Oracle, Mysql, MsSQL, Access, dbf all
> kinds of rdbms'ss and always the same. So Inetserv or asp.dll is not the
> problem I think. It has something to do with rpc*.dll in system32.
> Got WinXP build 2600, no SP2 installed. I found that when it was patched it
> did'nt work anymore, but don'nt when it started to fail for the first time?
> if you do have a suggestion or solution, please advice.
>
> "Ahmed Onsi" wrote:
>
> > Hello,
> > I recieve this code on my browser screen "-2147467259 (0x80004005)"
> > each time i load an ASP page; even the simplest one.
> > I even get the error for the http://localhost/
> >
> > System : Windows XP Pro SP2 , IIS v5.1
> >
> > Any Clue ?!
> > Thanks
> >
> > Onsi
> >
> >
> >

RE: error -2147467259 (0x80004005)

am 24.03.2005 02:23:05 von Brett Trotter

I also have Win XP SP2 and I can run ASP.NET pages just fine, even ones that
query an MS SQL server, but any plain .asp page gives me the "-2147467259
(0x80004005)" error.

Has anyone come up with a finite solution? I've reinstalled IIS and asp
framework, etc. What aren't I getting right?

"Ahmed Onsi" wrote:

> Hello,
> I recieve this code on my browser screen "-2147467259 (0x80004005)"
> each time i load an ASP page; even the simplest one.
> I even get the error for the http://localhost/
>
> System : Windows XP Pro SP2 , IIS v5.1
>
> Any Clue ?!
> Thanks
>
> Onsi
>
>
>

Re: error -2147467259 (0x80004005)

am 24.03.2005 03:16:29 von reb01501

Search for your error at www.aspfaq.com and www.iisfaq.com

Brett Trotter wrote:
> I also have Win XP SP2 and I can run ASP.NET pages just fine, even
> ones that query an MS SQL server, but any plain .asp page gives me
> the "-2147467259 (0x80004005)" error.
>
> Has anyone come up with a finite solution? I've reinstalled IIS and
> asp framework, etc. What aren't I getting right?
>
> "Ahmed Onsi" wrote:
>
>> Hello,
>> I recieve this code on my browser screen "-2147467259 (0x80004005)"
>> each time i load an ASP page; even the simplest one.
>> I even get the error for the http://localhost/
>>
>> System : Windows XP Pro SP2 , IIS v5.1
>>
>> Any Clue ?!
>> Thanks
>>
>> Onsi

--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

Re: error -2147467259 (0x80004005)

am 24.03.2005 17:23:08 von ten.xoc

> I also have Win XP SP2 and I can run ASP.NET pages just fine, even ones
that
> query an MS SQL server, but any plain .asp page gives me the "-2147467259
> (0x80004005)" error.

Unfortunately, you forgot to include the TEXT of the error message. So, the
best I can do is guide you here:
http://www.aspfaq.com/80004005

Re: error -2147467259 (0x80004005)

am 27.03.2005 03:19:05 von BrettTrotter

Actually there wasn't any text, just those two numbers.

In any case, i ditched XP and installed win 2k, worked without having to do
anything at all.

"Aaron [SQL Server MVP]" wrote:

> > I also have Win XP SP2 and I can run ASP.NET pages just fine, even ones
> that
> > query an MS SQL server, but any plain .asp page gives me the "-2147467259
> > (0x80004005)" error.
>
> Unfortunately, you forgot to include the TEXT of the error message. So, the
> best I can do is guide you here:
> http://www.aspfaq.com/80004005
>
>
>

Re: error -2147467259 (0x80004005)

am 07.04.2005 14:52:05 von lexic0n

I had this exact same issue. It took a lot of digging but I finally
solved my problem. In IIS, I went to the properties for the virtual
directory giving me trouble and set the application protection to Low.
I'm not sure why this works, but it appears to have fixed the issue.

I hope this helps someone else and saves them some time!