I take back what I said about this being a really easy question - Microsoft produce in my opinion some of the best software in the marketplace and in most cases very easy to get to grips with, although some things they just haven't got right and this is one of them, I've never experienced such frustration trying to solve one "simple" problem before.
I have followed the instructions in both of the support pages you provided and neither has solved my problem, I even played around with the access setting in the SQL table I'm trying to publish to the web, I added a new User: WEBSERVER\IUSR_WEBSERVER and grated the same permission as was already provided in the dbo user, but alas to no avail.
I tried to add the guest account also but received an error indicating it could not map the guest account to a login ID .. then I tried to add it a few minutes later but this time without setting any permissions at all, and it allowed the guest account to be set up, yet each time I navigate to the page with the SQL table I receive the same error.
I really think Microsoft could make this area of their software far easier to work with, and I'm sure some diehards will insist it has to be this way because its to do with security, but it just doesn't work in a meaningful and logical manner. (sorry for griping, but I'm frustrated)
I've pretty much given up on solving this problem now, unless any incredibly clever person out there can suggest something else.
See
http://support.microsoft.com/default.aspx?ID=kb;en-us;Q247931
and
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_security_47u6.asp
Use Tools Site Settings Database to verify your connection (and set any credentials required for the SQL Server DB)
--
_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
To find the best Newsgroup for FrontPage support see:
http://www.frontpagemvps.com/FrontPageNewsGroups/tabid/53/Default.aspx
_____________________________________________
Hi Stefan,
Thanks for your reply. I don't mean to sound stupid but can you explain what you mean by checking the authorization strings? where
do I look and what do I look for.
I'm sorry if this is a really dumb question but I am "very" new to SQL Server
If you mean the connection method in SQL Server, I currently have that set to "Windows only" with the Administrator account
selected, although I have also tried "SQL Server and Windows" Authentication, but that didn't seem to make much difference. Maybe
I'm completely off the mark and looking at the wrong thing ... a step-by-step guide for idiots would be appreciated
Kind Regards,
Wayne
For OleDbException: Invalid authorization specification
Either the user identifier or the authorization string or both, as specified in the browse request connection string
(InConnectionString), violated restrictions defined by the data source.
Check your authorization strings
--
_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
To find the best Newsgroup for FrontPage support see:
http://www.frontpagemvps.com/FrontPageNewsGroups/tabid/53/Default.aspx
_____________________________________________
| Hello Mike,
| Thanks for your reply to my post, it's very appreciated.
|
| I had previously made a connection to the SQL Server database using the
| Database Results Wizard and connecting to an external source, in a similar
| way to how I would connect to an Access database.
|
| I've checked the code in the global.asa file as you suggested and found the
| following, which was automatically generated from the Database Results
| Wizard:
|
| Application("musicSQL_ConnectionString") = "DRIVER={SQL
| Server};SERVER=webserver;DATABASE=musicSQL"
|
| To the best of my knowledge, this is all correct .. the connection has been
| named 'musicSQL', the server is called 'webserver' and the SQL Database is
| called 'musicSQL', so I can't see any problem or obvious errors with this.
|
| However, when I open the page in my broswer to display a table from that
| database, the following error message is showing in my browser:
|
| Invalid authorization specification
|
| Description: An unhandled exception occurred during the execution of the
| current web request. Please review the stack trace for more information
| about the error and where it originated in the code.
|
| Exception Details: System.Data.OleDb.OleDbException: Invalid authorization
| specification
|
| I have to say I know little if nothing about what this all means and I'm
| feeling a bit frustrated that I can't seem to find an easy solution to what
| I expected would be a fairly straightforward problem.
|
| Does the above error message mean anything to you, and if so can you offer a
| solution or workaround?
|
| Thanks again
| Wayne
|
|
|
| | > Hi Wayne,
| >
| > The easiest method would be to alter the connection string in the
| global.asa produced by FP to one using the MS SQL system. There
| > are some differences but nothing that should be difficult to overcome.
| >
| > --
| > Mike -- FrontPage MVP '97 - '02
| >
http://www.websunlimited.com
| > FrontPage Add-in
| >
| >
| | > > I'm very new to SQL Server 2000 and I'm trying to find out how to use
| > > FrontPage 2003 to connect to a back-end SQL Server database and display
| > > individual tables, add and delete records etc but through a web page. I
| want
| > > web site visitors to be able to click a hyperlink to view one set of
| > > records, or another link to add a record to a table etc.
| > >
| > > I'm sure this is a really simple question but I've never done it before.
| I
| > > have used Access with .asp successfully in the past by adding that
| database
| > > to the fpdb directory within FrontPage and creating a connection to it,
| but
| > > I have no idea how to do the same thing with SQL Server databases.
| > >
| > > Any help, pointers or step-by-step instructions you can give will be
| really
| > > appreciated.
| > >
| > > Thanks in advance
| > > Wayne
| > >
| > >
| > >
| > >
| >
| >
|
|
