Hidden Property - "Deserialization failed: is not a Valid Value" E

If I add an expression to the visibility property on a text box, table row,
etc.. and then remove that same expression, I get the following error message
in preview:
"deserialization failed: is not a valid value..."
I get an option to edit the XML code. When I look at the code, I find the
<Hidden /> tag. But get this, there is no </Hidden> tag. Apparently, VS is
removing only one side of the Hidden tag when I delete the expression.
I used to be able to edit the code, but now I can't even edit the code to
take the remaining tag out. With this error my rdl file became, for all
intents and purposes, corrupt. Luckily I had posted it to a dev Report
Manager site earlier and was able to recover it.
Has anyone seen this?
Also, not being able to close VS2005 because of the the "Modal Dialog
Open..." box is killing me. Anyone have a solution to that yet besides
killing the devenv process?
Thanks in Advance,
bsod55I just had a similar error - I had to open the file and remove the Hidden
tags. In the IDE I right clicked on the file and selected Open from the menu
- this gave me the XML version and allowed me to remove the tags.
--
mal
"bsod55" wrote:
> If I add an expression to the visibility property on a text box, table row,
> etc.. and then remove that same expression, I get the following error message
> in preview:
> "deserialization failed: is not a valid value..."
> I get an option to edit the XML code. When I look at the code, I find the
> <Hidden /> tag. But get this, there is no </Hidden> tag. Apparently, VS is
> removing only one side of the Hidden tag when I delete the expression.
> I used to be able to edit the code, but now I can't even edit the code to
> take the remaining tag out. With this error my rdl file became, for all
> intents and purposes, corrupt. Luckily I had posted it to a dev Report
> Manager site earlier and was able to recover it.
> Has anyone seen this?
> Also, not being able to close VS2005 because of the the "Modal Dialog
> Open..." box is killing me. Anyone have a solution to that yet besides
> killing the devenv process?
> Thanks in Advance,
> bsod55

help-login failed for MACHINE_NAME\IUSR_MACHINE_NAME

HI,
i have some problem,

one database 'SMS' is installed in sql server which instance is
BARODA\EMIS.

now i want to connect my web app to this database.
for that
my connectionstring is
--
conn.ConnectionString = "workstation id=BARODA;packet size=4096;integrated security=SSPI;data source=BARODA\EMIS;persist security info=True;initial catalog=SMS"
--

but when i run this error occur

--
login failed for 'MERIDIAN\IUSR_BARODA'
--

for that what should i do?
give any solution.

it's urgent.

thanks in advance.Hi,

This blog might help you:http://weblogs.asp.net/coltk/archive/2003/07/10/9920.aspx

Colt|||hey, colt

my problem,

i want to creat user in MSDE.

how to create user in MSDE?
how to create user in MSDE during app. installation?

give any solution.
it's urgent.

thanks in advance.

Help: SQL Server 2000 failed to restart after NT Server reboot

