Install Second Instance Of SQL Server 2005

I'm trying to install a second instance of SQL Server 2005 to an existing
server where Service Pack 2 is installed. Nothing special - no clustering, I
just want an additional instance for QA purposes.
The problem that I'm experiencing is that I receive an error message during
the installation:
Error 1603 installing Microsoft SQL Server 2005 Setup Support Files
The log file doesn't provide any description of an error. My only guess at
this point is that my current instance has higher versions of files than the
ones on the original install disk.
Any suggestions on how to proceed? Should I wipe-out the server and start
over?
I would appreciate any assistance. THANKS!!!
Regards,
RayHi Ray,
You could try running sqlrun.msi (in the setup directory) directly,
instead of the setup.exe. That would forego the installation of the
Setup Support Files. Not sure if that works, though.
--
Regards,
Steve
www.foxville.ch
On Sep 13, 7:08 pm, raz0r9edge <raz0r9e...@.discussions.microsoft.com>
wrote:
> I'm trying to install a second instance of SQL Server 2005 to an existing
> server where Service Pack 2 is installed. Nothing special - no clustering, I
> just want an additional instance for QA purposes.
> The problem that I'm experiencing is that I receive an error message during
> the installation:
> Error 1603 installing Microsoft SQL Server 2005 Setup Support Files
> The log file doesn't provide any description of an error. My only guess at
> this point is that my current instance has higher versions of files than the
> ones on the original install disk.
> Any suggestions on how to proceed? Should I wipe-out the server and start
> over?
> I would appreciate any assistance. THANKS!!!
> Regards,
> Ray

install Reporting service problem on SQL 2005 Express advanced Help please

Hi All,
I try to install reporting services with a french version of SQL 2005
Express Advanced on W2003 std SP1
Install of SQL2005 OK
When setup programm reach reporting service installation, i get an error
message( in french) :
"Le programme d'installation de SQL Server n'a pas pu récupérer le nom du
certificat SSL"
in English from my own translation : "SQL server installation program has
not been able to find SSL certificate"
This stop installation
detail of error give :
Linkid 20476
Nom du produit Microsoft sql Server
Version du Produit 9.00.2047.00
Source du mesage setup.rll
ID du message 29561
evtType
sqlca\sqlrsguica.cpp@.CheckRSSetupRequirements@.CheckRSSetupRequirements@.x7379
I try to install anyway reporting services via RSConfigTool
Install seems ok . Reporting services start ok
but http://mydomain/reports/Pages/folder.aspx give : Red cross Error
and message : "The request failed with HTTP status 400: Bad Request."
That we can find in C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting
Services\LogFiles:
----
w3wp!ui!1!17/02/2007-12:02:13:: e ERROR: The request failed with HTTP status
400: Bad Request.
w3wp!ui!1!17/02/2007-12:02:13:: e ERROR: HTTP status code --> 500
--Details--
System.Net.WebException: The request failed with HTTP status 400: Bad
Request.
at
Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods()
at
Microsoft.ReportingServices.UI.Global.RSWebServiceWrapper.GetSecureMethods()
at
Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String
methodname)
at
Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()
at
Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
level)
at Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
sender, EventArgs args)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Web.UI.Control.OnInit(EventArgs e)
at System.Web.UI.Page.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
w3wp!ui!1!17/02/2007-12:02:13:: e ERROR: Exception in ShowErrorPage:
System.Threading.ThreadAbortException: Thread was being aborted.
at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean
preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg) at at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean
preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg)
-----
Any idea '
MERCI beaucoup
Philippe
C.I.A ITI work around by desintalling IIS et re_install.
In fact i had installed a certificate via selfssl prior install reporting
services, as i have no option to remove this cerificate, the only way i
found, was to uninstall IIS
Philippe
"Philippe" <ph.boussaroque@.Espace-NTIC.com> a écrit dans le message de news:
ecmCyToUHHA.1364@.TK2MSFTNGP06.phx.gbl...
> Hi All,
> I try to install reporting services with a french version of SQL 2005
> Express Advanced on W2003 std SP1
> Install of SQL2005 OK
> When setup programm reach reporting service installation, i get an error
> message( in french) :
> "Le programme d'installation de SQL Server n'a pas pu récupérer le nom du
> certificat SSL"
> in English from my own translation : "SQL server installation program has
> not been able to find SSL certificate"
> This stop installation
> detail of error give :
> Linkid 20476
> Nom du produit Microsoft sql Server
> Version du Produit 9.00.2047.00
> Source du mesage setup.rll
> ID du message 29561
> evtType
> sqlca\sqlrsguica.cpp@.CheckRSSetupRequirements@.CheckRSSetupRequirements@.x7379
> I try to install anyway reporting services via RSConfigTool
> Install seems ok . Reporting services start ok
> but http://mydomain/reports/Pages/folder.aspx give : Red cross Error
> and message : "The request failed with HTTP status 400: Bad Request."
> That we can find in C:\Program Files\Microsoft SQL
> Server\MSSQL.2\Reporting Services\LogFiles:
> ----
> w3wp!ui!1!17/02/2007-12:02:13:: e ERROR: The request failed with HTTP
> status 400: Bad Request.
> w3wp!ui!1!17/02/2007-12:02:13:: e ERROR: HTTP status code --> 500
> --Details--
> System.Net.WebException: The request failed with HTTP status 400: Bad
> Request.
> at
> Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods()
> at
> Microsoft.ReportingServices.UI.Global.RSWebServiceWrapper.GetSecureMethods()
> at
> Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String
> methodname)
> at
> Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()
> at
> Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
> level)
> at
> Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
> sender, EventArgs args)
> at System.EventHandler.Invoke(Object sender, EventArgs e)
> at System.Web.UI.Control.OnInit(EventArgs e)
> at System.Web.UI.Page.OnInit(EventArgs e)
> at System.Web.UI.Control.InitRecursive(Control namingContainer)
> at System.Web.UI.Page.ProcessRequestMain(Boolean
> includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
> w3wp!ui!1!17/02/2007-12:02:13:: e ERROR: Exception in ShowErrorPage:
> System.Threading.ThreadAbortException: Thread was being aborted.
> at System.Threading.Thread.AbortInternal()
> at System.Threading.Thread.Abort(Object stateInfo)
> at System.Web.HttpResponse.End()
> at System.Web.HttpServerUtility.Transfer(String path, Boolean
> preserveForm)
> at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> errMsg) at at System.Threading.Thread.AbortInternal()
> at System.Threading.Thread.Abort(Object stateInfo)
> at System.Web.HttpResponse.End()
> at System.Web.HttpServerUtility.Transfer(String path, Boolean
> preserveForm)
> at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> errMsg)
> -----
> Any idea '
> MERCI beaucoup
> Philippe
> C.I.A IT
>
>

install reporting service 2005

Hi
I tried to install reporting service after i had installed sql server 2005, I find reporting service checkbox is disabled, so i can not install it.
Why it is disabled, and how i install reporting service.
thanks

Do you have IIS installed on the machine? If not installed, RS will not install either.

Also, because you have a SQL instance already installed, you have two options.

1. Install RS as another instance and you will get a full install and the check box should be enabled.

2. Install RS as a files only installation for the existing SQL Instance. Then use the configuration tool to configure RS to work with the current instance of SQL Server.

|||Hi Brad
That solved the problem. I installed IIS , and succeded in instaling RS within a named sqlsever 2005 service.
I tried to create a simple report using RS wizard in VS 2005 to test the reporting service , and when finishing the wizard the error message:
"Exception of type 'System.Runtime.InteropServices.COMException' " was thrown , and i can not generate the report.
Pls, how can i resolve the problem.
Thanks.

|||I resolved the exception error thanks to the post: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=573569&SiteID=1&mode=1

after reading the post , I downloaded the refactor software . I tried to install it

, but it could not be installed due to error:

"Error 1001: The SavedState Dictionary contains inconsistent data and

might have corrupted."

I traced the propblem until i found that DXCore (software provided by same

company of refactor) was the reason.

I removed DXcore , and every thing in reporting service in visual studio 2005

become working well !!!..

