isql query output issue: installation

Showing posts with label installation. Show all posts

Wednesday, March 21, 2012

Issues with moving existing single production server setup to a New Cluster installation

According to the documentation the chosen Cluster name and IP address need
to be unused before installing the cluster. The IP address is not a problem,
but it will be a difficult task with the Cluster Name as the business
processes have many scripts, DTS packages, stored procedures and views that
have the production server name hard coded. There are many other servers
involved for updating and transferring data, so there was no way around it
and I would like to keep it that way if possible.
Therefore, my question is how can I reuse the production server name for the
cluster without jeopardising the Cluster installation ?
Hello,
You may need to rename the current production server name "ServerA" to
another name before installing virtual server. After that, you could reuse
the name "ServerA" as the virtual server name.
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||You can't, however there are a lot of workarounds. If you are in an AD/DNS
envorinment, you can create an alias record that points the old name to the
new server. You can also set up a SQL alias on each client, but that is
generally harder.
Geoff N. Hiten
Microsoft SQL Server MVP
"GMG" <nospam@.nospam.com> wrote in message
news:uNQ4jV6dFHA.4060@.TK2MSFTNGP10.phx.gbl...
> According to the documentation the chosen Cluster name and IP address need
> to be unused before installing the cluster. The IP address is not a
> problem,
> but it will be a difficult task with the Cluster Name as the business
> processes have many scripts, DTS packages, stored procedures and views
> that
> have the production server name hard coded. There are many other servers
> involved for updating and transferring data, so there was no way around it
> and I would like to keep it that way if possible.
> Therefore, my question is how can I reuse the production server name for
> the
> cluster without jeopardising the Cluster installation ?
>

Friday, March 9, 2012

Issue with launching Report Builder from client PC's

Hi,

I got a working installation of reporting services 2005 up and running, Im able to create models and launch the Report Builder on the machine on which the server is installed, however if I try and run it from another machine on the network I get an error and Im able to view the following exception.

Following errors were detected during this operation.
* [04 Jul 2005 10:39:34 +01:00] System.Deployment.Application.DeploymentDownloadException (Unknown subtype)
- Failed while downloading http://testserver/ReportServer/ReportBuilder/ReportBuilder.application
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)
at System.Deployment.Application.SystemNetDownloader.DownloadAllFiles()
at System.Deployment.Application.FileDownloader.Download(SubscriptionState subState)
at System.Deployment.Application.DownloadManager.DownloadManifest(Uri& sourceUri, String targetPath, IDownloadNotification notification, DownloadOptions options, ManifestType manifestType, ServerInformation& serverInformation)
at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestDirect(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
at System.Deployment.Application.DownloadManager.DownloadDeploymentManifest(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, IDownloadNotification notification, DownloadOptions options)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
Inner Exception
System.Net.WebException
- The remote server returned an error: (401) Unauthorized.
- Source: System
- Stack trace:
at System.Net.HttpWebRequest.GetResponse()
at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)

Anyone able to help ?The error means that the client does not have the Whidbey CLR installed. You will need to install the Whidbey CLR on each client machine where you want to use report builder.

-Lukasz|||Hi,
I was facing similar problem while accessing Report Manager installed on different system on the network, I was able to get Report Manager menu but can not see contents on Report Server. It was displayed Blank without any exception.

Report Server is installed on http://testsrv/Reports$sql2005.

I changed configuration of Reporting Service on Server , Report Server Configuration Manager > Windows Service Identity> Service account from "Local System" to "Local Services".

I can access Report Manager with contents.

Meanwhile I noticed that Report Builder is not launching on the system which is a different system from the Report Server. As per my understanding, Report Builder is a "End user tool" and will be launched without any upgradation of the system (Different system from server). I am getting prompt for "Open/Save document".
Where as Report Builder is working fine on Server itself.

While opening document, I can see XML contents to access Report Builder.
I am pasting part of that XML file in orange colour,

<?xml version="1.0" encoding="utf-8" ?>

- <asmv1:assembly xsi:schemaLocation="urn:schemas-microsoft-com:asm.v1 assembly.adaptive.xsd" manifestVersion="1.0" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" xmlns="urn:schemas-microsoft-com:asm.v2" xmlns:asmv1="urn:schemas-microsoft-com:asm.v1" xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:xrml="urn:mpeg:mpeg21:2003:01-REL-R-NS" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

