Clearing LOG Files: couple

Showing posts with label couple. Show all posts

Thursday, March 29, 2012

Cluster SQL 2000 errorlog problem

Tuesday, March 27, 2012

Cluster SQL 2000 errorlog problem

We've recently installed a couple of Windows Server 2003 Ent Ed servers with
SQL 2000 Ent Ed and one of the active/active nodes continually gives the
error below in the Application Event log.
The NT user which was used to install the server and owns the directories
and files below has full rights so this should not be an issue.
I've checked MSDN, etc. but nothing which seems to help.
Thanks.
Ron
--
17050 :
initerrlog: Could not open error log file 'D:\Program Files\Microsoft SQL
Server\MSSQL\log\ERRORLOG'. Operating system error = 3(The system cannot find
the path specified.).
--Ron,
Is drive D local to the server or on the cluster's shared drives? The error
message could be implying that the node in question was installed with the
data files on a local drive.
Hope this helps,
Ron
--
Ron Talmage
SQL Server MVP
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:7BABBA49-964A-4422-ACB8-B559661A5F05@.microsoft.com...
> We've recently installed a couple of Windows Server 2003 Ent Ed servers
with
> SQL 2000 Ent Ed and one of the active/active nodes continually gives the
> error below in the Application Event log.
> The NT user which was used to install the server and owns the directories
> and files below has full rights so this should not be an issue.
> I've checked MSDN, etc. but nothing which seems to help.
> Thanks.
> Ron
> --
> 17050 :
> initerrlog: Could not open error log file 'D:\Program Files\Microsoft SQL
> Server\MSSQL\log\ERRORLOG'. Operating system error = 3(The system cannot
find
> the path specified.).
> --|||BTW, there's a webcast on troubleshooting a SQL Server 2000 cluster install
that contains a lot of detail not available elsewhere:
http://support.microsoft.com/default.aspx?scid=/servicedesks/webcasts/wcd020703/wcdblurb020703.asp
Ron
--
Ron Talmage
SQL Server MVP
"Ron Talmage" <rtalmage@.prospice.com> wrote in message
news:%23c46wJI%23EHA.3368@.TK2MSFTNGP15.phx.gbl...
> Ron,
> Is drive D local to the server or on the cluster's shared drives? The
error
> message could be implying that the node in question was installed with the
> data files on a local drive.
> Hope this helps,
> Ron
> --
> Ron Talmage
> SQL Server MVP
> "Ron" <Ron@.discussions.microsoft.com> wrote in message
> news:7BABBA49-964A-4422-ACB8-B559661A5F05@.microsoft.com...
> > We've recently installed a couple of Windows Server 2003 Ent Ed servers
> with
> > SQL 2000 Ent Ed and one of the active/active nodes continually gives the
> > error below in the Application Event log.
> >
> > The NT user which was used to install the server and owns the
directories
> > and files below has full rights so this should not be an issue.
> >
> > I've checked MSDN, etc. but nothing which seems to help.
> > Thanks.
> > Ron
> >
> > --
> > 17050 :
> > initerrlog: Could not open error log file 'D:\Program Files\Microsoft
SQL
> > Server\MSSQL\log\ERRORLOG'. Operating system error = 3(The system cannot
> find
> > the path specified.).
> >
> > --
>|||Ron,
I'll review the webcast...thanks!
SQL Server is installed on the C: drive, the data files are installed on D:
which is a SAN drive share.
I've rebooted both nodes and only started node1...with node2 offline, there
errors are not appearing in the event logs...? Seems odd as it's node1 which
is logging the errors...any other ideas?
Thanks.
Ron
"Ron Talmage" wrote:
> BTW, there's a webcast on troubleshooting a SQL Server 2000 cluster install
> that contains a lot of detail not available elsewhere:
> http://support.microsoft.com/default.aspx?scid=/servicedesks/webcasts/wcd020703/wcdblurb020703.asp
> Ron
> --
> Ron Talmage
> SQL Server MVP
> "Ron Talmage" <rtalmage@.prospice.com> wrote in message
> news:%23c46wJI%23EHA.3368@.TK2MSFTNGP15.phx.gbl...
> > Ron,
> >
> > Is drive D local to the server or on the cluster's shared drives? The
> error
> > message could be implying that the node in question was installed with the
> > data files on a local drive.
> >
> > Hope this helps,
> > Ron
> > --
> > Ron Talmage
> > SQL Server MVP
> >
> > "Ron" <Ron@.discussions.microsoft.com> wrote in message
> > news:7BABBA49-964A-4422-ACB8-B559661A5F05@.microsoft.com...
> > > We've recently installed a couple of Windows Server 2003 Ent Ed servers
> > with
> > > SQL 2000 Ent Ed and one of the active/active nodes continually gives the
> > > error below in the Application Event log.
> > >
> > > The NT user which was used to install the server and owns the
> directories
> > > and files below has full rights so this should not be an issue.
> > >
> > > I've checked MSDN, etc. but nothing which seems to help.
> > > Thanks.
> > > Ron
> > >
> > > --
> > > 17050 :
> > > initerrlog: Could not open error log file 'D:\Program Files\Microsoft
> SQL
> > > Server\MSSQL\log\ERRORLOG'. Operating system error = 3(The system cannot
> > find
> > > the path specified.).
> > >
> > > --
> >
> >
>
>sql sql