Is it a bug in DXcore ?

sql

Install Problems

I keep getting this error when trying to install. "SQL Server is terminating due to 'stop' request from Service Control Manager." Any ideas how to fix it?
Check the SQLSTP.log file for additioanl information.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Install Problems

I keep getting this error when trying to install. "SQL Server is terminatin
g due to 'stop' request from Service Control Manager." Any ideas how to fix
it?Check the SQLSTP.log file for additioanl information.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Install Problems

I keep getting this error when trying to install. "SQL Server is terminating due to 'stop' request from Service Control Manager." Any ideas how to fix it?Check the SQLSTP.log file for additioanl information.
Rand
This posting is provided "as is" with no warranties and confers no rights.

install Office ifilter on SQL Server 2005

Hi there
I might be being dense, but I can't seem to get the Full Text Search
service working for office type documents. The service works OK for
text and RTF files, so I know that the Full Text indexing service is
there, but just doesn't seem to be working for Office docs -
specifially Word .doc files.
Digging a little deeper, it seems that the relevant ifilter isn't
installed. When I run
select * from sys.fulltext_document_types
I get the list of document types that can be indexed and searched by
SQL server 2005. For .the .rtf entry, I get a path of
c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\msfte.dll
for the ifilter, version 12.0.6214.0 which is where I would expect it
to be (ie I can see the msfte.dll file in the Binn directory).
For the .doc entry, I get a path of
c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\offfilt.dll
for the ifilter, but no version number, and when I look at the Binn
directory, the file is not there.
Is there any way I can install the office ifilter on SQL server 2005?
Note that this is a database server so does not have IIS, Sharepoint,
Desktop search or any other search mechanism installed. I would like
the entire office doc search facility to be confined to the SQL server
2005 installation if possible - and from the path specified in the
fulltext_document_types view I take it that it should work this way.
Any help / pointers would be very gratefully received.
Thanks is advance
Jeremy
Hi Jeremy. I see the same thing on my machine, but it does work on my
machine.
Basically you will find the iFilter in %windir%\system32 which is likely
c:\Windows\System32. I am not sure why it refers to this location. You will
find that the persistent handler associated with the .doc extension points
here.
Can you check your Word Docs to make sure that they are not saved in the
fast save format? the Office iFilter does not understand this format.
Also download filtdump from the platform sdk and run your word docs through
this to make sure the iFilter understands them.
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
"Jeremy Holland" <jeremy.holland@.konetic.com> wrote in message
news:1165402032.796856.43690@.l12g2000cwl.googlegro ups.com...
> Hi there
> I might be being dense, but I can't seem to get the Full Text Search
> service working for office type documents. The service works OK for
> text and RTF files, so I know that the Full Text indexing service is
> there, but just doesn't seem to be working for Office docs -
> specifially Word .doc files.
> Digging a little deeper, it seems that the relevant ifilter isn't
> installed. When I run
> select * from sys.fulltext_document_types
> I get the list of document types that can be indexed and searched by
> SQL server 2005. For .the .rtf entry, I get a path of
> c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\msfte.dll
> for the ifilter, version 12.0.6214.0 which is where I would expect it
> to be (ie I can see the msfte.dll file in the Binn directory).
> For the .doc entry, I get a path of
> c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\offfilt.dll
> for the ifilter, but no version number, and when I look at the Binn
> directory, the file is not there.
> Is there any way I can install the office ifilter on SQL server 2005?
> Note that this is a database server so does not have IIS, Sharepoint,
> Desktop search or any other search mechanism installed. I would like
> the entire office doc search facility to be confined to the SQL server
> 2005 installation if possible - and from the path specified in the
> fulltext_document_types view I take it that it should work this way.
> Any help / pointers would be very gratefully received.
> Thanks is advance
> Jeremy
>
|||Hi Hilary
Thanks for your reply - I'll try as you suggest.
Jeremy
|||Hi Hilary
Thanks for that - I registered the OS ifilters and ignored that view as
you suggested.
It seems to work fine now with Word docs - thanks a lot for that.
Jeremy
Jeremy Holland wrote:

> Hi Hilary
> Thanks for your reply - I'll try as you suggest.
> Jeremy

install integration service on existing instance

I need to install Integration Service on an existing SQL 2005 instance. Is
it possible add components to an existing instance or do I need to create a
new instance of SQL server?
When you install SSIS on a Server, the service is "stand alone", not bound to
a specific instance. You can install SSIS alone, running the setup and asking
for the installation of the Integration services without install the other
components
Gilberto Zampatti
"Mike" wrote:

> I need to install Integration Service on an existing SQL 2005 instance. Is
> it possible add components to an existing instance or do I need to create a
> new instance of SQL server?
>
>

install integration service on existing instance

I need to install Integration Service on an existing SQL 2005 instance. Is
it possible add components to an existing instance or do I need to create a
new instance of SQL server?When you install SSIS on a Server, the service is "stand alone", not bound t
o
a specific instance. You can install SSIS alone, running the setup and askin
g
for the installation of the Integration services without install the other
components
Gilberto Zampatti
"Mike" wrote:

> I need to install Integration Service on an existing SQL 2005 instance. Is
> it possible add components to an existing instance or do I need to create
a
> new instance of SQL server?
>
>

install integration service on existing instance

I need to install Integration Service on an existing SQL 2005 instance. Is
it possible add components to an existing instance or do I need to create a
new instance of SQL server?When you install SSIS on a Server, the service is "stand alone", not bound to
a specific instance. You can install SSIS alone, running the setup and asking
for the installation of the Integration services without install the other
components
Gilberto Zampatti
"Mike" wrote:
> I need to install Integration Service on an existing SQL 2005 instance. Is
> it possible add components to an existing instance or do I need to create a
> new instance of SQL server?
>
>sql

Install for Designer Add-In only, should I install SSRS SP2?

I have a dev machine which doesn't have sql2k installed on it, but I need to
install the report designer for VS2003 and sql2k. I have service pack 2 for
ssrs 2k but don't know if I should install it or not since I don't actually
have ssrs running on this machine. Should I run sp2 anyway?
thanks.
--
moondaddy@.noemail.noemailHello,
I understand that you installed report designer for vs 2003 in SSRS 2k, and
you' like to know if you need to install SSRS 2k sp2 on this machine since
you don't actually has SSRS installed. If I'm off-base, please let me know.
As far as I know, You still need to install SSRS sp2 on this machine since
report designer is a component included in SSRS 2k and sp2 shall include
some update for this component. If anything is unclear, please let's know.
Thank you!
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||OK thanks.
I also have SQL 2005 and SSRS 2005 on this machine. I assume that SSRS 2k
sp2 wont effect the 2005 version. Correct?
"Peter Yang [MSFT]" <petery@.online.microsoft.com> wrote in message
news:sMIaT6e3GHA.4464@.TK2MSFTNGXA01.phx.gbl...
> Hello,
> I understand that you installed report designer for vs 2003 in SSRS 2k,
> and
> you' like to know if you need to install SSRS 2k sp2 on this machine since
> you don't actually has SSRS installed. If I'm off-base, please let me
> know.
> As far as I know, You still need to install SSRS sp2 on this machine since
> report designer is a component included in SSRS 2k and sp2 shall include
> some update for this component. If anything is unclear, please let's know.
> Thank you!
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Community Support
> ==================================================> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications
> <http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> <http://msdn.microsoft.com/subscriptions/support/default.aspx>.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Yes, based on my experience, installing SP2 for SSRS 2000 shall not affect
SSRS 2005 installed. If anything is unclear or you encounter issues, please
feel free to let's know. Thank you.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================

install error on web server (windows 2003 web edition/iis6)

