Showing posts with label network. Show all posts
Showing posts with label network. Show all posts

Monday, March 12, 2012

Quagmire situation (Database or Network)

I am here in a peculiar situtation i am not very sure the problem which i am facing as of know is a Database or Network.

One of our organisation application is connected to SQLServer 2005 (clustered) database was working fine before few days back we gone though a windows 2003 server patch update activity and server was restarted and a failover occured.

The day patch activity is done we are facing data loss problem over the network.

Checked the SQLServer2005 ErrorLog but no error related to database.

Few user are facing problem as mentioned below

Error : Checknetwork Documentation

Search the net but no satisfactory answer.

Please help me with a resolution or work around.

One more Issue :

While pinging the server some time we get request Time out.This Request time out is for 1 ms.

Do this also effects the thick client application connectivity with the Database.

regards

Sufian

There are all sorts of network issues surrounding 2003 patches.

I have experienced similar problems with 2003 patches and upgrades.

If you are getting timeouts on a ping, it's a network issue.

Friday, March 9, 2012

QFE 859

We are attempting to install SQL Reporting Services using a network service
account for the ReportServer service. This configuration will fail without
installing QFE 859. There is allegedly a hotfix installer which will apply
the necessary hotfix, but the Microsoft KB articles go in circles without
ever offering a download.
Does anyone know where to download this hotfix and/or why Microsoft has
chosen to hide it so carefully?
The links I'm directed to are: http://support.microsoft.com/?id=821334 and
http://support.microsoft.com/kb/330391/I noticed this myself awhile back. I think what has happened is that they
pulled it because SP4 was out. SP4 is cumulative so it should work for you
(of course SP4 has a problem that requires a hotfix if you have more than 2
Gig of RAM and AWE enabled).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Lowell Williams" <Lowell Williams@.discussions.microsoft.com> wrote in
message news:2DC69A07-1D0F-48D6-BE42-773B8029219B@.microsoft.com...
> We are attempting to install SQL Reporting Services using a network
> service
> account for the ReportServer service. This configuration will fail
> without
> installing QFE 859. There is allegedly a hotfix installer which will
> apply
> the necessary hotfix, but the Microsoft KB articles go in circles without
> ever offering a download.
> Does anyone know where to download this hotfix and/or why Microsoft has
> chosen to hide it so carefully?
> The links I'm directed to are: http://support.microsoft.com/?id=821334
> and
> http://support.microsoft.com/kb/330391/|||Thanks for the reply, Bruce.
Unfortunately, we're not ready to go down the SP4 road yet. It boggles the
mind that a hotfix would be pulled when there are so many different
configurations out there.
I suppose we'll have to use a domain account if the original hotfix file
really is unavailable.
Any other suggestions are appreciated.
"Bruce L-C [MVP]" wrote:
> I noticed this myself awhile back. I think what has happened is that they
> pulled it because SP4 was out. SP4 is cumulative so it should work for you
> (of course SP4 has a problem that requires a hotfix if you have more than 2
> Gig of RAM and AWE enabled).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Lowell Williams" <Lowell Williams@.discussions.microsoft.com> wrote in
> message news:2DC69A07-1D0F-48D6-BE42-773B8029219B@.microsoft.com...
> > We are attempting to install SQL Reporting Services using a network
> > service
> > account for the ReportServer service. This configuration will fail
> > without
> > installing QFE 859. There is allegedly a hotfix installer which will
> > apply
> > the necessary hotfix, but the Microsoft KB articles go in circles without
> > ever offering a download.
> >
> > Does anyone know where to download this hotfix and/or why Microsoft has
> > chosen to hide it so carefully?
> >
> > The links I'm directed to are: http://support.microsoft.com/?id=821334
> > and
> > http://support.microsoft.com/kb/330391/
>
>|||You could also call support. It should be a free call.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Lowell Williams" <LowellWilliams@.discussions.microsoft.com> wrote in
message news:33ECDA63-BCB5-4469-9E81-9EEBAAB6E22C@.microsoft.com...
> Thanks for the reply, Bruce.
> Unfortunately, we're not ready to go down the SP4 road yet. It boggles
> the
> mind that a hotfix would be pulled when there are so many different
> configurations out there.
> I suppose we'll have to use a domain account if the original hotfix file
> really is unavailable.
> Any other suggestions are appreciated.
> "Bruce L-C [MVP]" wrote:
>> I noticed this myself awhile back. I think what has happened is that they
>> pulled it because SP4 was out. SP4 is cumulative so it should work for
>> you
>> (of course SP4 has a problem that requires a hotfix if you have more than
>> 2
>> Gig of RAM and AWE enabled).
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "Lowell Williams" <Lowell Williams@.discussions.microsoft.com> wrote in
>> message news:2DC69A07-1D0F-48D6-BE42-773B8029219B@.microsoft.com...
>> > We are attempting to install SQL Reporting Services using a network
>> > service
>> > account for the ReportServer service. This configuration will fail
>> > without
>> > installing QFE 859. There is allegedly a hotfix installer which will
>> > apply
>> > the necessary hotfix, but the Microsoft KB articles go in circles
>> > without
>> > ever offering a download.
>> >
>> > Does anyone know where to download this hotfix and/or why Microsoft has
>> > chosen to hide it so carefully?
>> >
>> > The links I'm directed to are: http://support.microsoft.com/?id=821334
>> > and
>> > http://support.microsoft.com/kb/330391/
>>|||Did you get it resolved? Did you have to call? We have the identical
problem here.
"Lowell Williams" wrote:
> We are attempting to install SQL Reporting Services using a network service
> account for the ReportServer service. This configuration will fail without
> installing QFE 859. There is allegedly a hotfix installer which will apply
> the necessary hotfix, but the Microsoft KB articles go in circles without
> ever offering a download.
> Does anyone know where to download this hotfix and/or why Microsoft has
> chosen to hide it so carefully?
> The links I'm directed to are: http://support.microsoft.com/?id=821334 and
> http://support.microsoft.com/kb/330391/|||My guess is that this is part of Windows 2003 SP1. If you install SP1 you
should not need the hotfix. If you do not want to install SP1 then I would
think you need to contact support to get the hotfix.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Rob" <Rob@.discussions.microsoft.com> wrote in message
news:95CA7B1D-AAC1-45E4-9E8C-6687586B1BDC@.microsoft.com...
> Did you get it resolved? Did you have to call? We have the identical
> problem here.
>
> "Lowell Williams" wrote:
>> We are attempting to install SQL Reporting Services using a network
>> service
>> account for the ReportServer service. This configuration will fail
>> without
>> installing QFE 859. There is allegedly a hotfix installer which will
>> apply
>> the necessary hotfix, but the Microsoft KB articles go in circles without
>> ever offering a download.
>> Does anyone know where to download this hotfix and/or why Microsoft has
>> chosen to hide it so carefully?
>> The links I'm directed to are: http://support.microsoft.com/?id=821334
>> and
>> http://support.microsoft.com/kb/330391/|||We got it resolved by installing the patch, but to get it we did an end run
by having a Microsoft Partner call in to get it. I believe it took him about
five phone calls.
We started with the 800 number for partner support and went from there.
Make sure you have details available when you call in. I assume the regular
support number should get you there, and since a hotfix will solve your
problem, there should be no charge for the call (I think). Have KB article#
references from my original post, your SQL license and patch level, your
Server versions, etc. all at your fingertips when you call.
I've pasted part of the link they sent us for the patch below which might
help MS support figure out what you want. It has an expiring password on
it, so it won't help you to d/l it now... They also hinted that the patch
was customized to particular environments, and that they had to "configure"
it for us.
It was a little difficult to get them to realize what patch we wanted until
they finally transferred us to the SQL group.
"Bug470536/873/free/150452_ENU_i386_zip.exe"
Hope this helps, and good luck!
Lowell
"Rob" wrote:
> Did you get it resolved? Did you have to call? We have the identical
> problem here.
>
> "Lowell Williams" wrote:
> > We are attempting to install SQL Reporting Services using a network service
> > account for the ReportServer service. This configuration will fail without
> > installing QFE 859. There is allegedly a hotfix installer which will apply
> > the necessary hotfix, but the Microsoft KB articles go in circles without
> > ever offering a download.
> >
> > Does anyone know where to download this hotfix and/or why Microsoft has
> > chosen to hide it so carefully?
> >
> > The links I'm directed to are: http://support.microsoft.com/?id=821334 and
> > http://support.microsoft.com/kb/330391/|||I forgot to mention that there are two versions of this hotfix. You'll want
to verify with Microsoft which version you need.
The two files are called:
SQL2000-KB810185-8.00.0873-ENU.exe
SQL2000-KB884856-v8.00.0977-x86-ENU.exe
Those embedded KB articles should be of help when calling, too.
"Rob" wrote:
> Did you get it resolved? Did you have to call? We have the identical
> problem here.
>
> "Lowell Williams" wrote:
> > We are attempting to install SQL Reporting Services using a network service
> > account for the ReportServer service. This configuration will fail without
> > installing QFE 859. There is allegedly a hotfix installer which will apply
> > the necessary hotfix, but the Microsoft KB articles go in circles without
> > ever offering a download.
> >
> > Does anyone know where to download this hotfix and/or why Microsoft has
> > chosen to hide it so carefully?
> >
> > The links I'm directed to are: http://support.microsoft.com/?id=821334 and
> > http://support.microsoft.com/kb/330391/|||Thanks for all your help. I ended up installing SP4 and that also resolved
the issue.
"Lowell Williams" wrote:
> I forgot to mention that there are two versions of this hotfix. You'll want
> to verify with Microsoft which version you need.
>
> The two files are called:
> SQL2000-KB810185-8.00.0873-ENU.exe
> SQL2000-KB884856-v8.00.0977-x86-ENU.exe
> Those embedded KB articles should be of help when calling, too.
> "Rob" wrote:
> > Did you get it resolved? Did you have to call? We have the identical
> > problem here.
> >
> >
> > "Lowell Williams" wrote:
> >
> > > We are attempting to install SQL Reporting Services using a network service
> > > account for the ReportServer service. This configuration will fail without
> > > installing QFE 859. There is allegedly a hotfix installer which will apply
> > > the necessary hotfix, but the Microsoft KB articles go in circles without
> > > ever offering a download.
> > >
> > > Does anyone know where to download this hotfix and/or why Microsoft has
> > > chosen to hide it so carefully?
> > >
> > > The links I'm directed to are: http://support.microsoft.com/?id=821334 and
> > > http://support.microsoft.com/kb/330391/