- <dependency>

- <dependentAssembly dependencyType="install" allowDelayedBinding="true" codebase="ReportBuilder.exe.manifest" size="7148">

- <hash>

- <dsig:Transforms>

<dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity" />

</dsig:Transforms>

<dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />

<dsig:DigestValue>aAi7VtRySyyvYXiAs4FuFXSiqLA=</dsig:DigestValue>

</hash>

</dependentAssembly>

Anyone knows how to fix this, It is required to upgrade my system, what are the upgrades require on the system to access Report Builder?

|||Your two issues are unrelated. Specifically for the Report Builder issue - the client machine (the one on which you want to run Report Builder) needs to have The .Net Framework 2.0 (CLR 2.0) installed on it.

The reason is that the Report Builder leverages the ClickOnce technology that is new in the .Net Framework 2.0.

Regarding your other issue - the Report Manager shows the top menu with a blank contents when your login does not have permissions on the root of the report server. You will need a role that has Read Properties (Browser roles has this) assigned to your login on the root of the report server namespace. Changing the account from Local System to Local Service should not affect this.

-Lukasz|||Thanks Lukasz, I have installed .NET Framework 2.0 on Client machine and able to launch Report Builder successfully.

I created a new user with sufficient permission and access to HOME directory on Report Server and able to access Reports/Data Sources/Models using Client Machine.

Thanks again!|||

I have what may be a similar problem. I try to click on the "Report Builder" button from a client machine and nothing happens, however I have tried things mentioned in the suggestions above and it did not seem to help. From a client PC, I logged in as myself and am not able to run "Report Builder", but when I login as a local admin I am able to run "Report Builder".

Our server has SQL Server 2005 Enterprise Edition and Visual Studio 2005 installed. I am able to run "Report Builder" from my PC where I had Visual Studio 2005 installed, but not SQL Server 2005 installed. I have local admin priviledges to my PC.

From a client PC, I logged in as myself and am not able to run "Report Builder". When I click on it nothing happens. I gave my Windows login "Content Manger" permissions under the SSRS Home -> Properties tab, and I also added my login and gave myself "System Administrator" and "System User" Roles under the SSRS ->Site Settings->Configure site-wide security option. This seems to be configured correctly, as "Report Builder" launches when I am on my PC. However, it does not launch on the client PC when logged in under my login.

Further, when I login as a local admin on the client PC, I am able to run "Report Builder", so I think the .net framework 2.0 is correctly installed and working properly. However, it is our policy not to give the user of the client PC local admin rights. My windows login does not have local admin rights to this particular PC.

Q1. Is local admin rights required on the client PC where "Report Builder" is ran? If so, is it only required for the first time it is loaded? It seems like it should not be required, however this would explain the symptoms detailed above.

Q2. Is there an error log that may help debug what this problem is? It is strange to me, that nothing happens, but no error is displayed on the http://.../reportserver/Pages page

Q3. When logged in as local admin, report builder installed to something like:

C:\Documents and Settings\Administrator.8ZR5551\Local Settings\Apps\2.0\VVJ0004J.B0N\H3KE16BP.Y07\repo..lder_89845dcd8080cc91_0009.0000_none_7ecce75e919dcccd

I am not sure if I can copy this install to another directory which the client has permission to run from. Is this a valid thing to do? I am guessing probably not since I tried this and it did not seem to work.I tried this and it did not seem to work..

Q4. I saw this posting talking about the need to run under PartialTrust mode, instead of FullTrust mode. So I reconfigured the RSWebApplication.config file to do that, and it still does not work.:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=280387&SiteID=1 which refers to the following link.

http://msdn2.microsoft.com/en-us/library/ms345245.aspx

I changed the C:\Program Files\MSSQL2005\MSSQL.3\Reporting Services\ReportManager\ RSWebApplication.config

From

<Configuration><UI> …

<ReportBuilderTrustLevel> FullTrust </ReportBuilderTrustLevel>

</UI>…</Configuration>

<Configuration><UI> …

<ReportBuilderTrustLevel>PartialTrust</ReportBuilderTrustLevel>

</UI>…</Configuration>

Stopped and restarted report server through reporting services configuration (not sure if I needed to do this) The problem still occurred, however.