During the web server install, I used the network service account to run the
report server.
My Error: setup could not initialize the report server. you must manually
initialize the report server before using it for the 1st time. see reporting
services setup doc.
My environment:
sql server = dbs
web server = report server
client = designer
Do I need to run the rsactivate utility on the web server? How is this done?
Is this correct syntax in the command prompt?
rsconfig -m \\<webserver> -u<administrator> -p<password>
Or, if I am logged onto the web server directly; is this the correct way to
activate the report server?
rsconfig -c"C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportServer\RSReportServer.config"
Thanks,When I tried to pull up the site on my client, I got:
reporting services error
the report server installation is not initialized. check the doc for more
info. (rsreportservernotactivated) get help:
http://www.microsoft.com/products/ee/transform.aspx?EvtSrc=Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings.resources.Strings&EvtID=rsReportServerNotActivated&ProdName=Microsoft+SQL+Server+Reporting+Services&ProdVer=8.00
As a result of the error, I restarted the web server and typed in the
address for the reportserver and got prompted to login. I could not use the
servername, but the ipaddress 192.168.0.4/reportserver
It let me in after logging in and displayed the ms sql server reporting
services v 8.
Does this mean that it is working?
---
"wills" wrote:
> During the web server install, I used the network service account to run the
> report server.
> My Error: setup could not initialize the report server. you must manually
> initialize the report server before using it for the 1st time. see reporting
> services setup doc.
> My environment:
> sql server = dbs
> web server = report server
> client = designer
> Do I need to run the rsactivate utility on the web server? How is this done?
> Is this correct syntax in the command prompt?
> rsconfig -m \\<webserver> -u<administrator> -p<password>
>
> Or, if I am logged onto the web server directly; is this the correct way to
> activate the report server?
> rsconfig -c"C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportServer\RSReportServer.config"
> Thanks,
>|||I tried to test the report manager, 192.168.0.4/reports
I got the following: 192.168.0.4/reports/pages/folder.aspx
Error
The request failed with http status 400. Bad Request.
Home
Does this mean that it is working?
"wills" wrote:
> When I tried to pull up the site on my client, I got:
> reporting services error
> the report server installation is not initialized. check the doc for more
> info. (rsreportservernotactivated) get help:
> http://www.microsoft.com/products/ee/transform.aspx?EvtSrc=Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings.resources.Strings&EvtID=rsReportServerNotActivated&ProdName=Microsoft+SQL+Server+Reporting+Services&ProdVer=8.00
>
> As a result of the error, I restarted the web server and typed in the
> address for the reportserver and got prompted to login. I could not use the
> servername, but the ipaddress 192.168.0.4/reportserver
> It let me in after logging in and displayed the ms sql server reporting
> services v 8.
> Does this mean that it is working?
>
> ---
> "wills" wrote:
> > During the web server install, I used the network service account to run the
> > report server.
> >
> > My Error: setup could not initialize the report server. you must manually
> > initialize the report server before using it for the 1st time. see reporting
> > services setup doc.
> >
> > My environment:
> > sql server = dbs
> > web server = report server
> > client = designer
> >
> > Do I need to run the rsactivate utility on the web server? How is this done?
> > Is this correct syntax in the command prompt?
> >
> > rsconfig -m \\<webserver> -u<administrator> -p<password>
> >
> >
> > Or, if I am logged onto the web server directly; is this the correct way to
> > activate the report server?
> >
> > rsconfig -c"C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> > Services\ReportServer\RSReportServer.config"
> >
> > Thanks,
> >
> >

Install Error - Operating System Service Pack Level (SP1)

I am attempting to install SQL Server 2005 Developer Edition (from CD) on my IBM PC with XP Operating System. During set up, I get a error message (see below) telling me about a Service Pack requirement. When I click on the link provided in the error message, it does not lead to any service pack download.

I'm trying to read thru these forum posts, it seems that there is a service pack that I need to download after installing SQL Server 2005. But how can I install the pack after when I can't install SQL Server. Any help would be greatly appreciated. Below is more information about the version of windows my PC has.

My PC: Windows Version 5.1 (Build 2600.xpsp2.030422-1633:Service Pack 1)

Error message from install program:

Operating System Service Pack Level Requirement. (Error)

Messages

Operating System Service Pack Level Requirement.

"The current operating system does not meet Service Pack level requirements for this SQL Server release. Install the most recent Service Pack from the Microsoft download center at http://go.microsoft.com/fwlink/?LinkId=50380, and then run SQL Server Setup again."

SQL Server 2005 Developer Edition needs SP2 on operating sytesm Windows XP. Please update your operating sytem and then install SQL Server 2005 again. Please see the BOL (Books On Line) for detailed inforamtion.

Installation - Only help file installs, No virtual directories or

Hi,
I am trying to install Reporting Services on Windows 2003 server (with no
service pack). Initially it says Visual Studio is not present which is fine,
i press next, then it goes into installation and there are no prompts for rs
components, sql database creation etc. once installation is finished, only
thing i can see is the reporting services help file in the menu. there are no
virtual directories.
Please help.
thanks
dhariwalWeird. I have two installations on 2003. Do you have IIS running. In 2003
you need to configure it to have asp.net applications supported. 2003 comes
much more locked down. You are correct that you can just ignore VS not being
present.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"K M Dhariwal" <KMDhariwal@.discussions.microsoft.com> wrote in message
news:E9F35571-D726-4F77-BE62-50BA9A363175@.microsoft.com...
> Hi,
> I am trying to install Reporting Services on Windows 2003 server (with no
> service pack). Initially it says Visual Studio is not present which is
> fine,
> i press next, then it goes into installation and there are no prompts for
> rs
> components, sql database creation etc. once installation is finished, only
> thing i can see is the reporting services help file in the menu. there are
> no
> virtual directories.
> Please help.
> thanks
> dhariwal|||Hi,
I also have Reporting Services running on 2003 at other customers and it
works like a charm. This is the first time i am stuck like this with RS. IIS
is up and running as well as asp.net, i have got front page extension
installed as well (do u think extensions are the culprit), one thing i
noticed is that there is default website as well as Microsoft Sharepoint
Administration. Do you think sharepoint is throwing this thing down.
If i re-install IIS, will it make any difference.
thanks
khalid
"Bruce L-C [MVP]" wrote:
> Weird. I have two installations on 2003. Do you have IIS running. In 2003
> you need to configure it to have asp.net applications supported. 2003 comes
> much more locked down. You are correct that you can just ignore VS not being
> present.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "K M Dhariwal" <KMDhariwal@.discussions.microsoft.com> wrote in message
> news:E9F35571-D726-4F77-BE62-50BA9A363175@.microsoft.com...
> > Hi,
> > I am trying to install Reporting Services on Windows 2003 server (with no
> > service pack). Initially it says Visual Studio is not present which is
> > fine,
> > i press next, then it goes into installation and there are no prompts for
> > rs
> > components, sql database creation etc. once installation is finished, only
> > thing i can see is the reporting services help file in the menu. there are
> > no
> > virtual directories.
> > Please help.
> > thanks
> > dhariwal
>
>|||I don't know. Seems like you should have gotten an error message. Sorry, no
brainstorms on what it might be.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"K M Dhariwal" <KMDhariwal@.discussions.microsoft.com> wrote in message
news:8D4C9377-EE84-4535-90D2-88BAA4809964@.microsoft.com...
> Hi,
> I also have Reporting Services running on 2003 at other customers and it
> works like a charm. This is the first time i am stuck like this with RS.
> IIS
> is up and running as well as asp.net, i have got front page extension
> installed as well (do u think extensions are the culprit), one thing i
> noticed is that there is default website as well as Microsoft Sharepoint
> Administration. Do you think sharepoint is throwing this thing down.
> If i re-install IIS, will it make any difference.
> thanks
> khalid
> "Bruce L-C [MVP]" wrote:
>> Weird. I have two installations on 2003. Do you have IIS running. In 2003
>> you need to configure it to have asp.net applications supported. 2003
>> comes
>> much more locked down. You are correct that you can just ignore VS not
>> being
>> present.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "K M Dhariwal" <KMDhariwal@.discussions.microsoft.com> wrote in message
>> news:E9F35571-D726-4F77-BE62-50BA9A363175@.microsoft.com...
>> > Hi,
>> > I am trying to install Reporting Services on Windows 2003 server (with
>> > no
>> > service pack). Initially it says Visual Studio is not present which is
>> > fine,
>> > i press next, then it goes into installation and there are no prompts
>> > for
>> > rs
>> > components, sql database creation etc. once installation is finished,
>> > only
>> > thing i can see is the reporting services help file in the menu. there
>> > are
>> > no
>> > virtual directories.
>> > Please help.
>> > thanks
>> > dhariwal
>>