Thursday, March 22, 2012

Cluster Group and SQL Question

We have a cluster that has been running for a couple of years. It has MSDE
running on one node of the cluster. This cluster only has one group on it
and want to install SQL 2005. Would it install into this group? Is it
possible to have more than one group on one device? I was able to get DTC
working so I was thinking I could install SQL.
thanks
Yes, you can install SQL Server 2005 into that cluster. However, the SQL
Server requires its own disk resources that are not shared with anything
else. You can't configure a disk device into multiple groups.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Roger" <roger@.nospam.com> wrote in message
news:%23T7iPR$JGHA.668@.TK2MSFTNGP11.phx.gbl...
> We have a cluster that has been running for a couple of years. It has
> MSDE running on one node of the cluster. This cluster only has one group
> on it and want to install SQL 2005. Would it install into this group?
> Is it possible to have more than one group on one device? I was able to
> get DTC working so I was thinking I could install SQL.
> thanks
>
>
|||Would I have to rebuild the cluster to get another disk device if everything
is allocated now? It was not known at the time when the cluster was built
that we were going to install SQL.
thanks
"Michael Hotek" <mike@.solidqualitylearning.com> wrote in message
news:ecxJngBKGHA.3728@.tk2msftngp13.phx.gbl...
> Yes, you can install SQL Server 2005 into that cluster. However, the SQL
> Server requires its own disk resources that are not shared with anything
> else. You can't configure a disk device into multiple groups.
> --
> Mike
> http://www.solidqualitylearning.com
> Disclaimer: This communication is an original work and represents my sole
> views on the subject. It does not represent the views of any other person
> or entity either by inference or direct reference.
>
> "Roger" <roger@.nospam.com> wrote in message
> news:%23T7iPR$JGHA.668@.TK2MSFTNGP11.phx.gbl...
>
|||No, the cluster doesn't need to be rebuilt. You just have to add the disk
resource into the cluster before you can use it with the failover cluster
instance.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Roger" <roger@.nospam.com> wrote in message
news:%236s%23kwLKGHA.1288@.TK2MSFTNGP09.phx.gbl...
> Would I have to rebuild the cluster to get another disk device if
> everything is allocated now? It was not known at the time when the
> cluster was built that we were going to install SQL.
> thanks
> "Michael Hotek" <mike@.solidqualitylearning.com> wrote in message
> news:ecxJngBKGHA.3728@.tk2msftngp13.phx.gbl...
>
|||Where would I get the disk resource from? I know if I add more disks I can
use that. I have 60 gig free on what I currenly have and I was thinking to
delete and redo the partitions to get what I would need for SQL.
thanks again for your help.
"Michael Hotek" <mike@.solidqualitylearning.com> wrote in message
news:uA7unAvKGHA.3912@.TK2MSFTNGP10.phx.gbl...
> No, the cluster doesn't need to be rebuilt. You just have to add the disk
> resource into the cluster before you can use it with the failover cluster
> instance.
> --
> Mike
> http://www.solidqualitylearning.com
> Disclaimer: This communication is an original work and represents my sole
> views on the subject. It does not represent the views of any other person
> or entity either by inference or direct reference.
>
> "Roger" <roger@.nospam.com> wrote in message
> news:%236s%23kwLKGHA.1288@.TK2MSFTNGP09.phx.gbl...
>

Monday, March 19, 2012

cluster