|||

Well scratch that idea on local admin rights. Our IT department gave login admin to my windows login (My computer->Manage->System Tools: Local Users and Groups->Administrators) and it still did not work. When I click on "Report Builder" it still does not do anything. I also tried to use it directly at the following URL's and it still did not work, same result of not displaying anything:

http://.../reportserver/ReportBuilder/ReportBuilder.application

http://.../reportserver/ReportBuilder/ReportBuilderLocalIntranet.application

Q5. Is there any Internet Explorer settings that would cause this behavior? I tried disabling popup blocker, but this did not seem to help.

Q6. In the above posting, giving permission on the server HOME directory was required. What directory does this refer to? Does this mean each user of Report Builder needs Windows Directory level security to some directories like C:\Program Files\MSSQL2005\MSSQL.3\Reporting Services\ReportManager\ or others? This does not seem to make sense, but I was unsure which HOME directory was mentioned in the previous posting by Nilesh Trivedi.
.

|||Well this is almost a year old but I am facing the exact same problem as Chad Buher. Clicking on the Report Builder button does nothing, no error, nothing. Can this be caused by some network policy setting?

Issue with Installation SQL 2005

We are running some tests here to evaluate whether to upgrade and switch som
e
of the databases from Oracle to SQL 2005, but running into a major issue.
We have a W2003 server where we used to have SQL 2000 running. We upgraded
that to SQL 2005 server. So far, so good, but the client tool (Management
Studio) doesn't show up in the menu list. Running sqlwb.exe also doesn't
return anything.
However trying to install the client tools gives a friendly that it is
already there, but it isn't. I tried a client install on a laptop which
works, but on the server it gives a problem.
Are you not able to install the client tools on the server?
We tried to remove SQL 2005 from Remove Programs which removes it from the
list, but SQL server remains installed and we have no way to access the
databases.
Hopefully someone can help here, because it isn't anything good on the
perception of the product, while from a functionality perspective the produc
t
looks promising. We tried to install SQL 2005 Standard Edition.
Thanks in advance.
MattTry uninstalling and reinstalling the client tools.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Matt" <Matt@.discussions.microsoft.com> wrote in message
news:DD66D067-60E6-4B2B-8574-1C3DE32A4FFA@.microsoft.com...
> We are running some tests here to evaluate whether to upgrade and switch
> some
> of the databases from Oracle to SQL 2005, but running into a major issue.
> We have a W2003 server where we used to have SQL 2000 running. We upgraded
> that to SQL 2005 server. So far, so good, but the client tool (Management
> Studio) doesn't show up in the menu list. Running sqlwb.exe also doesn't
> return anything.
> However trying to install the client tools gives a friendly that it is
> already there, but it isn't. I tried a client install on a laptop which
> works, but on the server it gives a problem.
> Are you not able to install the client tools on the server?
> We tried to remove SQL 2005 from Remove Programs which removes it from the
> list, but SQL server remains installed and we have no way to access the
> databases.
> Hopefully someone can help here, because it isn't anything good on the
> perception of the product, while from a functionality perspective the
> product
> looks promising. We tried to install SQL 2005 Standard Edition.
> Thanks in advance.
> Matt|||YES, it worked. Thank you!
"Roger Wolter[MSFT]" wrote:

> Try uninstalling and reinstalling the client tools.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Matt" <Matt@.discussions.microsoft.com> wrote in message
> news:DD66D067-60E6-4B2B-8574-1C3DE32A4FFA@.microsoft.com...
>
>

Issue with Installation SQL 2005