Install Database Components SP3a

Hi,
Do I need to know the sa password when I install Database Components for
SP3a? The extracted service pack files is in the directory of the local
computer.
Thanks.Only if you're installing on the SQL Server/MSDE, not for the clients.
"Samuel Yap" <yaphcs@.yahoo.com> wrote in message
news:%231rcsX0dDHA.3596@.tk2msftngp13.phx.gbl...
> Hi,
> Do I need to know the sa password when I install Database Components for
> SP3a? The extracted service pack files is in the directory of the local
> computer.
> Thanks.
>|||Yes, preferably. But any account that has system administrator privileges to
SQL Server should suffice I suppose. "sa" account is safe and sure to have
all the access to the database files for sure.
--
HTH,
Vinod Kumar
MCSE, DBA, MCAD
http://www.extremeexperts.com
"Samuel Yap" <yaphcs@.yahoo.com> wrote in message
news:%231rcsX0dDHA.3596@.tk2msftngp13.phx.gbl...
> Hi,
> Do I need to know the sa password when I install Database Components for
> SP3a? The extracted service pack files is in the directory of the local
> computer.
> Thanks.
>|||Noted. Thanks.
"Vinodk" <vinodk_sct@.NO_SPAM_hotmail.com> wrote in message
news:eqSUIi0dDHA.3992@.TK2MSFTNGP11.phx.gbl...
> Yes, preferably. But any account that has system administrator privileges
to
> SQL Server should suffice I suppose. "sa" account is safe and sure to have
> all the access to the database files for sure.
> --
> HTH,
> Vinod Kumar
> MCSE, DBA, MCAD
> http://www.extremeexperts.com
>
> "Samuel Yap" <yaphcs@.yahoo.com> wrote in message
> news:%231rcsX0dDHA.3596@.tk2msftngp13.phx.gbl...
> > Hi,
> >
> > Do I need to know the sa password when I install Database Components for
> > SP3a? The extracted service pack files is in the directory of the local
> > computer.
> >
> > Thanks.
> >
> >
>

install analysis services on sql server 2005 workgroup

I made an analysis services project but I can't deploy it because it can't find the server
I search for the analysis service in the Service Control Manager but I can't find it.
Is it possible to download and install it with this version of sql server (workgroup) ?SQL Server 2005 does not contain Analysis Services. If you wish to use Analysis Services features you'll have to upgrade to Standard Edition. For further information about features in the various editons of SQL Server, you may have a look at SQL Server 2005 Features Comparison (http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx)|||thank you
I hope that there's an upgrade.

Instalation

I'm facing a problem while installing SQL Server 2005 Express. When SQLServer Installer going to start service during instalation, installer don't start service and rollback the instalation. i found following message in SQL

LOG File

.2007-08-31 12:01:17.28 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2007-08-31 12:01:17.28 Server Detected 1 CPUs. This is an informational message; no user action is required.
2007-08-31 12:04:36.56 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2007-08-31 12:04:38.06 Server Database Mirroring Transport is disabled in the endpoint configuration.

2007-08-30 00:07:34.21 Server Service control: stop before startup

if u have any solution regarding above please help me.

Thankx in advance.

Hi Zaib,

Please check this KB article and follow up the workaround inside.

http://support.microsoft.com/kb/920114

Error message when you try to install SQL Server Express or SQL Server Express Edition or SQL Server Express Edition with Advanced Services: "The SQL Server service failed to start"

CAUSE

This problem occurs because the Network Service account does not have permissions on the following folder: C:\Documents and Settings\NetworkService\Application Data\Microsoft\Protect

WORKAROUND

To work around this problem, grant the Network Service account the Full Control permission on the Protect folder. To do this, follow these steps:

1.

Open My Computer.

2.

Type C:\Documents and Settings\NetworkService\Application Data\Microsoft in the address bar, and then press ENTER.

3.

Right-click the Protect folder, and then click Properties.

4.

In the folder Properties dialog box, click the Security tab.

5.

Under Group or user names, determine whether NETWORK SERVICE is listed. If NETWORK SERVICE is not listed, follow these steps to add this account:

a. Click Add to show the Select Users or Groups dialog box. b. Click Locations, select your computer name in the Locations dialog box, and then click OK to return to the Select Users or Groups dialog box. c. Type Network Service in the Enter the object names to select box, and then click Check Names. d. Click OK to close the Select Users or Groups dialog box.

6.

Click NETWORK SERVICE under Group or user names, and then click to select the Allow check box for Full Control under Permissions for NETWORK SERVICE.

7.

Click OK to close the folder Properties dialog box.

8.

Click Retry in the error message dialog box to continue to install SQL Server Express Edition or SQL Server Express Edition with Advanced Services.

Note that the NetworkService folder may be hidden, and If the Protect folder is not found, you need to create it manually.

Please take a try. I hope that can help you.

These threads are similar to your issue.

SQL Express installation error

SQL Express Cannot Start
SQL server 2005 express failed to install under win2k SP4

Best regards,

Martin Xie

|||

I move it from VB Express forum to SQL Server Express forum for better responses.

Thanks,

Martin

Instalation

I'm facing a problem while installing SQL Server 2005 Express. When SQLServer Installer going to start service during instalation, installer don't start service and rollback the instalation. i found following message in SQL

LOG File

.2007-08-31 12:01:17.28 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2007-08-31 12:01:17.28 Server Detected 1 CPUs. This is an informational message; no user action is required.
2007-08-31 12:04:36.56 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2007-08-31 12:04:38.06 Server Database Mirroring Transport is disabled in the endpoint configuration.

2007-08-30 00:07:34.21 Server Service control: stop before startup

if u have any solution regarding above please help me.

Thankx in advance.

Hi Zaib,

Please check this KB article and follow up the workaround inside.

http://support.microsoft.com/kb/920114

Error message when you try to install SQL Server Express or SQL Server Express Edition or SQL Server Express Edition with Advanced Services: "The SQL Server service failed to start"

CAUSE

This problem occurs because the Network Service account does not have permissions on the following folder: C:\Documents and Settings\NetworkService\Application Data\Microsoft\Protect

WORKAROUND

To work around this problem, grant the Network Service account the Full Control permission on the Protect folder. To do this, follow these steps:

1.

Open My Computer.

2.

Type C:\Documents and Settings\NetworkService\Application Data\Microsoft in the address bar, and then press ENTER.

3.

Right-click the Protect folder, and then click Properties.

4.

In the folder Properties dialog box, click the Security tab.

5.

Under Group or user names, determine whether NETWORK SERVICE is listed. If NETWORK SERVICE is not listed, follow these steps to add this account:

a. Click Add to show the Select Users or Groups dialog box. b. Click Locations, select your computer name in the Locations dialog box, and then click OK to return to the Select Users or Groups dialog box. c. Type Network Service in the Enter the object names to select box, and then click Check Names. d. Click OK to close the Select Users or Groups dialog box.

6.

Click NETWORK SERVICE under Group or user names, and then click to select the Allow check box for Full Control under Permissions for NETWORK SERVICE.

7.

Click OK to close the folder Properties dialog box.

8.

Click Retry in the error message dialog box to continue to install SQL Server Express Edition or SQL Server Express Edition with Advanced Services.

Note that the NetworkService folder may be hidden, and If the Protect folder is not found, you need to create it manually.

Please take a try. I hope that can help you.

These threads are similar to your issue.

SQL Express installation error

SQL Express Cannot Start
SQL server 2005 express failed to install under win2k SP4

Best regards,

Martin Xie

|||

I move it from VB Express forum to SQL Server Express forum for better responses.

Thanks,

Martin

Insertion failed