Hello ,
I have couple of questions on clustering as well as on hardware.
1) Is the license for SQL Server 2005 Enterprise edition ( Production) on
active/active and active/passive is same?
2) Is the license for sql server 2005 is socket based or processor based, is
there any differnce between them.
3) Do we have any figures for SQL Server 2005 performance on single socket
as well as dual socket servers ?
4) If we have a active/active cluster on single socket on quad core
processor , what will be the license as well as performance when compared to
the active/active on dual socket on quad processor?
Any input is appreciated?
Comments Inline
"IT" <IT@.discussions.microsoft.com> wrote in message
news:87B5B6CB-413D-4A12-A4D3-59CDAC0C569A@.microsoft.com...
> Hello ,
> I have couple of questions on clustering as well as on hardware.
> 1) Is the license for SQL Server 2005 Enterprise edition ( Production) on
> active/active and active/passive is same?
Sort of. There is a single-instance or N+1 exception to normal licensing
requirements. If you have a node that is always a standby system, Then it
doesn't have to be licensed for SQL. Two nodes, one instance, one license.
Four nodes, three instances, three licenses.
Also, on two-node clusters, you might look into Standard Edition for
clustering. It's lots cheaper and it does support two-node clusters.

> 2) Is the license for sql server 2005 is socket based or processor based,
> is
> there any differnce between them.
Socket-based. This makes dual and quad core systems very price competitive
from a licensing standpoint.

> 3) Do we have any figures for SQL Server 2005 performance on single socket
> as well as dual socket servers ?
I generally don't trust benchmarks all that much. With SQL, the nature of
the load can vary so much between systems that finding a matching benchmark
is difficult if not impossible. Dual and quad socket systems are commodity
priced so I wouldn't go with a single-socket system except for the very
lowest application. Certainly not for a cluster.

> 4) If we have a active/active cluster on single socket on quad core
> processor , what will be the license as well as performance when compared
> to
> the active/active on dual socket on quad processor?
>
Assuming per-socket licensing, you would need one socket license for the
first and four licenses for the second. CAL licensing (assuming the usage
meets the requirements) would be one server license and N CALS for the first
or two server licenses and N CALs for the second. N being the number of
client users or devices.

> Any input is appreciated?
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
|||Thanks that was helpful....
Is there any KB or white paper describing the same for some documentation...
"Geoff N. Hiten" wrote:

> Comments Inline
> "IT" <IT@.discussions.microsoft.com> wrote in message
> news:87B5B6CB-413D-4A12-A4D3-59CDAC0C569A@.microsoft.com...
> Sort of. There is a single-instance or N+1 exception to normal licensing
> requirements. If you have a node that is always a standby system, Then it
> doesn't have to be licensed for SQL. Two nodes, one instance, one license.
> Four nodes, three instances, three licenses.
> Also, on two-node clusters, you might look into Standard Edition for
> clustering. It's lots cheaper and it does support two-node clusters.
> Socket-based. This makes dual and quad core systems very price competitive
> from a licensing standpoint.
> I generally don't trust benchmarks all that much. With SQL, the nature of
> the load can vary so much between systems that finding a matching benchmark
> is difficult if not impossible. Dual and quad socket systems are commodity
> priced so I wouldn't go with a single-socket system except for the very
> lowest application. Certainly not for a cluster.
> Assuming per-socket licensing, you would need one socket license for the
> first and four licenses for the second. CAL licensing (assuming the usage
> meets the requirements) would be one server license and N CALS for the first
> or two server licenses and N CALs for the second. N being the number of
> client users or devices.
>
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
|||Microsoft SQL Server 2005 Licensing
http://www.microsoft.com/sql/howtobuy/default.mspx#EXE
The links to the white paper and FAQ are very useful
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"IT" <IT@.discussions.microsoft.com> wrote in message
news:8848E76E-646D-4AA9-B7FD-7FCCA6D5DAFE@.microsoft.com...[vbcol=seagreen]
> Thanks that was helpful....
> Is there any KB or white paper describing the same for some
> documentation...
> "Geoff N. Hiten" wrote:

Saturday, February 25, 2012

Cloned SQL 2005 Install

I need a little help with a cloned SQL 2005 install. We have a couple of Virtual Machines that SQL 2005 was installed on. The install was orginally completed on <pc1> and then duped over to <pc2>. The problem now is that <pc2> is showing information from <pc1> everywhere. I have reviewd this document: http://msdn2.microsoft.com/en-us/library/ms143799.aspx, and it doesn't seem to help any. I have used the sp_dropserver command with 'droplogins' to try to recreate the logins for <pc2> but it's still showing the logins from <pc1>. Can someone please help me out, I'm not sure what I'm doing wrong here. Thanks!