Hi,
We have a NT Server that's set to reboot every weekend. SQL server
2000 and SQL Server Agent were set to auto-restart after reboot. It's
been working fine for a long time.
But several weeks ago,both SQL server and SQL server agent didn't
restart after the reboot so all DTS jobs didn't run until we manually
restart the Server and the server agent. We didn't receive any error
message and event log didn't
have any error either. It did show the SQL server was shut down by
request and the server agent was stoped successfully. But there's no
log about the server starting and ready for client connection. The
services are set with local system account.
We have a utility to check the connection to the server and it came
back with error of "[Shared Memory]SQL Server does not exist or access
denied. [Shared Memory]ConnectionOpen (Connect())"
If the SQL server was never asked to restart by the OS, what could be
the reason and how can I fix it?
Thanks a lot.
Ping LiWhat are you getting with issuing the command OSQL -L at the
commandline. Did you try to restart the SQL Server service the Service
Panel in Windows ? If not, do so and see if the server is coming u and
if not what kind of error message you are getting here. There must be
some event log message if the SQl Server doesnt=B4start up properly
(even if it does there is an entry). Is your event log outta space ?
HTH, Jens Suessmeyer.|||Hi, Jens,
Thanks for your reply. I tried OSQL -L and the result is:
(local)
commserver\commvaultqinetix
digital
zpm
I have no idea what it means.
We were able to restart the SQL server every time it failed to start
automatically after reboot. There's no entry about the server at all.
The last entry is the sql server was shut down by request(we schedule
the task) and the server agent was stopped successfully.
There is no error about the event log out of space. Can you guess what
the possible reason for the failure? They were set to restart
automatically.
Thank you for your help.
Ping
I have no idea what it means.|||Hi
You may want to post the SQL Server log for when the server failed to
re-boot as this should have more information as to why it failed. You may
also want to see if anything was logged in the event log.
As something to test the server is available you may want to use SQL Ping
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=26 you will need a
processs that parses the output to see if the given server is there.
John
"pli@.umn.edu" <pingli@.gmail.com> wrote in message
news:1128568970.436836.215890@.f14g2000cwb.googlegroups.com...
> Hi,
> We have a NT Server that's set to reboot every weekend. SQL server
> 2000 and SQL Server Agent were set to auto-restart after reboot. It's
> been working fine for a long time.
> But several weeks ago,both SQL server and SQL server agent didn't
> restart after the reboot so all DTS jobs didn't run until we manually
> restart the Server and the server agent. We didn't receive any error
> message and event log didn't
> have any error either. It did show the SQL server was shut down by
> request and the server agent was stoped successfully. But there's no
> log about the server starting and ready for client connection. The
> services are set with local system account.
> We have a utility to check the connection to the server and it came
> back with error of "[Shared Memory]SQL Server does not exist or access
> denied. [Shared Memory]ConnectionOpen (Connect())"
> If the SQL server was never asked to restart by the OS, what could be
> the reason and how can I fix it?
> Thanks a lot.
> Ping Li
>|||Hi, John,
Thanks for your reply.
As my previous posts said, there weren't any event log in the event
viewer after the shut down. The last 2 log entries were: SQL Server
was shut down by request. SQL Server agent was stopped successfully.
I couldn't find any log or information specifying why the server failed
to reboot. I'm trying to find out what the possible causes are so that
I know which direction to go. But so far nothing from the server log
showed up. It just disappeared in nowhere.
Thanks again and hope you can help.
Ping

Help: SQL Server 2000 failed to restart after NT Server reboot

Hi,
We have a NT Server that's set to reboot every weekend. SQL server
2000 and SQL Server Agent were set to auto-restart after reboot. It's
been working fine for a long time.
But several weeks ago,both SQL server and SQL server agent didn't
restart after the reboot so all DTS jobs didn't run until we manually
restart the Server and the server agent. We didn't receive any error
message and event log didn't
have any error either. It did show the SQL server was shut down by
request and the server agent was stoped successfully. But there's no
log about the server starting and ready for client connection. The
services are set with local system account.
We have a utility to check the connection to the server and it came
back with error of "[Shared Memory]SQL Server does not exist or access
denied. [Shared Memory]ConnectionOpen (Connect())"
If the SQL server was never asked to restart by the OS, what could be
the reason and how can I fix it?
Thanks a lot.
Ping LiWhat are you getting with issuing the command OSQL -L at the
commandline. Did you try to restart the SQL Server service the Service
Panel in Windows ? If not, do so and see if the server is coming u and
if not what kind of error message you are getting here. There must be
some event log message if the SQl Server doesnt=B4start up properly
(even if it does there is an entry). Is your event log outta space ?
HTH, Jens Suessmeyer.|||Hi, Jens,
Thanks for your reply. I tried OSQL -L and the result is:
(local)
commserver\commvaultqinetix
digital
zpm
I have no idea what it means.
We were able to restart the SQL server every time it failed to start
automatically after reboot. There's no entry about the server at all.
The last entry is the sql server was shut down by request(we schedule
the task) and the server agent was stopped successfully.
There is no error about the event log out of space. Can you guess what
the possible reason for the failure? They were set to restart
automatically.
Thank you for your help.
Ping
I have no idea what it means.

Help: SQL Server 2000 failed to restart after NT Server reboot