I have a service that writes a lot of records to many
tables in SQL server. Recently, the service failed in
writing record to any of the tables. But, the retrieving
of the records is still OK. By examining the application
log file, it seems that the SQL server started to
deteriorate by not allowing insertion in one table at a
time and eventually all tables are rejected for insertion.
I ended up re-booting the system and everything went back
to normal. After the reboot, I checked the SQL log file
and noticed that about 18,000 records were rolled forward
during SQL Server start-up.
Does anybody have any idea as why the insertion would
fail? And why the checkpoint was not executed even there
are about 18,000 committed transactions?Mike,
Perhaps the database space filled up as one table attempted to grow again.
Tables that still had some space left in them could take a few more rows,
then they were filled up as well and would no longer take any more rows.
Etc. Etc.
If this is the case, either allocate more space or turn on autogrow for the
database in question.
With regard to your closing comment, checkpoint is not equal to a commit.
Without knowing the period covered by the 18,000 records and something more
about your server it is not possible to offer details. However, I would
think that checkpointing was working just fine.
Russell Fields
"mike" <mike@.ftsl.com> wrote in message
news:5c0401c3e5e3$cb4094d0$a101280a@.phx.gbl...

quote:

---

> I have a service that writes a lot of records to many
> tables in SQL server. Recently, the service failed in
> writing record to any of the tables. But, the retrieving
> of the records is still OK. By examining the application
> log file, it seems that the SQL server started to
> deteriorate by not allowing insertion in one table at a
> time and eventually all tables are rejected for insertion.
> I ended up re-booting the system and everything went back
> to normal. After the reboot, I checked the SQL log file
> and noticed that about 18,000 records were rolled forward
> during SQL Server start-up.
> Does anybody have any idea as why the insertion would
> fail? And why the checkpoint was not executed even there
> are about 18,000 committed transactions?
>

---

|||Russell - Thank you for your reply.
I was also thinking about the possible disk space problem
but I don't think it's the case here. There was about 10G
left in the disk when this happened. At the same time, the
database files (data & transaction) are set to auto-grow.
If disk space was the problem, I would think rebooting the
server couldn't solve the problem. Based on my
calculation, in 5 mins period, properly 3500 record would
have been inserted to the table.

quote:

---

>--Original Message--
>Mike,
>Perhaps the database space filled up as one table

---

attempted to grow again.

quote:

---

>Tables that still had some space left in them could take

---

a few more rows,

quote:

---

>then they were filled up as well and would no longer take

---

any more rows.

quote:

---

>Etc. Etc.
>If this is the case, either allocate more space or turn

---

on autogrow for the

quote:

---

>database in question.
>With regard to your closing comment, checkpoint is not

---

equal to a commit.

quote:

---

>Without knowing the period covered by the 18,000 records

---

and something more

quote:

---

>about your server it is not possible to offer details.

---

However, I would

quote:

---

>think that checkpointing was working just fine.
>Russell Fields
>"mike" <mike@.ftsl.com> wrote in message
>news:5c0401c3e5e3$cb4094d0$a101280a@.phx.gbl...
insertion.[QUOTE]
back[QUOTE]
forward[QUOTE]
>
>.
>

---

