|
Home > Archive > Microsoft Content Management Server > July 2005 > "Offending SQL"
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| jason.hau@gmail.com 2005-07-14, 7:47 am |
| I recently applied a new windows update patch which resolved two
security flaws, one to do with color management, one to do with image
loopholes.
Once my machien rebooted however, my CMS repository appeared to have
been corrupted somehow.
On firing up the SCA, the following error message appears:
Unexpected Error! Failed to get General Global Settings
Extended error: [What='Offending SQL: SELECT * FROM Node WHERE Id = ?
;Unknown ODBC data type -11'] [LCID='1024'] [SourceFile='']
[SourceFileLine='-1'] [DebugInfo=''] [RecommendedAction='']
[ExtraInfo=''] [UniqueErrorId='4005'] [Severity='5'] [Source='(ISOK
File serverwrapper.cpp, Line 501)'] [CategoryId='0']
On trying to fire up Siet Manager, we get a similar error albeit for a
lookup on domains. The same bit of SQL is generated though, i.e. SELECT
* FROM Node WHERE Id = ?.
It looks like the CMS system account has become disassociated in some
way within the DB but a check of the database shows it to be there so
it looks like some kind of rights problem, possibly registry but I am
unable to track down exactly where.
System is XP, Service Pack 1.
CMS is 2002, SP1A'd.
SQL is 2000, SP4, local to the machine.
Any ideas would be gratefully received.
| |
| Stefan [MSFT] 2005-07-14, 5:51 pm |
| Hi Jason,
try to run the DCA again to connect again to the database.
Does this resolve the problem?
What happens if you connect a different MCMS server to the same database
does this work?
Cheers,
Stefan
--
This posting is provided "AS IS" with no warranties, and confers no rights
New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
----------------------
<jason.hau@gmail.com> wrote in message
news:1121346756.053906.102960@g14g2000cwa.googlegroups.com...
>I recently applied a new windows update patch which resolved two
> security flaws, one to do with color management, one to do with image
> loopholes.
>
> Once my machien rebooted however, my CMS repository appeared to have
> been corrupted somehow.
>
> On firing up the SCA, the following error message appears:
>
> Unexpected Error! Failed to get General Global Settings
>
> Extended error: [What='Offending SQL: SELECT * FROM Node WHERE Id = ?
> ;Unknown ODBC data type -11'] [LCID='1024'] [SourceFile='']
> [SourceFileLine='-1'] [DebugInfo=''] [RecommendedAction='']
> [ExtraInfo=''] [UniqueErrorId='4005'] [Severity='5'] [Source='(ISOK
> File serverwrapper.cpp, Line 501)'] [CategoryId='0']
>
> On trying to fire up Siet Manager, we get a similar error albeit for a
> lookup on domains. The same bit of SQL is generated though, i.e. SELECT
> * FROM Node WHERE Id = ?.
>
> It looks like the CMS system account has become disassociated in some
> way within the DB but a check of the database shows it to be there so
> it looks like some kind of rights problem, possibly registry but I am
> unable to track down exactly where.
>
> System is XP, Service Pack 1.
> CMS is 2002, SP1A'd.
> SQL is 2000, SP4, local to the machine.
>
> Any ideas would be gratefully received.
>
| |
| jason.hau@gmail.com 2005-07-14, 5:51 pm |
| Tried that, it doesn't fix it I'm afraid. Connecting to a completely
new one works fine. I tried getting somone to connect remotely and they
had exactly the same problem, offending SQL, etc. after they had
successfully changed over.
| |
| Stefan [MSFT] 2005-07-14, 5:51 pm |
| Hi Jason,
then you should open a support case for this.
Cheers,
Stefan
--
This posting is provided "AS IS" with no warranties, and confers no rights
New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
----------------------
<jason.hau@gmail.com> wrote in message
news:1121353867.517053.129310@g43g2000cwa.googlegroups.com...
> Tried that, it doesn't fix it I'm afraid. Connecting to a completely
> new one works fine. I tried getting somone to connect remotely and they
> had exactly the same problem, offending SQL, etc. after they had
> successfully changed over.
>
|
|
|
|
|