Hi,
We have a NT Server that's set to reboot every weekend. SQL server
2000 and SQL Server Agent were set to auto-restart after reboot. It's
been working fine for a long time.
But several weeks ago,both SQL server and SQL server agent didn't
restart after the reboot so all DTS jobs didn't run until we manually
restart the Server and the server agent. We didn't receive any error
message and event log didn't
have any error either. It did show the SQL server was shut down by
request and the server agent was stoped successfully. But there's no
log about the server starting and ready for client connection. The
services are set with local system account.
We have a utility to check the connection to the server and it came
back with error of "[Shared Memory]SQL Server does not exist or access
denied. [Shared Memory]ConnectionOpen (Connect())"
If the SQL server was never asked to restart by the OS, what could be
the reason and how can I fix it?
Thanks a lot.
Ping Li
What are you getting with issuing the command OSQL -L at the
commandline. Did you try to restart the SQL Server service the Service
Panel in Windows ? If not, do so and see if the server is coming u and
if not what kind of error message you are getting here. There must be
some event log message if the SQl Server doesnt=B4start up properly
(even if it does there is an entry). Is your event log outta space ?
HTH, Jens Suessmeyer.
|||Hi, Jens,
Thanks for your reply. I tried OSQL -L and the result is:
(local)
commserver\commvaultqinetix
digital
zpm
I have no idea what it means.
We were able to restart the SQL server every time it failed to start
automatically after reboot. There's no entry about the server at all.
The last entry is the sql server was shut down by request(we schedule
the task) and the server agent was stopped successfully.
There is no error about the event log out of space. Can you guess what
the possible reason for the failure? They were set to restart
automatically.
Thank you for your help.
Ping
I have no idea what it means.

HELP: SP4 Version?

I am convinced we do not have SQL 2000 SP4 installed but the console says I
do. After a few failed installation of SP4 I cannot imagine it is truly
installed.
It says: 8.00.2039 (SP4)
Do I REALLY have SP4?
@.@.version of 8.00.2039 seems correct.
"Whispering Leaf" wrote:

> I am convinced we do not have SQL 2000 SP4 installed but the console says
I
> do. After a few failed installation of SP4 I cannot imagine it is truly
> installed.
> It says: 8.00.2039 (SP4)
> Do I REALLY have SP4?
>
>

HELP: SP4 Version?

I am convinced we do not have SQL 2000 SP4 installed but the console says I
do. After a few failed installation of SP4 I cannot imagine it is truly
installed.
It says: 8.00.2039 (SP4)
Do I REALLY have SP4?
:)@.@.version of 8.00.2039 seems correct.
"Whispering Leaf" wrote:
> I am convinced we do not have SQL 2000 SP4 installed but the console says I
> do. After a few failed installation of SP4 I cannot imagine it is truly
> installed.
> It says: 8.00.2039 (SP4)
> Do I REALLY have SP4?
> :)
>

HELP: SP4 Version?

I am convinced we do not have SQL 2000 SP4 installed but the console says I
do. After a few failed installation of SP4 I cannot imagine it is truly
installed.
It says: 8.00.2039 (SP4)
Do I REALLY have SP4?

@.@.version of 8.00.2039 seems correct.
"Whispering Leaf" wrote:

> I am convinced we do not have SQL 2000 SP4 installed but the console says I
> do. After a few failed installation of SP4 I cannot imagine it is truly
> installed.
> It says: 8.00.2039 (SP4)
> Do I REALLY have SP4?
>
>

HELP: Merge Agent failed - Error number: MSSQL_REPL-2147199402)