Am I looking at a re-install here?

The doc says there is no need to re-install, but those commands just aren't taking care of the problem. When I run @.@.servername it does show the correct server as node 0, but the logins are still there from <pc1>. I deleted the 3 logins that were referenced to the old PC, now I just can't get them re-created for <pc2>

|||What logins are you referring to?

Friday, February 24, 2012

clients sometimes get locked and can't write

I have an SQL 2000 back end. We have a couple of databases with about 12-20
tables a piece. About once or twice a month there are times for up to an
hour or so where no one can write from any of the front end applications to
the SQL 2000 back end. Each application gives their own error which all are
basically a time out waiting to write. Often times the system will just
start working again on its own.
When this happens the first thing we check in the Enterprise Manager is for
any locks and there are none. We then check to see if one of the other
applications like Access 2003, Labview or others can write to the database
and we see they cannot. Next we see if we can open the table on the SQL
server and edit or append and we CAN from the Enterprise Manager?
Thinking that there might be someone locking a record or a page we kick
everyone out and just let one person (sometimes myself as an admin) try to
work and they cannot. We then restart the SQL server and the workstations
and have someone try again and they still fail.
The only thing that I have seen help get it out of this state is when I go
to my daily maintenance jobs and run both my integrity check and my
optimization plan. The Integrety Check plan was done with the wizard and
it:
1. Checks the integrity of all user database
2. Includes indexes
3. Attempts to repair minor problems.
4. Run every day at 12:00 AM
The Optimization plan is set to:
1. Reorganize Data and Index Pages
2. Change free space to 10%
3. Run every day at 1:30 AM
Finally, when I look in the Event Viewer logs for anything strange I really
do not see anything in the app, security, or system logs anywhere near the
time of the start of the errors.
Sounds like the SQL Server Agents for the SQL Server instances aren't
running sometimes. Goto start->administrative tools->services and
look for the SQL Server Agent (your server instance name) entries and
see their status. Should be in "Started" state. If not started,
click on the entry and click start in top left corner of pane.
SQL Server Agents are the programs that act as proxies to enable
remote access to a SQL server instance. If they are not running,
nobody will be able to gain access to the server, and will receive
time out errors instead.
Some programs, such as backups, may stop the agents so they can take a
snapshot of the database. These programs should start the agents as
soon as they are done. If you find the agents in a stopped state in
the next outage, you should try to trace down what program was
executing at the time they were stopped, and check if that program is
configured properly.
|||I don't think it is the agent because the users are able to read the data
remotely. Also, the only maintenance that is done is done at 1-3 AM. This
problem happens randomly mid day.
"Andy" <anedza@.infotek-consulting.com> wrote in message
news:e1159a72-4a2a-449d-a8d7-d22be76d6595@.q78g2000hsh.googlegroups.com...
> Sounds like the SQL Server Agents for the SQL Server instances aren't
> running sometimes. Goto start->administrative tools->services and
> look for the SQL Server Agent (your server instance name) entries and
> see their status. Should be in "Started" state. If not started,
> click on the entry and click start in top left corner of pane.
> SQL Server Agents are the programs that act as proxies to enable
> remote access to a SQL server instance. If they are not running,
> nobody will be able to gain access to the server, and will receive
> time out errors instead.
> Some programs, such as backups, may stop the agents so they can take a
> snapshot of the database. These programs should start the agents as
> soon as they are done. If you find the agents in a stopped state in
> the next outage, you should try to trace down what program was
> executing at the time they were stopped, and check if that program is
> configured properly.
>
>
>

clients sometimes get locked and can't write