We are running some tests here to evaluate whether to upgrade and switch some
of the databases from Oracle to SQL 2005, but running into a major issue.
We have a W2003 server where we used to have SQL 2000 running. We upgraded
that to SQL 2005 server. So far, so good, but the client tool (Management
Studio) doesn't show up in the menu list. Running sqlwb.exe also doesn't
return anything.
However trying to install the client tools gives a friendly that it is
already there, but it isn't. I tried a client install on a laptop which
works, but on the server it gives a problem.
Are you not able to install the client tools on the server?
We tried to remove SQL 2005 from Remove Programs which removes it from the
list, but SQL server remains installed and we have no way to access the
databases.
Hopefully someone can help here, because it isn't anything good on the
perception of the product, while from a functionality perspective the product
looks promising. We tried to install SQL 2005 Standard Edition.
Thanks in advance.
Matt
Try uninstalling and reinstalling the client tools.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Matt" <Matt@.discussions.microsoft.com> wrote in message
news:DD66D067-60E6-4B2B-8574-1C3DE32A4FFA@.microsoft.com...
> We are running some tests here to evaluate whether to upgrade and switch
> some
> of the databases from Oracle to SQL 2005, but running into a major issue.
> We have a W2003 server where we used to have SQL 2000 running. We upgraded
> that to SQL 2005 server. So far, so good, but the client tool (Management
> Studio) doesn't show up in the menu list. Running sqlwb.exe also doesn't
> return anything.
> However trying to install the client tools gives a friendly that it is
> already there, but it isn't. I tried a client install on a laptop which
> works, but on the server it gives a problem.
> Are you not able to install the client tools on the server?
> We tried to remove SQL 2005 from Remove Programs which removes it from the
> list, but SQL server remains installed and we have no way to access the
> databases.
> Hopefully someone can help here, because it isn't anything good on the
> perception of the product, while from a functionality perspective the
> product
> looks promising. We tried to install SQL 2005 Standard Edition.
> Thanks in advance.
> Matt
|||YES, it worked. Thank you!
"Roger Wolter[MSFT]" wrote:

> Try uninstalling and reinstalling the client tools.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Matt" <Matt@.discussions.microsoft.com> wrote in message
> news:DD66D067-60E6-4B2B-8574-1C3DE32A4FFA@.microsoft.com...
>
>

Issue with Installation SQL 2005

We are running some tests here to evaluate whether to upgrade and switch some
of the databases from Oracle to SQL 2005, but running into a major issue.
We have a W2003 server where we used to have SQL 2000 running. We upgraded
that to SQL 2005 server. So far, so good, but the client tool (Management
Studio) doesn't show up in the menu list. Running sqlwb.exe also doesn't
return anything.
However trying to install the client tools gives a friendly that it is
already there, but it isn't. I tried a client install on a laptop which
works, but on the server it gives a problem.
Are you not able to install the client tools on the server?
We tried to remove SQL 2005 from Remove Programs which removes it from the
list, but SQL server remains installed and we have no way to access the
databases.
Hopefully someone can help here, because it isn't anything good on the
perception of the product, while from a functionality perspective the product
looks promising. We tried to install SQL 2005 Standard Edition.
Thanks in advance.
MattTry uninstalling and reinstalling the client tools.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Matt" <Matt@.discussions.microsoft.com> wrote in message
news:DD66D067-60E6-4B2B-8574-1C3DE32A4FFA@.microsoft.com...
> We are running some tests here to evaluate whether to upgrade and switch
> some
> of the databases from Oracle to SQL 2005, but running into a major issue.
> We have a W2003 server where we used to have SQL 2000 running. We upgraded
> that to SQL 2005 server. So far, so good, but the client tool (Management
> Studio) doesn't show up in the menu list. Running sqlwb.exe also doesn't
> return anything.
> However trying to install the client tools gives a friendly that it is
> already there, but it isn't. I tried a client install on a laptop which
> works, but on the server it gives a problem.
> Are you not able to install the client tools on the server?
> We tried to remove SQL 2005 from Remove Programs which removes it from the
> list, but SQL server remains installed and we have no way to access the
> databases.
> Hopefully someone can help here, because it isn't anything good on the
> perception of the product, while from a functionality perspective the
> product
> looks promising. We tried to install SQL 2005 Standard Edition.
> Thanks in advance.
> Matt|||YES, it worked. Thank you!
"Roger Wolter[MSFT]" wrote:
> Try uninstalling and reinstalling the client tools.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Matt" <Matt@.discussions.microsoft.com> wrote in message
> news:DD66D067-60E6-4B2B-8574-1C3DE32A4FFA@.microsoft.com...
> > We are running some tests here to evaluate whether to upgrade and switch
> > some
> > of the databases from Oracle to SQL 2005, but running into a major issue.
> >
> > We have a W2003 server where we used to have SQL 2000 running. We upgraded
> > that to SQL 2005 server. So far, so good, but the client tool (Management
> > Studio) doesn't show up in the menu list. Running sqlwb.exe also doesn't
> > return anything.
> >
> > However trying to install the client tools gives a friendly that it is
> > already there, but it isn't. I tried a client install on a laptop which
> > works, but on the server it gives a problem.
> >
> > Are you not able to install the client tools on the server?
> >
> > We tried to remove SQL 2005 from Remove Programs which removes it from the
> > list, but SQL server remains installed and we have no way to access the
> > databases.
> >
> > Hopefully someone can help here, because it isn't anything good on the
> > perception of the product, while from a functionality perspective the
> > product
> > looks promising. We tried to install SQL 2005 Standard Edition.
> >
> > Thanks in advance.
> >
> > Matt
>
>