We have 50+ clients that use a pull merge subscription. There are 2
databases and each databases has only 1 publication. Each client has ONE
subscription to each of the 2 databases.
We had to set the retention to unlimited to avoid the following error:
The Merge Agent failed after detecting that retention-based metadata cleanup
has deleted metadata at the Publisher for changes not yet sent to the
Subscriber. You must reinitialize the subscription (without upload).
(Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199402)
Get help: http://help/MSSQL_REPL-2147199402
The article http://support.microsoft.com/kb/919929/kb/919929 has a hotfix
BUT it says that it is if a Subscriber subscribes to two publications in the
same Subscriber database. This is not the case.
We had a ticket open with Miscrosoft but they were unable to find the
solution for it after 4 or 5 weeks.
The clients use their subscription databases directly and they are synced to
the server every 30 minutes.
Anybody have any idea what is causing this and how to solve this problem.
The LDF's are getting quite large and we need to find a solution soon.
Thanks in advance!
I fail to understand how the ldf's fit in here. It sounds like there are
some long running transactions which transcend the log dump boundaries. Have
you investigated what these open transactions are? Are they replication
related?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"RichardD" <RichardD@.discussions.microsoft.com> wrote in message
news:B0445940-5C26-403B-8589-692458B82098@.microsoft.com...
> We have 50+ clients that use a pull merge subscription. There are 2
> databases and each databases has only 1 publication. Each client has ONE
> subscription to each of the 2 databases.
> We had to set the retention to unlimited to avoid the following error:
> The Merge Agent failed after detecting that retention-based metadata
> cleanup
> has deleted metadata at the Publisher for changes not yet sent to the
> Subscriber. You must reinitialize the subscription (without upload).
> (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199402)
> Get help: http://help/MSSQL_REPL-2147199402
> The article http://support.microsoft.com/kb/919929/kb/919929 has a hotfix
> BUT it says that it is if a Subscriber subscribes to two publications in
> the
> same Subscriber database. This is not the case.
> We had a ticket open with Miscrosoft but they were unable to find the
> solution for it after 4 or 5 weeks.
> The clients use their subscription databases directly and they are synced
> to
> the server every 30 minutes.
> Anybody have any idea what is causing this and how to solve this problem.
> The LDF's are getting quite large and we need to find a solution soon.
> Thanks in advance!
>
|||I also expect, the size of the log file has nothing to do with your
retention period.
I'm afraid I can't help on your retention period problem, but perhaps
your ldfs are growing because of a combination of the recovery model
your database is using, and your backup strategy.
Have a look at the following articles, perhaps they will help:
http://msdn2.microsoft.com/en-us/library/ms175987.aspx
http://msdn2.microsoft.com/en-us/library/ms175495.aspx
Tim Hill
On Feb 23, 6:24 pm, "Hilary Cotter" <hilary.cot...@.gmail.com> wrote:[vbcol=seagreen]
> I fail to understand how the ldf's fit in here. It sounds like there are
> some long running transactions which transcend the log dump boundaries. Have
> you investigated what these open transactions are? Are they replication
> related?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTShttp://www.indexserverfaq.com
> "RichardD" <Richa...@.discussions.microsoft.com> wrote in message
> news:B0445940-5C26-403B-8589-692458B82098@.microsoft.com...
>
>
>
>
|||You are right. I have already fixed the issue with the log files.
Regarding the error MSSQL_REPL-2147199402 we suspect that the subscribers
changed their computer date beyond 14 days (default retention) and it caused
this error.
One reason we suspect this is that out of 40+ subscribers to the one
publication, only a few had this problem and a couple of them had it happen
twice.
Does this sound like a possibility to you?
We are about to change their retention from unlimited back to 14 days. Is
there anything we should be aware of before doing this?
Thanks so much for your help.
|||Yes, we figured out the log file issue. Thank you anyway.
We are still looking for the solution for the Error number:
MSSQL_REPL-2147199402.
Any ideas?

Help: Job Failed (Error)

Dear All,
I have a DTS Package. When I run the package manually, it works, but
when it is executed by scheduled job, it always fail.
The error message is :
"Executed as user: <DOMAIN>\<Username>. The step did not generate any
output. Process Exit Code -1073741819. The step failed."
Pls help me to solve it out.
Thanks
Robert LieSee if this helps you understand what's happening:
http://support.microsoft.com/default.aspx?scid=kb;en-us;269074&sd=tech
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:easHEE4kFHA.2472@.TK2MSFTNGP15.phx.gbl...
Dear All,
I have a DTS Package. When I run the package manually, it works, but
when it is executed by scheduled job, it always fail.
The error message is :
"Executed as user: <DOMAIN>\<Username>. The step did not generate any
output. Process Exit Code -1073741819. The step failed."
Pls help me to solve it out.
Thanks
Robert Lie

HELP: Failed to create the task. (Microsoft Visual Studio)

I created my first SSIS project in BI Dev Studio but get the following error when trying to add a data flow task to the Control container:

==================================

Failed to create the task. (Microsoft Visual Studio)

===================================

Value does not fall within the expected range. (Microsoft.SqlServer.ManagedDTS)

Program Location:

at Microsoft.SqlServer.Dts.Runtime.Executables.Add(String moniker)
at Microsoft.DataTransformationServices.Design.DtsBasePackageDesigner.CreateExecutable(String moniker, IDTSSequence container, String name)

Any advice greatly appreciated..

cheers,
jordan

What build are you on? June CTP by chance?|||I just installed the June CPT and I am gettting this same error. Any ideas?

Thanks in advance.|||

Here's the entire error message:

===================================

Value does not fall within the expected range. (Microsoft.SqlServer.ManagedDTS)

Program Location:

at Microsoft.SqlServer.Dts.Runtime.Executables.Add(String moniker)
at Microsoft.DataTransformationServices.Design.DtsBasePackageDesigner.CreateExecutable(String moniker, IDTSSequence container, String name)

