I have searched high and low to find out what this means... and I can't. My
connection to the SQL server from Frontpage 2003 database wizard worked then
suddenly didn't. What did I inadvertently change... if anything... Sounds
like an SQL isn't letting me retrieve..but I have no idea why...
Help"Cheryl" <Cheryl@.discussions.microsoft.com> wrote in message
news:71C7C35F-BA9F-4F25-81D5-8BB3E6005A63@.microsoft.com...
>I have searched high and low to find out what this means... and I can't. My
> connection to the SQL server from Frontpage 2003 database wizard worked
> then
> suddenly didn't. What did I inadvertently change... if anything... Sounds
> like an SQL isn't letting me retrieve..but I have no idea why...
> Help
What error message is being reported back by Frontpage?
Is the SQL Server running?
Did you install any service packs, upgrades, other software?
Rick Sawtell
MCT, MCSD, MCDBA|||That was what the browser was reporting: invalid authorization specification
in the database results wizard... Yet, when I coded my own connection instea
d
of using the wizard on a page.. It worked fine...
When I changed the authentication method on the server to send in clear text
as per:
http://support.microsoft.com/defaul...Q24793
1
It seemed to start to work again... Yet I recalled re-setting nothing of the
sort...
I was lead here by changing trusted_connection to yes and following the
message from there...
"Rick Sawtell" wrote:
> "Cheryl" <Cheryl@.discussions.microsoft.com> wrote in message
> news:71C7C35F-BA9F-4F25-81D5-8BB3E6005A63@.microsoft.com...
>
> What error message is being reported back by Frontpage?
> Is the SQL Server running?
> Did you install any service packs, upgrades, other software?
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>|||Hmmm..
Glad you got it working again.
I wonder if you have automatic updates turned on and it installed a service
pack for IIS or IE that may have reset that value...
Rick
"Cheryl" <Cheryl@.discussions.microsoft.com> wrote in message
news:FFA1F56D-C150-4665-AB3F-D4FDEC749002@.microsoft.com...[vbcol=seagreen]
> That was what the browser was reporting: invalid authorization
> specification
> in the database results wizard... Yet, when I coded my own connection
> instead
> of using the wizard on a page.. It worked fine...
> When I changed the authentication method on the server to send in clear
> text
> as per:
> http://support.microsoft.com/defaul...Q247
931
> It seemed to start to work again... Yet I recalled re-setting nothing of
> the
> sort...
> I was lead here by changing trusted_connection to yes and following the
> message from there...
> "Rick Sawtell" wrote:
>
Showing posts with label frontpage. Show all posts
Showing posts with label frontpage. Show all posts
Friday, March 9, 2012
invalid authorization specification error? Frontpage DB wizard
I have searched high and low to find out what this means... and I can't. My
connection to the SQL server from Frontpage 2003 database wizard worked then
suddenly didn't. What did I inadvertently change... if anything... Sounds
like an SQL isn't letting me retrieve..but I have no idea why...
Help"Cheryl" <Cheryl@.discussions.microsoft.com> wrote in message
news:71C7C35F-BA9F-4F25-81D5-8BB3E6005A63@.microsoft.com...
>I have searched high and low to find out what this means... and I can't. My
> connection to the SQL server from Frontpage 2003 database wizard worked
> then
> suddenly didn't. What did I inadvertently change... if anything... Sounds
> like an SQL isn't letting me retrieve..but I have no idea why...
> Help
What error message is being reported back by Frontpage?
Is the SQL Server running?
Did you install any service packs, upgrades, other software?
Rick Sawtell
MCT, MCSD, MCDBA|||That was what the browser was reporting: invalid authorization specification
in the database results wizard... Yet, when I coded my own connection instead
of using the wizard on a page.. It worked fine...
When I changed the authentication method on the server to send in clear text
as per:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q247931&ID=kb;en-us;Q247931
It seemed to start to work again... Yet I recalled re-setting nothing of the
sort...
I was lead here by changing trusted_connection to yes and following the
message from there...
"Rick Sawtell" wrote:
> "Cheryl" <Cheryl@.discussions.microsoft.com> wrote in message
> news:71C7C35F-BA9F-4F25-81D5-8BB3E6005A63@.microsoft.com...
> >I have searched high and low to find out what this means... and I can't. My
> > connection to the SQL server from Frontpage 2003 database wizard worked
> > then
> > suddenly didn't. What did I inadvertently change... if anything... Sounds
> > like an SQL isn't letting me retrieve..but I have no idea why...
> >
> > Help
>
> What error message is being reported back by Frontpage?
> Is the SQL Server running?
> Did you install any service packs, upgrades, other software?
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>|||Hmmm..
Glad you got it working again.
I wonder if you have automatic updates turned on and it installed a service
pack for IIS or IE that may have reset that value...
Rick
"Cheryl" <Cheryl@.discussions.microsoft.com> wrote in message
news:FFA1F56D-C150-4665-AB3F-D4FDEC749002@.microsoft.com...
> That was what the browser was reporting: invalid authorization
> specification
> in the database results wizard... Yet, when I coded my own connection
> instead
> of using the wizard on a page.. It worked fine...
> When I changed the authentication method on the server to send in clear
> text
> as per:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;Q247931&ID=kb;en-us;Q247931
> It seemed to start to work again... Yet I recalled re-setting nothing of
> the
> sort...
> I was lead here by changing trusted_connection to yes and following the
> message from there...
> "Rick Sawtell" wrote:
>> "Cheryl" <Cheryl@.discussions.microsoft.com> wrote in message
>> news:71C7C35F-BA9F-4F25-81D5-8BB3E6005A63@.microsoft.com...
>> >I have searched high and low to find out what this means... and I can't.
>> >My
>> > connection to the SQL server from Frontpage 2003 database wizard worked
>> > then
>> > suddenly didn't. What did I inadvertently change... if anything...
>> > Sounds
>> > like an SQL isn't letting me retrieve..but I have no idea why...
>> >
>> > Help
>>
>> What error message is being reported back by Frontpage?
>> Is the SQL Server running?
>> Did you install any service packs, upgrades, other software?
>>
>> Rick Sawtell
>> MCT, MCSD, MCDBA
>>
connection to the SQL server from Frontpage 2003 database wizard worked then
suddenly didn't. What did I inadvertently change... if anything... Sounds
like an SQL isn't letting me retrieve..but I have no idea why...
Help"Cheryl" <Cheryl@.discussions.microsoft.com> wrote in message
news:71C7C35F-BA9F-4F25-81D5-8BB3E6005A63@.microsoft.com...
>I have searched high and low to find out what this means... and I can't. My
> connection to the SQL server from Frontpage 2003 database wizard worked
> then
> suddenly didn't. What did I inadvertently change... if anything... Sounds
> like an SQL isn't letting me retrieve..but I have no idea why...
> Help
What error message is being reported back by Frontpage?
Is the SQL Server running?
Did you install any service packs, upgrades, other software?
Rick Sawtell
MCT, MCSD, MCDBA|||That was what the browser was reporting: invalid authorization specification
in the database results wizard... Yet, when I coded my own connection instead
of using the wizard on a page.. It worked fine...
When I changed the authentication method on the server to send in clear text
as per:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q247931&ID=kb;en-us;Q247931
It seemed to start to work again... Yet I recalled re-setting nothing of the
sort...
I was lead here by changing trusted_connection to yes and following the
message from there...
"Rick Sawtell" wrote:
> "Cheryl" <Cheryl@.discussions.microsoft.com> wrote in message
> news:71C7C35F-BA9F-4F25-81D5-8BB3E6005A63@.microsoft.com...
> >I have searched high and low to find out what this means... and I can't. My
> > connection to the SQL server from Frontpage 2003 database wizard worked
> > then
> > suddenly didn't. What did I inadvertently change... if anything... Sounds
> > like an SQL isn't letting me retrieve..but I have no idea why...
> >
> > Help
>
> What error message is being reported back by Frontpage?
> Is the SQL Server running?
> Did you install any service packs, upgrades, other software?
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>|||Hmmm..
Glad you got it working again.
I wonder if you have automatic updates turned on and it installed a service
pack for IIS or IE that may have reset that value...
Rick
"Cheryl" <Cheryl@.discussions.microsoft.com> wrote in message
news:FFA1F56D-C150-4665-AB3F-D4FDEC749002@.microsoft.com...
> That was what the browser was reporting: invalid authorization
> specification
> in the database results wizard... Yet, when I coded my own connection
> instead
> of using the wizard on a page.. It worked fine...
> When I changed the authentication method on the server to send in clear
> text
> as per:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;Q247931&ID=kb;en-us;Q247931
> It seemed to start to work again... Yet I recalled re-setting nothing of
> the
> sort...
> I was lead here by changing trusted_connection to yes and following the
> message from there...
> "Rick Sawtell" wrote:
>> "Cheryl" <Cheryl@.discussions.microsoft.com> wrote in message
>> news:71C7C35F-BA9F-4F25-81D5-8BB3E6005A63@.microsoft.com...
>> >I have searched high and low to find out what this means... and I can't.
>> >My
>> > connection to the SQL server from Frontpage 2003 database wizard worked
>> > then
>> > suddenly didn't. What did I inadvertently change... if anything...
>> > Sounds
>> > like an SQL isn't letting me retrieve..but I have no idea why...
>> >
>> > Help
>>
>> What error message is being reported back by Frontpage?
>> Is the SQL Server running?
>> Did you install any service packs, upgrades, other software?
>>
>> Rick Sawtell
>> MCT, MCSD, MCDBA
>>
Labels:
authorization,
connection,
database,
error,
frontpage,
invalid,
means,
microsoft,
mysql,
oracle,
searched,
server,
specification,
sql,
wizard
invalid authorization specification error? Frontpage DB wizard
I have searched high and low to find out what this means... and I can't. My
connection to the SQL server from Frontpage 2003 database wizard worked then
suddenly didn't. What did I inadvertently change... if anything... Sounds
like an SQL isn't letting me retrieve..but I have no idea why...
Help
"Cheryl" <Cheryl@.discussions.microsoft.com> wrote in message
news:71C7C35F-BA9F-4F25-81D5-8BB3E6005A63@.microsoft.com...
>I have searched high and low to find out what this means... and I can't. My
> connection to the SQL server from Frontpage 2003 database wizard worked
> then
> suddenly didn't. What did I inadvertently change... if anything... Sounds
> like an SQL isn't letting me retrieve..but I have no idea why...
> Help
What error message is being reported back by Frontpage?
Is the SQL Server running?
Did you install any service packs, upgrades, other software?
Rick Sawtell
MCT, MCSD, MCDBA
|||That was what the browser was reporting: invalid authorization specification
in the database results wizard... Yet, when I coded my own connection instead
of using the wizard on a page.. It worked fine...
When I changed the authentication method on the server to send in clear text
as per:
http://support.microsoft.com/default...;en-us;Q247931
It seemed to start to work again... Yet I recalled re-setting nothing of the
sort...
I was lead here by changing trusted_connection to yes and following the
message from there...
"Rick Sawtell" wrote:
> "Cheryl" <Cheryl@.discussions.microsoft.com> wrote in message
> news:71C7C35F-BA9F-4F25-81D5-8BB3E6005A63@.microsoft.com...
>
> What error message is being reported back by Frontpage?
> Is the SQL Server running?
> Did you install any service packs, upgrades, other software?
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
|||Hmmm..
Glad you got it working again.
I wonder if you have automatic updates turned on and it installed a service
pack for IIS or IE that may have reset that value...
Rick
"Cheryl" <Cheryl@.discussions.microsoft.com> wrote in message
news:FFA1F56D-C150-4665-AB3F-D4FDEC749002@.microsoft.com...[vbcol=seagreen]
> That was what the browser was reporting: invalid authorization
> specification
> in the database results wizard... Yet, when I coded my own connection
> instead
> of using the wizard on a page.. It worked fine...
> When I changed the authentication method on the server to send in clear
> text
> as per:
> http://support.microsoft.com/default...;en-us;Q247931
> It seemed to start to work again... Yet I recalled re-setting nothing of
> the
> sort...
> I was lead here by changing trusted_connection to yes and following the
> message from there...
> "Rick Sawtell" wrote:
connection to the SQL server from Frontpage 2003 database wizard worked then
suddenly didn't. What did I inadvertently change... if anything... Sounds
like an SQL isn't letting me retrieve..but I have no idea why...
Help
"Cheryl" <Cheryl@.discussions.microsoft.com> wrote in message
news:71C7C35F-BA9F-4F25-81D5-8BB3E6005A63@.microsoft.com...
>I have searched high and low to find out what this means... and I can't. My
> connection to the SQL server from Frontpage 2003 database wizard worked
> then
> suddenly didn't. What did I inadvertently change... if anything... Sounds
> like an SQL isn't letting me retrieve..but I have no idea why...
> Help
What error message is being reported back by Frontpage?
Is the SQL Server running?
Did you install any service packs, upgrades, other software?
Rick Sawtell
MCT, MCSD, MCDBA
|||That was what the browser was reporting: invalid authorization specification
in the database results wizard... Yet, when I coded my own connection instead
of using the wizard on a page.. It worked fine...
When I changed the authentication method on the server to send in clear text
as per:
http://support.microsoft.com/default...;en-us;Q247931
It seemed to start to work again... Yet I recalled re-setting nothing of the
sort...
I was lead here by changing trusted_connection to yes and following the
message from there...
"Rick Sawtell" wrote:
> "Cheryl" <Cheryl@.discussions.microsoft.com> wrote in message
> news:71C7C35F-BA9F-4F25-81D5-8BB3E6005A63@.microsoft.com...
>
> What error message is being reported back by Frontpage?
> Is the SQL Server running?
> Did you install any service packs, upgrades, other software?
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
|||Hmmm..
Glad you got it working again.
I wonder if you have automatic updates turned on and it installed a service
pack for IIS or IE that may have reset that value...
Rick
"Cheryl" <Cheryl@.discussions.microsoft.com> wrote in message
news:FFA1F56D-C150-4665-AB3F-D4FDEC749002@.microsoft.com...[vbcol=seagreen]
> That was what the browser was reporting: invalid authorization
> specification
> in the database results wizard... Yet, when I coded my own connection
> instead
> of using the wizard on a page.. It worked fine...
> When I changed the authentication method on the server to send in clear
> text
> as per:
> http://support.microsoft.com/default...;en-us;Q247931
> It seemed to start to work again... Yet I recalled re-setting nothing of
> the
> sort...
> I was lead here by changing trusted_connection to yes and following the
> message from there...
> "Rick Sawtell" wrote:
Wednesday, March 7, 2012
Intra-query parallelism ???
Hi,
Im using SQL 7.0 with FrontPage sending code to the dB.
Im getting the following error and dont understand what it means.
------
Database Results Error
Description: [Microsoft][ODBC SQL Server Driver][SQL Server]Intra-query parallelism caused your server command (process ID #13) to deadlock. Rerun the query without intra-query parallelism by using the query hint option (maxdop 1).
Number: -2147217900 (0x80040E14)
Source: Microsoft OLE DB Provider for ODBC Drivers
-----
The code is long and has several sub-queries.
All are looking to the same rows in the dB.
Im passing a parameter from FP. If I remove the parameter and hardcode the value I dont get this error.
Is this problem SQL or FP? If SQL what am I looking at?
Thanks for you help
MottyThis does happen if you're on a multi-processor server. The query is being splitted up for parallel processing. Unfortunately, they happen to block each other.
As the error suggests, you either rerun or use option hint (maxdop 1) to limit the processing to one processor.
Im using SQL 7.0 with FrontPage sending code to the dB.
Im getting the following error and dont understand what it means.
------
Database Results Error
Description: [Microsoft][ODBC SQL Server Driver][SQL Server]Intra-query parallelism caused your server command (process ID #13) to deadlock. Rerun the query without intra-query parallelism by using the query hint option (maxdop 1).
Number: -2147217900 (0x80040E14)
Source: Microsoft OLE DB Provider for ODBC Drivers
-----
The code is long and has several sub-queries.
All are looking to the same rows in the dB.
Im passing a parameter from FP. If I remove the parameter and hardcode the value I dont get this error.
Is this problem SQL or FP? If SQL what am I looking at?
Thanks for you help
MottyThis does happen if you're on a multi-processor server. The query is being splitted up for parallel processing. Unfortunately, they happen to block each other.
As the error suggests, you either rerun or use option hint (maxdop 1) to limit the processing to one processor.
Subscribe to:
Posts (Atom)