QA green button grayed out

I'm running QA on my local PC and going through an ODBC
connection, I've been able to connect to SQL servers on
our network and execute TSQL statements.
Suddenly, last week, the green button is grayed out. No
matter what server. Everything else looks ok. All
features in EM seem to work. In QA, I can connect to the
correct DB and that seems ok. I can type in a command.
But, no green execute button!
I'm running SQL 2000 on my PC. I'm attaching to SQL 2000
and SQL 7.0 servers. The local OS is XP.
Any ideas?
Thanks,
DonHi
And does Ctrl+E work?
John
"Don" <ddachner@.hotmail.com> wrote in message
news:00ad01c3cfd7$463e4470$a501280a@.phx.gbl...
> I'm running QA on my local PC and going through an ODBC
> connection, I've been able to connect to SQL servers on
> our network and execute TSQL statements.
> Suddenly, last week, the green button is grayed out. No
> matter what server. Everything else looks ok. All
> features in EM seem to work. In QA, I can connect to the
> correct DB and that seems ok. I can type in a command.
> But, no green execute button!
> I'm running SQL 2000 on my PC. I'm attaching to SQL 2000
> and SQL 7.0 servers. The local OS is XP.
> Any ideas?
> Thanks,
> Don
>

Monday, February 20, 2012

Q: restrict other users

Hello,
I need to restrict other users to modify database including network
administrator. I go to permission tab and remove all checks and set
everything for my user but it seem administrator still have ability to modify
it.
How can I get only one user do everything and the rest have only read access?
Thanks,
Jim."JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
news:ADF936CE-5020-4CE0-A5E9-8C0EE086069C@.microsoft.com...
> Hello,
> I need to restrict other users to modify database including network
> administrator. I go to permission tab and remove all checks and set
> everything for my user but it seem administrator still have ability to
modify
> it.
> How can I get only one user do everything and the rest have only read
access?
> Thanks,
> Jim.
By default the BUILTIN\Administrators group is mapped to the sysadmin fixed
server role. To prevent this, first ensure that your user is mapped to the
sysadmin role, then either delete the admistrators login (stop them logging
in), or remove it from the sysadmin role. If everyone needs read access
then grant the appropriate permissions to the public role.
http://snodland.blogspot.com
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.788 / Virus Database: 533 - Release Date: 01/11/2004