|||Yes it is June CTP Developer Edition.|||I also couldn't use the SQL Server Import and Export Wizard. The error that I get:

The SSIS data flow task could not be created. Verify that DTSPipeline.dll is available and registered. The wizard cannot continue and it will terminate.

Value does not fall within the expected range. (Microsoft.SQLServer.DTSRuntimeWrap)|||Hmmm, very odd. It sounds as though you have a corrupted installation. Is this the first time you've installed SQL Server on that machine, IOW is it a clean install? You might try to regsvr32 DTSPipeline.dll. Then try again. It appears that it's just not registered.|||

I have tried uninstalling and reinstalling the CPT 4 times. The last time I did a regclean, deleted left over directories and anything else I could thing of the make the install clean.

One thing I should mention is that I had the VSS.Net 2005 Beta 2 on my machine before I installed the SQL Server 2005 CPT and I had to remove it in order to go forward with the SQL install. Not sure if that left something’s behind. I did use the SQL removal tools to get things off my machine the last couple of times, but not the first. The first time I used the Add/Remove Programs applet, and those uninstalls failed, but the option to remove through the applet disappeared afterward.

Very frustrating. I have installed this on another machine without the problems; it's just that that machine is not my main workstation (and not portable).

I will try the regsvr32 suggestion and regasm on some of the other libraries if that doesn't help.

Thanks!

|||Tried that, no luck.

Any other suggestions?

Thanks!|||I did a search on my local hard drives and couldn't even find DTSPipeline.dll. The CTP version that we have were downloaded from MSDN subscribers download web site.

cheers,
j.|||Has there been any resolve to this error at all? I am close to giving up on the CTP entirely.

Any help would be greatly appreciated.|||Where are you getting the install from? What SKU are you installing? The DtsPipeline.dll should be installed on all SKUs. Are you installing Integration Services? Is there a Microsoft SQL Server\90\DTS folder on your machine? What's in there?|||yeah there is indeed a C:\Program Files\Microsoft SQL Server\90\DTS\Binn directory with DTSPipeline.dll in there. But still re-registering the DLL did not help.|||What control container are you trying to add the dataflow task to?|||Control Flow. But as I mentioned in my earlier post I couldn't even get Import/Export wizard to work within Management Studio.

HELP: FAILED ASSERTION