I have an SQL 2000 back end. We have a couple of databases with about 12-20
tables a piece. About once or twice a month there are times for up to an
hour or so where no one can write from any of the front end applications to
the SQL 2000 back end. Each application gives their own error which all are
basically a time out waiting to write. Often times the system will just
start working again on its own.
When this happens the first thing we check in the Enterprise Manager is for
any locks and there are none. We then check to see if one of the other
applications like Access 2003, Labview or others can write to the database
and we see they cannot. Next we see if we can open the table on the SQL
server and edit or append and we CAN from the Enterprise Manager'
Thinking that there might be someone locking a record or a page we kick
everyone out and just let one person (sometimes myself as an admin) try to
work and they cannot. We then restart the SQL server and the workstations
and have someone try again and they still fail.
The only thing that I have seen help get it out of this state is when I go
to my daily maintenance jobs and run both my integrity check and my
optimization plan. The Integrety Check plan was done with the wizard and
it:
1. Checks the integrity of all user database
2. Includes indexes
3. Attempts to repair minor problems.
4. Run every day at 12:00 AM
The Optimization plan is set to:
1. Reorganize Data and Index Pages
2. Change free space to 10%
3. Run every day at 1:30 AM
Finally, when I look in the Event Viewer logs for anything strange I really
do not see anything in the app, security, or system logs anywhere near the
time of the start of the errors.Sounds like the SQL Server Agents for the SQL Server instances aren't
running sometimes. Goto start->administrative tools->services and
look for the SQL Server Agent (your server instance name) entries and
see their status. Should be in "Started" state. If not started,
click on the entry and click start in top left corner of pane.
SQL Server Agents are the programs that act as proxies to enable
remote access to a SQL server instance. If they are not running,
nobody will be able to gain access to the server, and will receive
time out errors instead.
Some programs, such as backups, may stop the agents so they can take a
snapshot of the database. These programs should start the agents as
soon as they are done. If you find the agents in a stopped state in
the next outage, you should try to trace down what program was
executing at the time they were stopped, and check if that program is
configured properly.|||I don't think it is the agent because the users are able to read the data
remotely. Also, the only maintenance that is done is done at 1-3 AM. This
problem happens randomly mid day.
"Andy" <anedza@.infotek-consulting.com> wrote in message
news:e1159a72-4a2a-449d-a8d7-d22be76d6595@.q78g2000hsh.googlegroups.com...
> Sounds like the SQL Server Agents for the SQL Server instances aren't
> running sometimes. Goto start->administrative tools->services and
> look for the SQL Server Agent (your server instance name) entries and
> see their status. Should be in "Started" state. If not started,
> click on the entry and click start in top left corner of pane.
> SQL Server Agents are the programs that act as proxies to enable
> remote access to a SQL server instance. If they are not running,
> nobody will be able to gain access to the server, and will receive
> time out errors instead.
> Some programs, such as backups, may stop the agents so they can take a
> snapshot of the database. These programs should start the agents as
> soon as they are done. If you find the agents in a stopped state in
> the next outage, you should try to trace down what program was
> executing at the time they were stopped, and check if that program is
> configured properly.
>
>
>

Thursday, February 16, 2012

Client Render broken after upgrade to Win2K3 Enterprise from Standard

First off, any suggestions are welcome here as we're lost.

We have a farm of 2 Win2k3 (standard) servers that had a couple GB of RAM. We then installed 16GB of RAM and upgraded to Win2k3 Enterprise to handle the upgrade.

Prior to the OS upgrade our reports rendered as expected. Post upgrade, they do not.

Some background on how we render...we open a PDF rendering of a report in a popup via JavaScript.

Also, we have 3 environments running the same code base. The only difference between the 3 is that one environment is the one we upgraded to Win2k3 Enterprise.

Again, any suggestions are much appreciated!

Scott

It would probably be important to note that we're using SQL Server 2005 and SQL RS 2005.|||

Of course, I forgot to add what's probably the biggest key. Only clients have this problem. Let me break that down. We have servers behing a crazy amount of firewall protection. The DB server is NOT on the SQL RS server. The Web server is also a farm, only serving this application.

I think this is the key. I can call the popup report (via the Web app) on any Web server on the farm, and it renders. When I call the report from a client outside of the network, the popup opens and the little green graphic comes up with "Report is being generated". This happens for about 20 seconds, then the graphic and text go away, the status bar says "Done", and there is a solid line at the top of the page...but of course no report (the title of the popup is correct by the way).

Thanks for your time!

Thursday, March 29, 2012

Cluster SQL 2000 errorlog problem

Cluster SQL 2000 errorlog problem

Tuesday, March 27, 2012

Cluster SQL 2000 errorlog problem

Thursday, March 22, 2012

Cluster Group and SQL Question

Monday, March 19, 2012

cluster

Saturday, February 25, 2012

Cloned SQL 2005 Install

Friday, February 24, 2012

clients sometimes get locked and can't write

clients sometimes get locked and can't write

Thursday, February 16, 2012

Client Render broken after upgrade to Win2K3 Enterprise from Standard

Clearing LOG Files

Blog Archive

About Me