I have a table report where amoung other things there is a list of names
from another data set. I don't want the names to print in one column because
the list maybe more than one page. I can create a multi column report for
just the names and when printed or print preview will display in multiply
columns (good). But when I add that report as a subreport to my main report
I believe it ignores the subreport's 'report properties' and uses the main
'report's properties'?
Any suggestions?
JohnI found this in 2005 Books online, I would guess that 2000 is the same.
Apparently the column setting is inherited from the parent report.
Denny
SQL Server 2005 Books Online
Writing Multi-Column Reports
Updated: 5 December 2005
You can design a report that uses a multi-column layout, similar to a
traditional newspaper column where data flows down multiple adjacent
columns. A multi-column layout applies to the entire report. It is not
possible to specify a multi-column layout on the top half of the report, and
a tabular layout on the bottom half of the report. When you specify a
multi-column layout, the report server creates each column as a series of
very narrow pages that are rendered in close sequence, giving the appearance
of multiple columns. Properties that you set at the page level are applied
to each column in the report. You can define as many columns you want.
For best results, use data regions that provide repeating rows of data (for
example, table or list box). A list box placed within a multi-column report
will display data from the top left of the page to the bottom left of the
page, and then continue the list in the adjacent column at the top of the
page. If you want to use text boxes or images, put them in a list so that
they repeat in each column.
If you are accustomed to using subreports to embed a separate report within
a parent report, be aware that you cannot use subreports to get the same
outcome in a multi-column layout. In a multi-column report, a subreport
inherits the column settings of the parent report. This means that if you
define a multi-column layout on a subreport, the subreport ignores the
column settings that are specified for it. It also means that you cannot use
subreports to create a free-form or single column layout within the
multi-column report. Subreports that you include in a multi-column report
always use the column settings of the parent report
"johnsh" <johnsh@.axiumae.com> wrote in message
news:%23%23usVHbhGHA.4368@.TK2MSFTNGP03.phx.gbl...
>I have a table report where amoung other things there is a list of names
>from another data set. I don't want the names to print in one column
>because the list maybe more than one page. I can create a multi column
>report for just the names and when printed or print preview will display in
>multiply columns (good). But when I add that report as a subreport to my
>main report I believe it ignores the subreport's 'report properties' and
>uses the main 'report's properties'?
> Any suggestions?
> John
>
Showing posts with label print. Show all posts
Showing posts with label print. Show all posts
Monday, March 26, 2012
Wednesday, March 21, 2012
MSSRS 2000 Restarts Windows XP system after the latest update
Hi Microsoft Sql server reproting services restarts the windows xp installed
desktops when we try to print using the print oprion in the report.
This is happening for lot of my clients.
How to fix this. This is happening only after the latest update in March.
My company has aroung 40,000 people who will be using the reports generated
by the reporting services most of them have windows xp with autometic update
switched on. Hence once the update happnes when they want to take a print out
of a report which shown using the MSSRS 2000 in internet explorere and
clicked onthe print icon in the report window system gets restarted.
Please help
Thanking you
SureshSuresh,
The first time you click the print icon a ActiveX control is installed. You
must have some sort of common desktop configuration that is blowing up when
you try to install this ActiveX.
First thing I would do is look at IE's security settings surrounding the
ActiveX downloading/installing.
--
Andy Potter
blog : http://sqlreportingservices.spaces.live.com
info@.(NOSPAM)lakeclaireenterprises.com
"Suresh" <Suresh@.discussions.microsoft.com> wrote in message
news:099AD7C4-D9BF-420A-A082-C0BB1438A79C@.microsoft.com...
> Hi Microsoft Sql server reproting services restarts the windows xp
> installed
> desktops when we try to print using the print oprion in the report.
> This is happening for lot of my clients.
> How to fix this. This is happening only after the latest update in March.
> My company has aroung 40,000 people who will be using the reports
> generated
> by the reporting services most of them have windows xp with autometic
> update
> switched on. Hence once the update happnes when they want to take a print
> out
> of a report which shown using the MSSRS 2000 in internet explorere and
> clicked onthe print icon in the report window system gets restarted.
> Please help
> Thanking you
> Suresh
>|||Thanks Andy.
But the issue is not with installing the active x.
In many systems the active x was installed long before.
It was working fine until recently a windws xp update was released.
After the update only when clicked on the print icon in the report displayed
in desktops the systems get restarted.
So this should be a bug introduced due to the recent update by Microsft
update for windows Xp. I am looking for a patch for this.
Regards
Suresh
"Andy Potter" wrote:
> Suresh,
> The first time you click the print icon a ActiveX control is installed. You
> must have some sort of common desktop configuration that is blowing up when
> you try to install this ActiveX.
> First thing I would do is look at IE's security settings surrounding the
> ActiveX downloading/installing.
> --
> Andy Potter
> blog : http://sqlreportingservices.spaces.live.com
> info@.(NOSPAM)lakeclaireenterprises.com
> "Suresh" <Suresh@.discussions.microsoft.com> wrote in message
> news:099AD7C4-D9BF-420A-A082-C0BB1438A79C@.microsoft.com...
> > Hi Microsoft Sql server reproting services restarts the windows xp
> > installed
> > desktops when we try to print using the print oprion in the report.
> >
> > This is happening for lot of my clients.
> > How to fix this. This is happening only after the latest update in March.
> >
> > My company has aroung 40,000 people who will be using the reports
> > generated
> > by the reporting services most of them have windows xp with autometic
> > update
> > switched on. Hence once the update happnes when they want to take a print
> > out
> > of a report which shown using the MSSRS 2000 in internet explorere and
> > clicked onthe print icon in the report window system gets restarted.
> >
> > Please help
> > Thanking you
> > Suresh
> >
> >
>
>|||Suresh,
We are facing the same problem..
I was searching around when i got something on this issue in the below
URL.
Not sure to what extent it will identify and solve this problem, but
may be worth a read.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1480005&SiteID=1
Please let us know if any body gets some solution to this
On Apr 17, 4:08 pm, Suresh <Sur...@.discussions.microsoft.com> wrote:
> Thanks Andy.
> But the issue is not with installing the active x.
> In many systems the active x was installed long before.
> It was working fine until recently a windws xp update was released.
> After the update only when clicked on theprinticon in the report displayed
> in desktops the systems get restarted.
> So this should be a bug introduced due to the recent update by Microsft
> update for windows Xp. I am looking for a patch for this.
> Regards
> Suresh
>
> "Andy Potter" wrote:
> > Suresh,
> > The first time you click theprinticon a ActiveX control is installed. You
> > must have some sort of common desktop configuration that is blowing up when
> > you try to install this ActiveX.
> > First thing I would do is look at IE's security settings surrounding the
> > ActiveX downloading/installing.
> > --
> > Andy Potter
> > blog :http://sqlreportingservices.spaces.live.com
> > info@.(NOSPAM)lakeclaireenterprises.com
> > "Suresh" <Sur...@.discussions.microsoft.com> wrote in message
> >news:099AD7C4-D9BF-420A-A082-C0BB1438A79C@.microsoft.com...
> > > Hi Microsoft Sql server reproting services restarts the windows xp
> > > installed
> > > desktops when we try toprintusing theprintoprion in the report.
> > > This is happening for lot of my clients.
> > > How to fix this. This is happening only after the latest update in March.
> > > My company has aroung 40,000 people who will be using the reports
> > > generated
> > > by thereporting servicesmost of them have windows xp with autometic
> > > update
> > > switched on. Hence once the update happnes when they want to take aprint
> > > out
> > > of a report which shown using the MSSRS 2000 in internet explorere and
> > > clicked ontheprinticon in the report windowsystemgets restarted.
> > > Please help
> > > Thanking you
> > > Suresh- Hide quoted text -
> - Show quoted text -|||Hi Shocky,
It is really great. the link you have given actually solved my problem.
Thanks a lot for the help. This was the need of the hour for me.
Once again
Thanking you
Suresh
"Shocky" wrote:
> Suresh,
> We are facing the same problem..
> I was searching around when i got something on this issue in the below
> URL.
> Not sure to what extent it will identify and solve this problem, but
> may be worth a read.
> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1480005&SiteID=1
>
> Please let us know if any body gets some solution to this
>
> On Apr 17, 4:08 pm, Suresh <Sur...@.discussions.microsoft.com> wrote:
> > Thanks Andy.
> >
> > But the issue is not with installing the active x.
> >
> > In many systems the active x was installed long before.
> > It was working fine until recently a windws xp update was released.
> > After the update only when clicked on theprinticon in the report displayed
> > in desktops the systems get restarted.
> >
> > So this should be a bug introduced due to the recent update by Microsft
> > update for windows Xp. I am looking for a patch for this.
> >
> > Regards
> > Suresh
> >
> >
> >
> > "Andy Potter" wrote:
> > > Suresh,
> >
> > > The first time you click theprinticon a ActiveX control is installed. You
> > > must have some sort of common desktop configuration that is blowing up when
> > > you try to install this ActiveX.
> >
> > > First thing I would do is look at IE's security settings surrounding the
> > > ActiveX downloading/installing.
> >
> > > --
> > > Andy Potter
> > > blog :http://sqlreportingservices.spaces.live.com
> > > info@.(NOSPAM)lakeclaireenterprises.com
> > > "Suresh" <Sur...@.discussions.microsoft.com> wrote in message
> > >news:099AD7C4-D9BF-420A-A082-C0BB1438A79C@.microsoft.com...
> > > > Hi Microsoft Sql server reproting services restarts the windows xp
> > > > installed
> > > > desktops when we try toprintusing theprintoprion in the report.
> >
> > > > This is happening for lot of my clients.
> > > > How to fix this. This is happening only after the latest update in March.
> >
> > > > My company has aroung 40,000 people who will be using the reports
> > > > generated
> > > > by thereporting servicesmost of them have windows xp with autometic
> > > > update
> > > > switched on. Hence once the update happnes when they want to take aprint
> > > > out
> > > > of a report which shown using the MSSRS 2000 in internet explorere and
> > > > clicked ontheprinticon in the report windowsystemgets restarted.
> >
> > > > Please help
> > > > Thanking you
> > > > Suresh- Hide quoted text -
> >
> > - Show quoted text -
>
>sql
desktops when we try to print using the print oprion in the report.
This is happening for lot of my clients.
How to fix this. This is happening only after the latest update in March.
My company has aroung 40,000 people who will be using the reports generated
by the reporting services most of them have windows xp with autometic update
switched on. Hence once the update happnes when they want to take a print out
of a report which shown using the MSSRS 2000 in internet explorere and
clicked onthe print icon in the report window system gets restarted.
Please help
Thanking you
SureshSuresh,
The first time you click the print icon a ActiveX control is installed. You
must have some sort of common desktop configuration that is blowing up when
you try to install this ActiveX.
First thing I would do is look at IE's security settings surrounding the
ActiveX downloading/installing.
--
Andy Potter
blog : http://sqlreportingservices.spaces.live.com
info@.(NOSPAM)lakeclaireenterprises.com
"Suresh" <Suresh@.discussions.microsoft.com> wrote in message
news:099AD7C4-D9BF-420A-A082-C0BB1438A79C@.microsoft.com...
> Hi Microsoft Sql server reproting services restarts the windows xp
> installed
> desktops when we try to print using the print oprion in the report.
> This is happening for lot of my clients.
> How to fix this. This is happening only after the latest update in March.
> My company has aroung 40,000 people who will be using the reports
> generated
> by the reporting services most of them have windows xp with autometic
> update
> switched on. Hence once the update happnes when they want to take a print
> out
> of a report which shown using the MSSRS 2000 in internet explorere and
> clicked onthe print icon in the report window system gets restarted.
> Please help
> Thanking you
> Suresh
>|||Thanks Andy.
But the issue is not with installing the active x.
In many systems the active x was installed long before.
It was working fine until recently a windws xp update was released.
After the update only when clicked on the print icon in the report displayed
in desktops the systems get restarted.
So this should be a bug introduced due to the recent update by Microsft
update for windows Xp. I am looking for a patch for this.
Regards
Suresh
"Andy Potter" wrote:
> Suresh,
> The first time you click the print icon a ActiveX control is installed. You
> must have some sort of common desktop configuration that is blowing up when
> you try to install this ActiveX.
> First thing I would do is look at IE's security settings surrounding the
> ActiveX downloading/installing.
> --
> Andy Potter
> blog : http://sqlreportingservices.spaces.live.com
> info@.(NOSPAM)lakeclaireenterprises.com
> "Suresh" <Suresh@.discussions.microsoft.com> wrote in message
> news:099AD7C4-D9BF-420A-A082-C0BB1438A79C@.microsoft.com...
> > Hi Microsoft Sql server reproting services restarts the windows xp
> > installed
> > desktops when we try to print using the print oprion in the report.
> >
> > This is happening for lot of my clients.
> > How to fix this. This is happening only after the latest update in March.
> >
> > My company has aroung 40,000 people who will be using the reports
> > generated
> > by the reporting services most of them have windows xp with autometic
> > update
> > switched on. Hence once the update happnes when they want to take a print
> > out
> > of a report which shown using the MSSRS 2000 in internet explorere and
> > clicked onthe print icon in the report window system gets restarted.
> >
> > Please help
> > Thanking you
> > Suresh
> >
> >
>
>|||Suresh,
We are facing the same problem..
I was searching around when i got something on this issue in the below
URL.
Not sure to what extent it will identify and solve this problem, but
may be worth a read.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1480005&SiteID=1
Please let us know if any body gets some solution to this
On Apr 17, 4:08 pm, Suresh <Sur...@.discussions.microsoft.com> wrote:
> Thanks Andy.
> But the issue is not with installing the active x.
> In many systems the active x was installed long before.
> It was working fine until recently a windws xp update was released.
> After the update only when clicked on theprinticon in the report displayed
> in desktops the systems get restarted.
> So this should be a bug introduced due to the recent update by Microsft
> update for windows Xp. I am looking for a patch for this.
> Regards
> Suresh
>
> "Andy Potter" wrote:
> > Suresh,
> > The first time you click theprinticon a ActiveX control is installed. You
> > must have some sort of common desktop configuration that is blowing up when
> > you try to install this ActiveX.
> > First thing I would do is look at IE's security settings surrounding the
> > ActiveX downloading/installing.
> > --
> > Andy Potter
> > blog :http://sqlreportingservices.spaces.live.com
> > info@.(NOSPAM)lakeclaireenterprises.com
> > "Suresh" <Sur...@.discussions.microsoft.com> wrote in message
> >news:099AD7C4-D9BF-420A-A082-C0BB1438A79C@.microsoft.com...
> > > Hi Microsoft Sql server reproting services restarts the windows xp
> > > installed
> > > desktops when we try toprintusing theprintoprion in the report.
> > > This is happening for lot of my clients.
> > > How to fix this. This is happening only after the latest update in March.
> > > My company has aroung 40,000 people who will be using the reports
> > > generated
> > > by thereporting servicesmost of them have windows xp with autometic
> > > update
> > > switched on. Hence once the update happnes when they want to take aprint
> > > out
> > > of a report which shown using the MSSRS 2000 in internet explorere and
> > > clicked ontheprinticon in the report windowsystemgets restarted.
> > > Please help
> > > Thanking you
> > > Suresh- Hide quoted text -
> - Show quoted text -|||Hi Shocky,
It is really great. the link you have given actually solved my problem.
Thanks a lot for the help. This was the need of the hour for me.
Once again
Thanking you
Suresh
"Shocky" wrote:
> Suresh,
> We are facing the same problem..
> I was searching around when i got something on this issue in the below
> URL.
> Not sure to what extent it will identify and solve this problem, but
> may be worth a read.
> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1480005&SiteID=1
>
> Please let us know if any body gets some solution to this
>
> On Apr 17, 4:08 pm, Suresh <Sur...@.discussions.microsoft.com> wrote:
> > Thanks Andy.
> >
> > But the issue is not with installing the active x.
> >
> > In many systems the active x was installed long before.
> > It was working fine until recently a windws xp update was released.
> > After the update only when clicked on theprinticon in the report displayed
> > in desktops the systems get restarted.
> >
> > So this should be a bug introduced due to the recent update by Microsft
> > update for windows Xp. I am looking for a patch for this.
> >
> > Regards
> > Suresh
> >
> >
> >
> > "Andy Potter" wrote:
> > > Suresh,
> >
> > > The first time you click theprinticon a ActiveX control is installed. You
> > > must have some sort of common desktop configuration that is blowing up when
> > > you try to install this ActiveX.
> >
> > > First thing I would do is look at IE's security settings surrounding the
> > > ActiveX downloading/installing.
> >
> > > --
> > > Andy Potter
> > > blog :http://sqlreportingservices.spaces.live.com
> > > info@.(NOSPAM)lakeclaireenterprises.com
> > > "Suresh" <Sur...@.discussions.microsoft.com> wrote in message
> > >news:099AD7C4-D9BF-420A-A082-C0BB1438A79C@.microsoft.com...
> > > > Hi Microsoft Sql server reproting services restarts the windows xp
> > > > installed
> > > > desktops when we try toprintusing theprintoprion in the report.
> >
> > > > This is happening for lot of my clients.
> > > > How to fix this. This is happening only after the latest update in March.
> >
> > > > My company has aroung 40,000 people who will be using the reports
> > > > generated
> > > > by thereporting servicesmost of them have windows xp with autometic
> > > > update
> > > > switched on. Hence once the update happnes when they want to take aprint
> > > > out
> > > > of a report which shown using the MSSRS 2000 in internet explorere and
> > > > clicked ontheprinticon in the report windowsystemgets restarted.
> >
> > > > Please help
> > > > Thanking you
> > > > Suresh- Hide quoted text -
> >
> > - Show quoted text -
>
>sql
Monday, March 19, 2012
MSSQLSERVER service terminated unexpectedly
HI
I have server MSDE 2000 SP3
frequently server stopped, and print in log file information:
1)
17310 :
SqlDumpExceptionHandler: Process 1984 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
2)
17311 :
SQL Server is aborting. Fatal exception c0000005 caught.
3)
The MSSQLSERVER service terminated unexpectedly.
If you didn't find anything in KB on this and you are on the current service pack: Open a case with MS
Support. Exceptions etc are most often bugs in SQL Server, so you will probably need a fix or workaround from
MS for this.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Bies" <ANTYSPAMbies22@.poczta.onet.pl> wrote in message news:ca1ij7$dd6$1@.atlantis.news.tpi.pl...
> HI
> I have server MSDE 2000 SP3
> frequently server stopped, and print in log file information:
> 1)
> 17310 :
> SqlDumpExceptionHandler: Process 1984 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> 2)
> 17311 :
> SQL Server is aborting. Fatal exception c0000005 caught.
> 3)
> The MSSQLSERVER service terminated unexpectedly.
>
I have server MSDE 2000 SP3
frequently server stopped, and print in log file information:
1)
17310 :
SqlDumpExceptionHandler: Process 1984 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
2)
17311 :
SQL Server is aborting. Fatal exception c0000005 caught.
3)
The MSSQLSERVER service terminated unexpectedly.
If you didn't find anything in KB on this and you are on the current service pack: Open a case with MS
Support. Exceptions etc are most often bugs in SQL Server, so you will probably need a fix or workaround from
MS for this.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Bies" <ANTYSPAMbies22@.poczta.onet.pl> wrote in message news:ca1ij7$dd6$1@.atlantis.news.tpi.pl...
> HI
> I have server MSDE 2000 SP3
> frequently server stopped, and print in log file information:
> 1)
> 17310 :
> SqlDumpExceptionHandler: Process 1984 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> 2)
> 17311 :
> SQL Server is aborting. Fatal exception c0000005 caught.
> 3)
> The MSSQLSERVER service terminated unexpectedly.
>
MSSQLSERVER service terminated unexpectedly
HI
I have server MSDE 2000 SP3
frequently server stopped, and print in log file information:
I have server MSDE 2000 SP3
frequently server stopped, and print in log file information:
1)
17310 :
SqlDumpExceptionHandler: Process 1984 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
2)
17311 :
SQL Server is aborting. Fatal exception c0000005 caught.
3)
The MSSQLSERVER service terminated unexpectedly.Hi
This may be as in:
http://support.microsoft.com/defaul...kb;en-us;814572
other possibilities
http://search.microsoft.com/search/...ql+server&na=54
You may also want to check if a anti-virus software is affecting it.
John
"Bies" <ANTYSPAMbies22@.poczta.onet.pl> wrote in message
news:ca1ie6$6gh$1@.nemesis.news.tpi.pl...
> HI
> I have server MSDE 2000 SP3
> frequently server stopped, and print in log file information:
> 1)
> 17310 :
> SqlDumpExceptionHandler: Process 1984 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> 2)
> 17311 :
> SQL Server is aborting. Fatal exception c0000005 caught.
> 3)
> The MSSQLSERVER service terminated unexpectedly.|||> This may be as in:
> http://support.microsoft.com/defaul...kb;en-us;814572
> other possibilities
http://search.microsoft.com/search/...ql+server&na=54
> You may also want to check if a anti-virus software is affecting it.
thx
MSSQLSERVER service terminated unexpectedly
HI
I have server MSDE 2000 SP3
frequently server stopped, and print in log file information:
1)
17310 :
SqlDumpExceptionHandler: Process 1984 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
2)
17311 :
SQL Server is aborting. Fatal exception c0000005 caught.
3)
The MSSQLSERVER service terminated unexpectedly.If you didn't find anything in KB on this and you are on the current service
pack: Open a case with MS
Support. Exceptions etc are most often bugs in SQL Server, so you will proba
bly need a fix or workaround from
MS for this.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Bies" <ANTYSPAMbies22@.poczta.onet.pl> wrote in message news:ca1ij7$dd6$1@.atlantis.news.tpi.
pl...
> HI
> I have server MSDE 2000 SP3
> frequently server stopped, and print in log file information:
> 1)
> 17310 :
> SqlDumpExceptionHandler: Process 1984 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> 2)
> 17311 :
> SQL Server is aborting. Fatal exception c0000005 caught.
> 3)
> The MSSQLSERVER service terminated unexpectedly.
>
I have server MSDE 2000 SP3
frequently server stopped, and print in log file information:
1)
17310 :
SqlDumpExceptionHandler: Process 1984 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
2)
17311 :
SQL Server is aborting. Fatal exception c0000005 caught.
3)
The MSSQLSERVER service terminated unexpectedly.If you didn't find anything in KB on this and you are on the current service
pack: Open a case with MS
Support. Exceptions etc are most often bugs in SQL Server, so you will proba
bly need a fix or workaround from
MS for this.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Bies" <ANTYSPAMbies22@.poczta.onet.pl> wrote in message news:ca1ij7$dd6$1@.atlantis.news.tpi.
pl...
> HI
> I have server MSDE 2000 SP3
> frequently server stopped, and print in log file information:
> 1)
> 17310 :
> SqlDumpExceptionHandler: Process 1984 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> 2)
> 17311 :
> SQL Server is aborting. Fatal exception c0000005 caught.
> 3)
> The MSSQLSERVER service terminated unexpectedly.
>
MSSQLSERVER service terminated unexpectedly
HI
I have server MSDE 2000 SP3
frequently server stopped, and print in log file information:
1)
17310 :
SqlDumpExceptionHandler: Process 1984 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
2)
17311 :
SQL Server is aborting. Fatal exception c0000005 caught.
3)
The MSSQLSERVER service terminated unexpectedly.If you didn't find anything in KB on this and you are on the current service pack: Open a case with MS
Support. Exceptions etc are most often bugs in SQL Server, so you will probably need a fix or workaround from
MS for this.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Bies" <ANTYSPAMbies22@.poczta.onet.pl> wrote in message news:ca1ij7$dd6$1@.atlantis.news.tpi.pl...
> HI
> I have server MSDE 2000 SP3
> frequently server stopped, and print in log file information:
> 1)
> 17310 :
> SqlDumpExceptionHandler: Process 1984 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> 2)
> 17311 :
> SQL Server is aborting. Fatal exception c0000005 caught.
> 3)
> The MSSQLSERVER service terminated unexpectedly.
>
I have server MSDE 2000 SP3
frequently server stopped, and print in log file information:
1)
17310 :
SqlDumpExceptionHandler: Process 1984 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
2)
17311 :
SQL Server is aborting. Fatal exception c0000005 caught.
3)
The MSSQLSERVER service terminated unexpectedly.If you didn't find anything in KB on this and you are on the current service pack: Open a case with MS
Support. Exceptions etc are most often bugs in SQL Server, so you will probably need a fix or workaround from
MS for this.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Bies" <ANTYSPAMbies22@.poczta.onet.pl> wrote in message news:ca1ij7$dd6$1@.atlantis.news.tpi.pl...
> HI
> I have server MSDE 2000 SP3
> frequently server stopped, and print in log file information:
> 1)
> 17310 :
> SqlDumpExceptionHandler: Process 1984 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> 2)
> 17311 :
> SQL Server is aborting. Fatal exception c0000005 caught.
> 3)
> The MSSQLSERVER service terminated unexpectedly.
>
Subscribe to:
Posts (Atom)