Issue with Installation of Service Pack 3a

All,
I successfully ran SQL Server Service Pack 3a on a machine that has two
instances of SQL Server. I ran the service pack against both instances. It
all appeared to run fine and I rebooted.
However, when I run the following select statement in Query Analyser:
select @.@.version
It is showing me:
Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
It is not registering as Microsoft SQL Server 2000 - 8.00.760 to indicate
that the instances are at service pack 3a.
Did my service pack really run successfully? Is this a known issue?
Thanks,
Andrea Wright
andrea.wright@.ips-sendero.comHi Andrea,
The version of sql server you are running is 8.00.818 which is a hotfixed
version of SQL server later than than sp3 (which is version 8.00.760).
Actually the 818 version is coming with the public critical SQL server
security roll up fix MS03-031. I Expect you have installed this SQL server
security fix after you've installed sp3.
Regards,
Jago
"Andrea Wright" wrote:
> All,
> I successfully ran SQL Server Service Pack 3a on a machine that has two
> instances of SQL Server. I ran the service pack against both instances. It
> all appeared to run fine and I rebooted.
> However, when I run the following select statement in Query Analyser:
> select @.@.version
> It is showing me:
> Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
> It is not registering as Microsoft SQL Server 2000 - 8.00.760 to indicate
> that the instances are at service pack 3a.
> Did my service pack really run successfully? Is this a known issue?
> Thanks,
> Andrea Wright
> andrea.wright@.ips-sendero.com
>
>|||Jago,
Thanks for your quick response.
I installed the following in this order:
Hotfix that fixed the security issue and the Slammer virus (Microsoft SQL
Server 2000 - 8.00.679)
Service Pack 3 (not sure of the number this put it at)
Service Pack 3a (Microsoft SQL Server 2000 - 8.00.760)
I did not realize there was another hotfix, and I didn't apply one manually.
Is this one perhaps coming with Windows updates?
Thanks,
Andrea
"Jago" <Jago@.discussions.microsoft.com> wrote in message
news:B676216C-B1D0-4F05-A8A8-213BD997DC76@.microsoft.com...
> Hi Andrea,
> The version of sql server you are running is 8.00.818 which is a hotfixed
> version of SQL server later than than sp3 (which is version 8.00.760).
> Actually the 818 version is coming with the public critical SQL server
> security roll up fix MS03-031. I Expect you have installed this SQL server
> security fix after you've installed sp3.
> Regards,
> Jago
> "Andrea Wright" wrote:
>> All,
>> I successfully ran SQL Server Service Pack 3a on a machine that has two
>> instances of SQL Server. I ran the service pack against both instances.
>> It
>> all appeared to run fine and I rebooted.
>> However, when I run the following select statement in Query Analyser:
>> select @.@.version
>> It is showing me:
>> Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
>> It is not registering as Microsoft SQL Server 2000 - 8.00.760 to indicate
>> that the instances are at service pack 3a.
>> Did my service pack really run successfully? Is this a known issue?
>> Thanks,
>> Andrea Wright
>> andrea.wright@.ips-sendero.com
>>|||Hi Andre,
No was not coming with windows update
Jago
"Andrea Wright" wrote:
> Jago,
> Thanks for your quick response.
> I installed the following in this order:
> Hotfix that fixed the security issue and the Slammer virus (Microsoft SQL
> Server 2000 - 8.00.679)
> Service Pack 3 (not sure of the number this put it at)
> Service Pack 3a (Microsoft SQL Server 2000 - 8.00.760)
> I did not realize there was another hotfix, and I didn't apply one manually.
> Is this one perhaps coming with Windows updates?
> Thanks,
> Andrea
> "Jago" <Jago@.discussions.microsoft.com> wrote in message
> news:B676216C-B1D0-4F05-A8A8-213BD997DC76@.microsoft.com...
> > Hi Andrea,
> >
> > The version of sql server you are running is 8.00.818 which is a hotfixed
> > version of SQL server later than than sp3 (which is version 8.00.760).
> > Actually the 818 version is coming with the public critical SQL server
> > security roll up fix MS03-031. I Expect you have installed this SQL server
> > security fix after you've installed sp3.
> >
> > Regards,
> >
> > Jago
> >
> > "Andrea Wright" wrote:
> >
> >> All,
> >>
> >> I successfully ran SQL Server Service Pack 3a on a machine that has two
> >> instances of SQL Server. I ran the service pack against both instances.
> >> It
> >> all appeared to run fine and I rebooted.
> >>
> >> However, when I run the following select statement in Query Analyser:
> >> select @.@.version
> >>
> >> It is showing me:
> >> Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
> >>
> >> It is not registering as Microsoft SQL Server 2000 - 8.00.760 to indicate
> >> that the instances are at service pack 3a.
> >>
> >> Did my service pack really run successfully? Is this a known issue?
> >>
> >> Thanks,
> >> Andrea Wright
> >> andrea.wright@.ips-sendero.com
> >>
> >>
> >>
>
>|||To confirm whether you are on SP3a, run the following command.
select serverproperty('productLevel')
Andrea Wright wrote:
> All,
> I successfully ran SQL Server Service Pack 3a on a machine that has two
> instances of SQL Server. I ran the service pack against both instances. It
> all appeared to run fine and I rebooted.
> However, when I run the following select statement in Query Analyser:
> select @.@.version
> It is showing me:
> Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
> It is not registering as Microsoft SQL Server 2000 - 8.00.760 to indicate
> that the instances are at service pack 3a.
> Did my service pack really run successfully? Is this a known issue?
> Thanks,
> Andrea Wright
> andrea.wright@.ips-sendero.com
>|||"Jonathan Yong" <jyong@.someplace.net> wrote in message
news:eP150unsEHA.624@.TK2MSFTNGP09.phx.gbl...
> To confirm whether you are on SP3a, run the following command.
> select serverproperty('productLevel')
And it should return... ? I "thought" I had SP3a - I definitely applied it
and received no errors. But I just ran this and it returns "SP3". When I
select @.@.version, I get 8.00.760.
>
> Andrea Wright wrote:
> > All,
> >
> > I successfully ran SQL Server Service Pack 3a on a machine that has two
> > instances of SQL Server. I ran the service pack against both instances.
It
> > all appeared to run fine and I rebooted.
> >
> > However, when I run the following select statement in Query Analyser:
> > select @.@.version
> >
> > It is showing me:
> > Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
> >
> > It is not registering as Microsoft SQL Server 2000 - 8.00.760 to
indicate
> > that the instances are at service pack 3a.
> >
> > Did my service pack really run successfully? Is this a known issue?
> >
> > Thanks,
> > Andrea Wright
> > andrea.wright@.ips-sendero.com
> >
> >|||Mine says SP3 as well - the a is missing...
-- Andrea
"Ron Hinds" <__NoSpam@.__NoSpamramac.com> wrote in message
news:ug0$JutsEHA.3320@.TK2MSFTNGP15.phx.gbl...
> "Jonathan Yong" <jyong@.someplace.net> wrote in message
> news:eP150unsEHA.624@.TK2MSFTNGP09.phx.gbl...
>> To confirm whether you are on SP3a, run the following command.
>> select serverproperty('productLevel')
> And it should return... ? I "thought" I had SP3a - I definitely applied it
> and received no errors. But I just ran this and it returns "SP3". When I
> select @.@.version, I get 8.00.760.
>>
>> Andrea Wright wrote:
>> > All,
>> >
>> > I successfully ran SQL Server Service Pack 3a on a machine that has two
>> > instances of SQL Server. I ran the service pack against both
>> > instances.
> It
>> > all appeared to run fine and I rebooted.
>> >
>> > However, when I run the following select statement in Query Analyser:
>> > select @.@.version
>> >
>> > It is showing me:
>> > Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
>> >
>> > It is not registering as Microsoft SQL Server 2000 - 8.00.760 to
> indicate
>> > that the instances are at service pack 3a.
>> >
>> > Did my service pack really run successfully? Is this a known issue?
>> >
>> > Thanks,
>> > Andrea Wright
>> > andrea.wright@.ips-sendero.com
>> >
>> >
>|||AFIK, SQL Server doesn't differentiate between SP 3 and SP 3a with Select
@.@.version or any other method in the database itself. You can look in the
registry for the correct version. If you're running SQL Server, run regedit
and locate HKLM\Software\Microsoft\MSSQLServer\MSSQLServer\CurrentVersion.
Then look at the CSDVersion value. It should be 8.00.761 for SP 3a,
8.00.760 for SP 3. There's also a file or two you can check for version
info in Windows Explorer, but I don't remember which ones off the top of my
head.
Thanks,
Michael C., MCDBA
"Andrea Wright" <andrea.wright@.ips-sendero.com#nospam> wrote in message
news:%23XbgujRtEHA.1040@.TK2MSFTNGP10.phx.gbl...
> Mine says SP3 as well - the a is missing...
> -- Andrea
> "Ron Hinds" <__NoSpam@.__NoSpamramac.com> wrote in message
> news:ug0$JutsEHA.3320@.TK2MSFTNGP15.phx.gbl...
>> "Jonathan Yong" <jyong@.someplace.net> wrote in message
>> news:eP150unsEHA.624@.TK2MSFTNGP09.phx.gbl...
>> To confirm whether you are on SP3a, run the following command.
>> select serverproperty('productLevel')
>> And it should return... ? I "thought" I had SP3a - I definitely applied
>> it
>> and received no errors. But I just ran this and it returns "SP3". When I
>> select @.@.version, I get 8.00.760.
>>
>>
>> Andrea Wright wrote:
>> > All,
>> >
>> > I successfully ran SQL Server Service Pack 3a on a machine that has
>> > two
>> > instances of SQL Server. I ran the service pack against both
>> > instances.
>> It
>> > all appeared to run fine and I rebooted.
>> >
>> > However, when I run the following select statement in Query Analyser:
>> > select @.@.version
>> >
>> > It is showing me:
>> > Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
>> >
>> > It is not registering as Microsoft SQL Server 2000 - 8.00.760 to
>> indicate
>> > that the instances are at service pack 3a.
>> >
>> > Did my service pack really run successfully? Is this a known issue?
>> >
>> > Thanks,
>> > Andrea Wright
>> > andrea.wright@.ips-sendero.com
>> >
>> >
>>
>