|||Mike,
Sorry that I do not have a better idea.
We had problems at one time when another process besides SQL Server was
using the same disk. It wrote LOTS of data into an operating system file
eating up the disk, then either deleted it again or ran out of space itself,
causing the file write to abort. Since you have 10 GB free, then it is hard
to believe that a similar thing is happening to you.
Regarding checkpoints, this is set using the "recovery interval" option.
You might read up on this and discover that the timing of checkpoints is
more complicated than you would have thought.
Russell Fields
"mike" <mike@.ftsl.com> wrote in message
news:635a01c3e5ef$46160ae0$a501280a@.phx.gbl...[QUOTE]
> Russell - Thank you for your reply.
> I was also thinking about the possible disk space problem
> but I don't think it's the case here. There was about 10G
> left in the disk when this happened. At the same time, the
> database files (data & transaction) are set to auto-grow.
> If disk space was the problem, I would think rebooting the
> server couldn't solve the problem. Based on my
> calculation, in 5 mins period, properly 3500 record would
> have been inserted to the table.
>
> attempted to grow again.
> a few more rows,
> any more rows.
> on autogrow for the
> equal to a commit.
> and something more
> However, I would
> insertion.
> back
> forward|||Hi Mike,
Thank you for using the newsgroup and it is my pleasure to help you with
you issue.
As my understanding of your problem, when inserting a large amount of
records to many tables but failed by insert rejection to tables one by one.
You rebooted the system and everything seems OK again. and you found in SQL
log that SQL Server rolled forward the inserting during the startup, so
many records are inserting, you wonder why insert failed and how the
rolling forward come, right?
I would better to explain the rolling forwand first. The log records for a
transaction ( both a transaction.. commit structure or a single T-SQL
statement) are written to disk before the commit acknowledgement is sent to
the client process, but the actual changed data might not have been
physically written out to the data pages. That is, writes to data pages
need only be posted to the operating system, and SQL Server can check later
to see that they were completed. They don't have to complete immediately
because the log contains all the information needed to redo the work, even
in the event of a power failure or system crash before the write completes.
When you reboot you system and start SQL Server, recovery performs both
redo (rollforward) and undo (rollback) operations. In a redo operation, the
log is examined and each change is verified as being already reflected in
the database. (After a redo, every change made by the transaction is
guaranteed to have been applied.) If the change doesn't appear in the
database, it is again performed from the information in the log. Every
database page has an LSN in the page header that uniquely identifies it, by
version, as rows on the page are changed over time. This page LSN reflects
the location in the transaction log of the last log entry that modified a
row on this page. During a redo operation of transactions, the LSN of each
log record is compared to the page LSN of the data page that the log entry
modified; if the page LSN is less than the log LSN, the operation indicated
in the log entry should be redo, that is, should be roll forward. As for
the 18,000 record insert in the SQL start process, they are the modified
records that have been recorded in the transaction log, but have not been
writen to the database.
When you commit the transaction, the data modifications will be have been
made a permanent part of the database. no roll forward or roll back is
needed.
For the checkpiont, it will flush dirty data and log pages from the buffer
cache of the current database, minimizing the number of modifications that
have to be rolled forward during a recovery. So, that 18,000 records
insertings active operations that have been recorded in the log file after
or when check point occures, they are logged into the transaction log. For
more information of checkpoint, when it will occure, what SQL Server will
do when checkpoint come, please refer to 'checkpoing' in the SQL Server
Books Online.
As for your questions of how the records insertings are rejected by tables
one by one, it would be very helpful for you to provide the detailed error
message, the error log and the T-SQL you were excuting at that time for
further analysis. Thanks.
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.
I have a service that writes a lot of records to many
tables in SQL server. Recently, the service failed in
writing record to any of the tables. But, the retrieving
of the records is still OK. By examining the application
log file, it seems that the SQL server started to
deteriorate by not allowing insertion in one table at a
time and eventually all tables are rejected for insertion.
I ended up re-booting the system and everything went back
to normal. After the reboot, I checked the SQL log file
and noticed that about 18,000 records were rolled forward
during SQL Server start-up.
Does anybody have any idea as why the insertion would
fail? And why the checkpoint was not executed even there
are about 18,000 committed transactions?|||From: v-baiwei@.online.microsoft.com (Baisong Wei[MSFT])
Date: Fri, 30 Jan 2004 05:10:41 GMT
Subject: RE: Insertion failed
Newsgroups: microsoft.public.sqlserver.server
Hi Mike,
Thank you for using the newsgroup and it is my pleasure to help you with
you issue.
As my understanding of your problem, when inserting a large amount of
records to many tables but failed by insert rejection to tables one by one.
You rebooted the system and everything seems OK again. and you found in SQL
log that SQL Server rolled forward the inserting during the startup, so
many records are inserting, you wonder why insert failed and how the
rolling forward come, right?
I would better to explain the rolling forwand first. The log records for a
transaction ( both a transaction.. commit structure or a single T-SQL
statement) are written to disk before the commit acknowledgement is sent to
the client process, but the actual changed data might not have been
physically written out to the data pages. That is, writes to data pages
need only be posted to the operating system, and SQL Server can check later
to see that they were completed. They don't have to complete immediately
because the log contains all the information needed to redo the work, even
in the event of a power failure or system crash before the write completes.
When you reboot you system and start SQL Server, recovery performs both
redo (rollforward) and undo (rollback) operations. In a redo operation, the
log is examined and each change is verified as being already reflected in
the database. (After a redo, every change made by the transaction is
guaranteed to have been applied.) If the change doesn't appear in the
database, it is again performed from the information in the log. Every
database page has an LSN in the page header that uniquely identifies it, by
version, as rows on the page are changed over time. This page LSN reflects
the location in the transaction log of the last log entry that modified a
row on this page. During a redo operation of transactions, the LSN of each
log record is compared to the page LSN of the data page that the log entry
modified; if the page LSN is less than the log LSN, the operation indicated
in the log entry should be redo, that is, should be roll forward. As for
the 18,000 record insert in the SQL start process, they are the modified
records that have been recorded in the transaction log, but have not been
writen to the database.
When you commit the transaction, the data modifications will be have been
made a permanent part of the database ( in the log file).
For the checkpiont, it will flush dirty data and log pages from the buffer
cache of the current database, minimizing the number of modifications that
have to be rolled forward during a recovery. So, that 18,000 records
insertings active operations that have been recorded in the log file after
or when check point occures, they are logged into the transaction log. For
more information of checkpoint, when it will occure, what SQL Server will
do when checkpoint come, please refer to 'checkpoing' in the SQL Server
Books Online. You could also refer to 'recoery mode' too.
As for your questions of how the records insertings are rejected by tables
one by one, it would be very helpful for you to provide the detailed error
message, the error log and the T-SQL you were excuting at that time for
further analysis. Thanks.
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.|||Hi Mike,
Thank you for using the newsgroup and it is my pleasure to help you with
you issue.
As my understanding of your problem, when inserting a large amount of
records to many tables but failed by insert rejection to tables one by one.
You rebooted the system and everything seems OK again. and you found in SQL
log that SQL Server rolled forward the inserting during the startup, so
many records are inserting, you wonder why insert failed and how the
rolling forward come, right?
I would better to explain the rolling forwand first. The log records for a
transaction ( both a transaction.. commit structure or a single T-SQL
statement) are written to disk before the commit acknowledgement is sent to
the client process, but the actual changed data might not have been
physically written out to the data pages. That is, writes to data pages
need only be posted to the operating system, and SQL Server can check later
to see that they were completed. They don't have to complete immediately
because the log contains all the information needed to redo the work, even
in the event of a power failure or system crash before the write completes.
When you reboot you system and start SQL Server, recovery performs both
redo (rollforward) and undo (rollback) operations. In a redo operation, the
log is examined and each change is verified as being already reflected in
the database. (After a redo, every change made by the transaction is
guaranteed to have been applied.) If the change doesn't appear in the
database, it is again performed from the information in the log. Every
database page has an LSN in the page header that uniquely identifies it, by
version, as rows on the page are changed over time. This page LSN reflects
the location in the transaction log of the last log entry that modified a
row on this page. During a redo operation of transactions, the LSN of each
log record is compared to the page LSN of the data page that the log entry
modified; if the page LSN is less than the log LSN, the operation indicated
in the log entry should be redo, that is, should be roll forward. As for
the 18,000 record insert in the SQL start process, they are the modified
records that have been recorded in the transaction log, but have not been
writen to the database.
When you commit the transaction, the data modifications will be have been
made a permanent part of the database ( in the log file).
For the checkpiont, it will flush dirty data and log pages from the buffer
cache of the current database, minimizing the number of modifications that
have to be rolled forward during a recovery. So, that 18,000 records
insertings active operations that have been recorded in the log file after
or when check point occures, they are logged into the transaction log. For
more information of checkpoint, when it will occure, what SQL Server will
do when checkpoint come, please refer to 'checkpoing' in the SQL Server
Books Online. You could also refer to 'recoery mode' too.
As for your questions of how the records insertings are rejected by tables
one by one, it would be very helpful for you to provide the detailed error
message, the error log and the T-SQL you were excuting at that time for
further analysis. Thanks.
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.|||Hi Baisong,
Thank you for your reply and I understand the description
provided. Here is more background regarding to my problem:
1. We use ADO command object to perform single T-SQL
statement with a time-out value set to one minute.
2. On average, we perform approximately 36,960 T-SQL
statements per hour.
3. Database and transaction files are set to auto grew at
a rate of (10%)
4. Unfortunately, we don't know what the error message was
generated by SQL Server when the records failed to be
written.
5. All the non-SQL processes appeared to be running
normally at the time of the restart. This information was
gathered using Windows Task Manager.
6. No rolled-forward information was logged in SQL Server
log files in previous restarts.
7. Prior to the restart, new information was unable to
insert into the database, but old records can be retrieved.
8. The largest table in the database had 25,000,000
records at the time of the problem.
Question:
What could be happening on the server that would result in
1) failed to insert, and 2) rolled forward of 18000
records in restart.|||Hi Mike,
Thank you for using the newsgroup and it is my pleasure to help you with
you issue.
In you first post, you mentioned that 'By examining the application log
file, it seems that the SQL server started to deteriorate by not allowing
insertion in one table at a time and eventually all tables are rejected for
insertion.' and in your last post, you mentioned that 'we don't know what
the error message was generated by SQL Server when the records failed to be
written'. I wonder if you could provide the content of this part of the log
that you made this judgement, what made you think that the insertion is
rejected while no error message indicating any abnormal. Any blocking of
locks or any information from you application side? This information is
helpful for our analysis. Second, as I mentioned in my last post, when an
operation is executed, this operation will be write to log but not
necessary to write to .MDB file, when checkpoint come, they will be write
to the MDB file. I think that it is because the 18,000 records' insert have
been written into the log file, but not to the .MDB file, so, when SQL
Server restart, it will compare with the LSN of page and log to decide
roll-forward or roll-back, no difference between, in the SQL Server start
process, no this action is taken, as in your past restart. Besides the log
message, could you please provide the recovery mode of you database?
As the ADO time-out option, I suggest you to set to zero, which prepresent
no limit for time-out.
Looking for your reply and thanks.
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.|||Baisong,
What I meant by 'By examining the application log
file,...' is checking the SQL server tables that the
application is writing to. All the written records
contain a time stamp; therefore I can tell when the
insertion started to fail on these tables.
'we don't know what the error message was generated by SQL
Server when the records failed' simply means that the
application did not log any error returned by the ADO
command object.
The recovery mode that the database uses is 'Full Recovery
Mode'
Mike

Insertion failed

