Hi,
Before I start, I have googled this problem for 2 weeks now,
have tried lots of suggestions on previous forums al lwith no luck.
You guys are my last hope!
Using Dreamweaver 8, SQL server (express edition) win XP pro
with IIS , .Net 2.0 framework, MDAC2.7
Heres the problem, I have the database setup all correctly,
can access it through the browser etc no problems there.
In dreamweaver 8, I create a new dynamic ASP VB Script page
connect to the same database - Bingo! everything works like a
charm.
I then change the site to use ASP.NET VB as a model (as this
is what I would like to develpop my app in), create an ASP.NET VB
page, go to the application panel click the + sign etc > choose
OLEDB then SQL server provider.
I select my server name, choose windows authentication as the
login method and then can see the dabase in the catalog box and
select it. (these are exactly the same settings as the ASP page
that I tested and worked).
I click the test button, "Test successfull" Fantastic I
think,
Press ok
Next window shows the connection string, I add a name for the
connection click the test and get the error message 'Http Error
code 500 - Internal server error'.
If I click ok, and then try and expand my database tables =
none.
________________________________
I have tried the following:
I don't think its a Database problem, a I have tried with
access, MySQL and SQL server all with the same result.
ASP works fine - ASP.NET fails. I have read on other forums
that ASP.NET 'remotely' connects to the testing server and this is
where the problem may lie.
I have copied MMScript directory to the root of my
c:\inetpub\www\root\ directory as this was also a suggestion.
I have added ALL accounts full access to this directory
(originally after just trying IIuser and the normal ones).
My testing server is local, in c:\inetpub\wwwroot\pbuyer\
//localhost/pbuyer (not infront of my dw at the mo but can
confirm it is setup correctly).
I can only think it is a permissions problem but as a last
resort I have given permissions to every account in all folders in
order to try and resolve the problem. Other posters have reported
the Macromedia could not replicate this and therefore could not
provide a solution, and from all posts on the internet there isn't
a fix.
Would reinstalling IIS be a goof idea?
Would really aprecciate someone posting a reply as I have hit
a brick wall!