Issue with Installation of Service Pack 3a

Friday, February 24, 2012

Issue installing SQL 2000 Enterprise

I need some help, I am attempting to install SQL 2k Enterprise and nothing is happening. When I attempt to start the installation again, I get a message of "Another instance is already running."

Can anyone help me with this? I need to have this installed tonight for work I need to do tomorrow.

Thanks

the error message says that Setp/Autorun is already running. What is the OS on this box. You need to have server version to install Enterprise Edition of SQL Server. If the os is not Server version(windows 2000 server/2003/NT) you can only install Client tool

Madhu

|||

I faced this type of issue before because the installation was aborted in the middle abnormally. And when i started it again it said another instance is already running. But after restarting the server it was thru.

Not sure if that is the same case with you...

Issue installing SQL 2000 Enterprise

I need some help, I am attempting to install SQL 2k Enterprise and nothing is happening. When I attempt to start the installation again, I get a message of "Another instance is already running."

Can anyone help me with this? I need to have this installed tonight for work I need to do tomorrow.

Thanks

Madhu

|||

Not sure if that is the same case with you...

Wednesday, March 21, 2012

Issues with moving existing single production server setup to a New Cluster installation

Friday, March 9, 2012

Issue with launching Report Builder from client PC's

Issue with Installation SQL 2005

Issue with Installation SQL 2005

Issue with Installation SQL 2005

Issue with Installation of Service Pack 3a

Issue with Installation of Service Pack 3a

Issue with Installation of Service Pack 3a

Friday, February 24, 2012

Issue installing SQL 2000 Enterprise

Issue installing SQL 2000 Enterprise

isql query output issue

Blog Archive

About Me