Hello,
I have a concern about 2 errors "Failed Assertion". We're using SQL Server
2005 SP2. May anyone help me to fix these errors?
It says:
SQL Server Assertion: File: <"xact.cpp">, line = 2788 Failed Assertion = '!m_updNestedXactCnt' Trying to use the transaction while there are 1
parallel nested xacts outstanding. This error may be timing-related. If the
error persists after rerunning the statement, use DBCC CHECKDB to check the
database for structural integrity, or restart the server to ensure in-memory
data structures are not corrupted.
SQL Server Assertion: File: <lckmgr.cpp>, line=9421 Failed Assertion = 'NULL
== m_lockList.Head ()'. This error may be timing-related. If the error
persists after rerunning the statement, use DBCC CHECKDB to check the
database for structural integrity, or restart the server to ensure in-memory
data structures are not corrupted.I would run a checkdb but this is almost always a bug in SQL Server. You
ought to open a case with PSS.
--
Jason Massie
www: http://statisticsio.com
rss: http://feeds.feedburner.com/statisticsio
"Maxim E" <Maxim E@.discussions.microsoft.com> wrote in message
news:2AE68634-7472-4A4C-96D0-B9CCE260A2BE@.microsoft.com...
> Hello,
> I have a concern about 2 errors "Failed Assertion". We're using SQL Server
> 2005 SP2. May anyone help me to fix these errors?
> It says:
> SQL Server Assertion: File: <"xact.cpp">, line = 2788 Failed Assertion => '!m_updNestedXactCnt' Trying to use the transaction while there are 1
> parallel nested xacts outstanding. This error may be timing-related. If
> the
> error persists after rerunning the statement, use DBCC CHECKDB to check
> the
> database for structural integrity, or restart the server to ensure
> in-memory
> data structures are not corrupted.
> SQL Server Assertion: File: <lckmgr.cpp>, line=9421 Failed Assertion => 'NULL
> == m_lockList.Head ()'. This error may be timing-related. If the error
> persists after rerunning the statement, use DBCC CHECKDB to check the
> database for structural integrity, or restart the server to ensure
> in-memory
> data structures are not corrupted.
>|||So I have to report these case to PSS. Ok, thanks for the advice.
"jason" wrote:
> I would run a checkdb but this is almost always a bug in SQL Server. You
> ought to open a case with PSS.
> --
> Jason Massie
> www: http://statisticsio.com
> rss: http://feeds.feedburner.com/statisticsio
> "Maxim E" <Maxim E@.discussions.microsoft.com> wrote in message
> news:2AE68634-7472-4A4C-96D0-B9CCE260A2BE@.microsoft.com...
> > Hello,
> >
> > I have a concern about 2 errors "Failed Assertion". We're using SQL Server
> > 2005 SP2. May anyone help me to fix these errors?
> >
> > It says:
> >
> > SQL Server Assertion: File: <"xact.cpp">, line = 2788 Failed Assertion => > '!m_updNestedXactCnt' Trying to use the transaction while there are 1
> > parallel nested xacts outstanding. This error may be timing-related. If
> > the
> > error persists after rerunning the statement, use DBCC CHECKDB to check
> > the
> > database for structural integrity, or restart the server to ensure
> > in-memory
> > data structures are not corrupted.
> >
> > SQL Server Assertion: File: <lckmgr.cpp>, line=9421 Failed Assertion => > 'NULL
> > == m_lockList.Head ()'. This error may be timing-related. If the error
> > persists after rerunning the statement, use DBCC CHECKDB to check the
> > database for structural integrity, or restart the server to ensure
> > in-memory
> > data structures are not corrupted.
> >
>|||We experience the same problem. How can we solve it ?
"Maxim" wrote:
> So I have to report these case to PSS. Ok, thanks for the advice.
> "jason" wrote:
> > I would run a checkdb but this is almost always a bug in SQL Server. You
> > ought to open a case with PSS.
> >
> > --
> > Jason Massie
> > www: http://statisticsio.com
> > rss: http://feeds.feedburner.com/statisticsio
> >
> > "Maxim E" <Maxim E@.discussions.microsoft.com> wrote in message
> > news:2AE68634-7472-4A4C-96D0-B9CCE260A2BE@.microsoft.com...
> > > Hello,
> > >
> > > I have a concern about 2 errors "Failed Assertion". We're using SQL Server
> > > 2005 SP2. May anyone help me to fix these errors?
> > >
> > > It says:
> > >
> > > SQL Server Assertion: File: <"xact.cpp">, line = 2788 Failed Assertion => > > '!m_updNestedXactCnt' Trying to use the transaction while there are 1
> > > parallel nested xacts outstanding. This error may be timing-related. If
> > > the
> > > error persists after rerunning the statement, use DBCC CHECKDB to check
> > > the
> > > database for structural integrity, or restart the server to ensure
> > > in-memory
> > > data structures are not corrupted.
> > >
> > > SQL Server Assertion: File: <lckmgr.cpp>, line=9421 Failed Assertion => > > 'NULL
> > > == m_lockList.Head ()'. This error may be timing-related. If the error
> > > persists after rerunning the statement, use DBCC CHECKDB to check the
> > > database for structural integrity, or restart the server to ensure
> > > in-memory
> > > data structures are not corrupted.
> > >
> >

HELP: FAILED ASSERTION

Hello,
I have a concern about 2 errors "Failed Assertion". We're using SQL Server
2005 SP2. May anyone help me to fix these errors?
It says:
SQL Server Assertion: File: <"xact.cpp">, line = 2788 Failed Assertion =
'!m_updNestedXactCnt' Trying to use the transaction while there are 1
parallel nested xacts outstanding. This error may be timing-related. If the
error persists after rerunning the statement, use DBCC CHECKDB to check the
database for structural integrity, or restart the server to ensure in-memory
data structures are not corrupted.
SQL Server Assertion: File: <lckmgr.cpp>, line=9421 Failed Assertion = 'NULL
== m_lockList.Head ()'. This error may be timing-related. If the error
persists after rerunning the statement, use DBCC CHECKDB to check the
database for structural integrity, or restart the server to ensure in-memory
data structures are not corrupted.
I would run a checkdb but this is almost always a bug in SQL Server. You
ought to open a case with PSS.
Jason Massie
www: http://statisticsio.com
rss: http://feeds.feedburner.com/statisticsio
"Maxim E" <Maxim E@.discussions.microsoft.com> wrote in message
news:2AE68634-7472-4A4C-96D0-B9CCE260A2BE@.microsoft.com...
> Hello,
> I have a concern about 2 errors "Failed Assertion". We're using SQL Server
> 2005 SP2. May anyone help me to fix these errors?
> It says:
> SQL Server Assertion: File: <"xact.cpp">, line = 2788 Failed Assertion =
> '!m_updNestedXactCnt' Trying to use the transaction while there are 1
> parallel nested xacts outstanding. This error may be timing-related. If
> the
> error persists after rerunning the statement, use DBCC CHECKDB to check
> the
> database for structural integrity, or restart the server to ensure
> in-memory
> data structures are not corrupted.
> SQL Server Assertion: File: <lckmgr.cpp>, line=9421 Failed Assertion =
> 'NULL
> == m_lockList.Head ()'. This error may be timing-related. If the error
> persists after rerunning the statement, use DBCC CHECKDB to check the
> database for structural integrity, or restart the server to ensure
> in-memory
> data structures are not corrupted.
>
|||So I have to report these case to PSS. Ok, thanks for the advice.
"jason" wrote:

> I would run a checkdb but this is almost always a bug in SQL Server. You
> ought to open a case with PSS.
> --
> Jason Massie
> www: http://statisticsio.com
> rss: http://feeds.feedburner.com/statisticsio
> "Maxim E" <Maxim E@.discussions.microsoft.com> wrote in message
> news:2AE68634-7472-4A4C-96D0-B9CCE260A2BE@.microsoft.com...
>

Help: Error Log

Dear all,
After I checked the SQL Server Log i found error like this:
1. Error: 17883, Severity: 1, State: 0
What does it mean?
2. Login failed for user 'sa'.
Almost every minute this error occured.
Does someone know what's happening to my SQL Server?
Thanks
Robert Lie
Robert,
1. This message means your scheduler appears to be hung. See the following
for more info:
New concurrency and scheduling diagnostics added to SQL Server
http://support.microsoft.com/kb/319892/
2. This means something is trying to login to SQL Server (and failing). Run
SQL Profiler to see what this is. Whatever it is, it shouldn't be using the
sa account.
Mark.
"Robert Lie" wrote:

> Dear all,
> After I checked the SQL Server Log i found error like this:
> 1. Error: 17883, Severity: 1, State: 0
> What does it mean?
> 2. Login failed for user 'sa'.
> Almost every minute this error occured.
> Does someone know what's happening to my SQL Server?
> Thanks
> Robert Lie
>

Help: Error Log

Dear all,
After I checked the SQL Server Log i found error like this:
1. Error: 17883, Severity: 1, State: 0
What does it mean?
2. Login failed for user 'sa'.
Almost every minute this error occured.
Does someone know what's happening to my SQL Server?
Thanks
Robert LieRobert,
1. This message means your scheduler appears to be hung. See the following
for more info:
New concurrency and scheduling diagnostics added to SQL Server
http://support.microsoft.com/kb/319892/
2. This means something is trying to login to SQL Server (and failing). Run
SQL Profiler to see what this is. Whatever it is, it shouldn't be using the
sa account.
Mark.
"Robert Lie" wrote:

> Dear all,
> After I checked the SQL Server Log i found error like this:
> 1. Error: 17883, Severity: 1, State: 0
> What does it mean?
> 2. Login failed for user 'sa'.
> Almost every minute this error occured.
> Does someone know what's happening to my SQL Server?
> Thanks
> Robert Lie
>

Help: Error Log

Dear all,
After I checked the SQL Server Log i found error like this:
1. Error: 17883, Severity: 1, State: 0
What does it mean?
2. Login failed for user 'sa'.
Almost every minute this error occured.
Does someone know what's happening to my SQL Server?
Thanks
Robert LieRobert,
1. This message means your scheduler appears to be hung. See the following
for more info:
New concurrency and scheduling diagnostics added to SQL Server
http://support.microsoft.com/kb/319892/
2. This means something is trying to login to SQL Server (and failing). Run
SQL Profiler to see what this is. Whatever it is, it shouldn't be using the
sa account.
Mark.
"Robert Lie" wrote:
> Dear all,
> After I checked the SQL Server Log i found error like this:
> 1. Error: 17883, Severity: 1, State: 0
> What does it mean?
> 2. Login failed for user 'sa'.
> Almost every minute this error occured.
> Does someone know what's happening to my SQL Server?
> Thanks
> Robert Lie
>