I have a service that writes a lot of records to many
tables in SQL server. Recently, the service failed in
writing record to any of the tables. But, the retrieving
of the records is still OK. By examining the application
log file, it seems that the SQL server started to
deteriorate by not allowing insertion in one table at a
time and eventually all tables are rejected for insertion.
I ended up re-booting the system and everything went back
to normal. After the reboot, I checked the SQL log file
and noticed that about 18,000 records were rolled forward
during SQL Server start-up.
Does anybody have any idea as why the insertion would
fail? And why the checkpoint was not executed even there
are about 18,000 committed transactions?Mike,
Perhaps the database space filled up as one table attempted to grow again.
Tables that still had some space left in them could take a few more rows,
then they were filled up as well and would no longer take any more rows.
Etc. Etc.
If this is the case, either allocate more space or turn on autogrow for the
database in question.
With regard to your closing comment, checkpoint is not equal to a commit.
Without knowing the period covered by the 18,000 records and something more
about your server it is not possible to offer details. However, I would
think that checkpointing was working just fine.
Russell Fields
"mike" <mike@.ftsl.com> wrote in message
news:5c0401c3e5e3$cb4094d0$a101280a@.phx.gbl...
> I have a service that writes a lot of records to many
> tables in SQL server. Recently, the service failed in
> writing record to any of the tables. But, the retrieving
> of the records is still OK. By examining the application
> log file, it seems that the SQL server started to
> deteriorate by not allowing insertion in one table at a
> time and eventually all tables are rejected for insertion.
> I ended up re-booting the system and everything went back
> to normal. After the reboot, I checked the SQL log file
> and noticed that about 18,000 records were rolled forward
> during SQL Server start-up.
> Does anybody have any idea as why the insertion would
> fail? And why the checkpoint was not executed even there
> are about 18,000 committed transactions?
>|||Russell - Thank you for your reply.
I was also thinking about the possible disk space problem
but I don't think it's the case here. There was about 10G
left in the disk when this happened. At the same time, the
database files (data & transaction) are set to auto-grow.
If disk space was the problem, I would think rebooting the
server couldn't solve the problem. Based on my
calculation, in 5 mins period, properly 3500 record would
have been inserted to the table.
>--Original Message--
>Mike,
>Perhaps the database space filled up as one table
attempted to grow again.
>Tables that still had some space left in them could take
a few more rows,
>then they were filled up as well and would no longer take
any more rows.
>Etc. Etc.
>If this is the case, either allocate more space or turn
on autogrow for the
>database in question.
>With regard to your closing comment, checkpoint is not
equal to a commit.
>Without knowing the period covered by the 18,000 records
and something more
>about your server it is not possible to offer details.
However, I would
>think that checkpointing was working just fine.
>Russell Fields
>"mike" <mike@.ftsl.com> wrote in message
>news:5c0401c3e5e3$cb4094d0$a101280a@.phx.gbl...
>> I have a service that writes a lot of records to many
>> tables in SQL server. Recently, the service failed in
>> writing record to any of the tables. But, the retrieving
>> of the records is still OK. By examining the application
>> log file, it seems that the SQL server started to
>> deteriorate by not allowing insertion in one table at a
>> time and eventually all tables are rejected for
insertion.
>> I ended up re-booting the system and everything went
back
>> to normal. After the reboot, I checked the SQL log file
>> and noticed that about 18,000 records were rolled
forward
>> during SQL Server start-up.
>> Does anybody have any idea as why the insertion would
>> fail? And why the checkpoint was not executed even there
>> are about 18,000 committed transactions?
>
>.
>|||Mike,
Sorry that I do not have a better idea.
We had problems at one time when another process besides SQL Server was
using the same disk. It wrote LOTS of data into an operating system file
eating up the disk, then either deleted it again or ran out of space itself,
causing the file write to abort. Since you have 10 GB free, then it is hard
to believe that a similar thing is happening to you.
Regarding checkpoints, this is set using the "recovery interval" option.
You might read up on this and discover that the timing of checkpoints is
more complicated than you would have thought.
Russell Fields
"mike" <mike@.ftsl.com> wrote in message
news:635a01c3e5ef$46160ae0$a501280a@.phx.gbl...
> Russell - Thank you for your reply.
> I was also thinking about the possible disk space problem
> but I don't think it's the case here. There was about 10G
> left in the disk when this happened. At the same time, the
> database files (data & transaction) are set to auto-grow.
> If disk space was the problem, I would think rebooting the
> server couldn't solve the problem. Based on my
> calculation, in 5 mins period, properly 3500 record would
> have been inserted to the table.
> >--Original Message--
> >Mike,
> >
> >Perhaps the database space filled up as one table
> attempted to grow again.
> >Tables that still had some space left in them could take
> a few more rows,
> >then they were filled up as well and would no longer take
> any more rows.
> >Etc. Etc.
> >
> >If this is the case, either allocate more space or turn
> on autogrow for the
> >database in question.
> >
> >With regard to your closing comment, checkpoint is not
> equal to a commit.
> >Without knowing the period covered by the 18,000 records
> and something more
> >about your server it is not possible to offer details.
> However, I would
> >think that checkpointing was working just fine.
> >
> >Russell Fields
> >"mike" <mike@.ftsl.com> wrote in message
> >news:5c0401c3e5e3$cb4094d0$a101280a@.phx.gbl...
> >> I have a service that writes a lot of records to many
> >> tables in SQL server. Recently, the service failed in
> >> writing record to any of the tables. But, the retrieving
> >> of the records is still OK. By examining the application
> >> log file, it seems that the SQL server started to
> >> deteriorate by not allowing insertion in one table at a
> >> time and eventually all tables are rejected for
> insertion.
> >> I ended up re-booting the system and everything went
> back
> >> to normal. After the reboot, I checked the SQL log file
> >> and noticed that about 18,000 records were rolled
> forward
> >> during SQL Server start-up.
> >>
> >> Does anybody have any idea as why the insertion would
> >> fail? And why the checkpoint was not executed even there
> >> are about 18,000 committed transactions?
> >>
> >
> >
> >.
> >|||Hi Mike,
Thank you for using the newsgroup and it is my pleasure to help you with
you issue.
As my understanding of your problem, when inserting a large amount of
records to many tables but failed by insert rejection to tables one by one.
You rebooted the system and everything seems OK again. and you found in SQL
log that SQL Server rolled forward the inserting during the startup, so
many records are inserting, you wonder why insert failed and how the
rolling forward come, right?
I would better to explain the rolling forwand first. The log records for a
transaction ( both a transaction.. commit structure or a single T-SQL
statement) are written to disk before the commit acknowledgement is sent to
the client process, but the actual changed data might not have been
physically written out to the data pages. That is, writes to data pages
need only be posted to the operating system, and SQL Server can check later
to see that they were completed. They don't have to complete immediately
because the log contains all the information needed to redo the work, even
in the event of a power failure or system crash before the write completes.
When you reboot you system and start SQL Server, recovery performs both
redo (rollforward) and undo (rollback) operations. In a redo operation, the
log is examined and each change is verified as being already reflected in
the database. (After a redo, every change made by the transaction is
guaranteed to have been applied.) If the change doesn't appear in the
database, it is again performed from the information in the log. Every
database page has an LSN in the page header that uniquely identifies it, by
version, as rows on the page are changed over time. This page LSN reflects
the location in the transaction log of the last log entry that modified a
row on this page. During a redo operation of transactions, the LSN of each
log record is compared to the page LSN of the data page that the log entry
modified; if the page LSN is less than the log LSN, the operation indicated
in the log entry should be redo, that is, should be roll forward. As for
the 18,000 record insert in the SQL start process, they are the modified
records that have been recorded in the transaction log, but have not been
writen to the database.
When you commit the transaction, the data modifications will be have been
made a permanent part of the database. no roll forward or roll back is
needed.
For the checkpiont, it will flush dirty data and log pages from the buffer
cache of the current database, minimizing the number of modifications that
have to be rolled forward during a recovery. So, that 18,000 records
insertings active operations that have been recorded in the log file after
or when check point occures, they are logged into the transaction log. For
more information of checkpoint, when it will occure, what SQL Server will
do when checkpoint come, please refer to 'checkpoing' in the SQL Server
Books Online.
As for your questions of how the records insertings are rejected by tables
one by one, it would be very helpful for you to provide the detailed error
message, the error log and the T-SQL you were excuting at that time for
further analysis. Thanks.
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.
I have a service that writes a lot of records to many
tables in SQL server. Recently, the service failed in
writing record to any of the tables. But, the retrieving
of the records is still OK. By examining the application
log file, it seems that the SQL server started to
deteriorate by not allowing insertion in one table at a
time and eventually all tables are rejected for insertion.
I ended up re-booting the system and everything went back
to normal. After the reboot, I checked the SQL log file
and noticed that about 18,000 records were rolled forward
during SQL Server start-up.
Does anybody have any idea as why the insertion would
fail? And why the checkpoint was not executed even there
are about 18,000 committed transactions?|||From: v-baiwei@.online.microsoft.com (Baisong Wei[MSFT])
Date: Fri, 30 Jan 2004 05:10:41 GMT
Subject: RE: Insertion failed
Newsgroups: microsoft.public.sqlserver.server
Hi Mike,
Thank you for using the newsgroup and it is my pleasure to help you with
you issue.
As my understanding of your problem, when inserting a large amount of
records to many tables but failed by insert rejection to tables one by one.
You rebooted the system and everything seems OK again. and you found in SQL
log that SQL Server rolled forward the inserting during the startup, so
many records are inserting, you wonder why insert failed and how the
rolling forward come, right?
I would better to explain the rolling forwand first. The log records for a
transaction ( both a transaction.. commit structure or a single T-SQL
statement) are written to disk before the commit acknowledgement is sent to
the client process, but the actual changed data might not have been
physically written out to the data pages. That is, writes to data pages
need only be posted to the operating system, and SQL Server can check later
to see that they were completed. They don't have to complete immediately
because the log contains all the information needed to redo the work, even
in the event of a power failure or system crash before the write completes.
When you reboot you system and start SQL Server, recovery performs both
redo (rollforward) and undo (rollback) operations. In a redo operation, the
log is examined and each change is verified as being already reflected in
the database. (After a redo, every change made by the transaction is
guaranteed to have been applied.) If the change doesn't appear in the
database, it is again performed from the information in the log. Every
database page has an LSN in the page header that uniquely identifies it, by
version, as rows on the page are changed over time. This page LSN reflects
the location in the transaction log of the last log entry that modified a
row on this page. During a redo operation of transactions, the LSN of each
log record is compared to the page LSN of the data page that the log entry
modified; if the page LSN is less than the log LSN, the operation indicated
in the log entry should be redo, that is, should be roll forward. As for
the 18,000 record insert in the SQL start process, they are the modified
records that have been recorded in the transaction log, but have not been
writen to the database.
When you commit the transaction, the data modifications will be have been
made a permanent part of the database ( in the log file).
For the checkpiont, it will flush dirty data and log pages from the buffer
cache of the current database, minimizing the number of modifications that
have to be rolled forward during a recovery. So, that 18,000 records
insertings active operations that have been recorded in the log file after
or when check point occures, they are logged into the transaction log. For
more information of checkpoint, when it will occure, what SQL Server will
do when checkpoint come, please refer to 'checkpoing' in the SQL Server
Books Online. You could also refer to 'recoery mode' too.
As for your questions of how the records insertings are rejected by tables
one by one, it would be very helpful for you to provide the detailed error
message, the error log and the T-SQL you were excuting at that time for
further analysis. Thanks.
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.|||Hi Mike,
Thank you for using the newsgroup and it is my pleasure to help you with
you issue.
As my understanding of your problem, when inserting a large amount of
records to many tables but failed by insert rejection to tables one by one.
You rebooted the system and everything seems OK again. and you found in SQL
log that SQL Server rolled forward the inserting during the startup, so
many records are inserting, you wonder why insert failed and how the
rolling forward come, right?
I would better to explain the rolling forwand first. The log records for a
transaction ( both a transaction.. commit structure or a single T-SQL
statement) are written to disk before the commit acknowledgement is sent to
the client process, but the actual changed data might not have been
physically written out to the data pages. That is, writes to data pages
need only be posted to the operating system, and SQL Server can check later
to see that they were completed. They don't have to complete immediately
because the log contains all the information needed to redo the work, even
in the event of a power failure or system crash before the write completes.
When you reboot you system and start SQL Server, recovery performs both
redo (rollforward) and undo (rollback) operations. In a redo operation, the
log is examined and each change is verified as being already reflected in
the database. (After a redo, every change made by the transaction is
guaranteed to have been applied.) If the change doesn't appear in the
database, it is again performed from the information in the log. Every
database page has an LSN in the page header that uniquely identifies it, by
version, as rows on the page are changed over time. This page LSN reflects
the location in the transaction log of the last log entry that modified a
row on this page. During a redo operation of transactions, the LSN of each
log record is compared to the page LSN of the data page that the log entry
modified; if the page LSN is less than the log LSN, the operation indicated
in the log entry should be redo, that is, should be roll forward. As for
the 18,000 record insert in the SQL start process, they are the modified
records that have been recorded in the transaction log, but have not been
writen to the database.
When you commit the transaction, the data modifications will be have been
made a permanent part of the database ( in the log file).
For the checkpiont, it will flush dirty data and log pages from the buffer
cache of the current database, minimizing the number of modifications that
have to be rolled forward during a recovery. So, that 18,000 records
insertings active operations that have been recorded in the log file after
or when check point occures, they are logged into the transaction log. For
more information of checkpoint, when it will occure, what SQL Server will
do when checkpoint come, please refer to 'checkpoing' in the SQL Server
Books Online. You could also refer to 'recoery mode' too.
As for your questions of how the records insertings are rejected by tables
one by one, it would be very helpful for you to provide the detailed error
message, the error log and the T-SQL you were excuting at that time for
further analysis. Thanks.
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.|||Hi Baisong,
Thank you for your reply and I understand the description
provided. Here is more background regarding to my problem:
1. We use ADO command object to perform single T-SQL
statement with a time-out value set to one minute.
2. On average, we perform approximately 36,960 T-SQL
statements per hour.
3. Database and transaction files are set to auto grew at
a rate of (10%)
4. Unfortunately, we don't know what the error message was
generated by SQL Server when the records failed to be
written.
5. All the non-SQL processes appeared to be running
normally at the time of the restart. This information was
gathered using Windows Task Manager.
6. No rolled-forward information was logged in SQL Server
log files in previous restarts.
7. Prior to the restart, new information was unable to
insert into the database, but old records can be retrieved.
8. The largest table in the database had 25,000,000
records at the time of the problem.
Question:
What could be happening on the server that would result in
1) failed to insert, and 2) rolled forward of 18000
records in restart.|||Hi Mike,
Thank you for using the newsgroup and it is my pleasure to help you with
you issue.
In you first post, you mentioned that 'By examining the application log
file, it seems that the SQL server started to deteriorate by not allowing
insertion in one table at a time and eventually all tables are rejected for
insertion.' and in your last post, you mentioned that 'we don't know what
the error message was generated by SQL Server when the records failed to be
written'. I wonder if you could provide the content of this part of the log
that you made this judgement, what made you think that the insertion is
rejected while no error message indicating any abnormal. Any blocking of
locks or any information from you application side? This information is
helpful for our analysis. Second, as I mentioned in my last post, when an
operation is executed, this operation will be write to log but not
necessary to write to .MDB file, when checkpoint come, they will be write
to the MDB file. I think that it is because the 18,000 records' insert have
been written into the log file, but not to the .MDB file, so, when SQL
Server restart, it will compare with the LSN of page and log to decide
roll-forward or roll-back, no difference between, in the SQL Server start
process, no this action is taken, as in your past restart. Besides the log
message, could you please provide the recovery mode of you database?
As the ADO time-out option, I suggest you to set to zero, which prepresent
no limit for time-out.
Looking for your reply and thanks.
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.|||Baisong,
What I meant by 'By examining the application log
file,...' is checking the SQL server tables that the
application is writing to. All the written records
contain a time stamp; therefore I can tell when the
insertion started to fail on these tables.
'we don't know what the error message was generated by SQL
Server when the records failed' simply means that the
application did not log any error returned by the ADO
command object.
The recovery mode that the database uses is 'Full Recovery
Mode'
Mike|||Hi Mike,
Thank you for your update.
Yes, from the time stamps in your table that indicating when the insertion
was inserted, we could figure out that the inserting is stopped. However,
we could this can just provide the information about when the inserting
failure happened. From the error log and other informations collected,
could we figure out the cause of the problem. From the information now I
could have, I doubt that there were blocks and later deadlocks that cause
the insertion stopped and then cause all the insert failed. As I mentioned
in my previous reply, before the deadlock happen, some of the insert is
succeeded and this inserting is logged in the transactional log file, but
not in the data file. Before the checkpoint came, you re-booted the system,
and the SQL Server will also restart. SQL Server will compare the LSN of
data page and the log, then will decide which to roll forward and which to
rolled back. The operations already in the transactional log file will be
rolled forward, such as the 18,000 record in your case.
However, this is just a assumption based on my experience. To judge what
happend at that time, we need the corresponding error log for analysis.
Also, when this problem happened again, we could collect the useful
information by the following command. They are:
1) sp_lock: displaying the active locking information
2) sp_who, sp_who2: displaying the current users and processes information
You could also refer to this part in the SQL Server Books Online:
Troubleshooting Deadlocks
Hope this helps!
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.