Showing posts with label edition. Show all posts
Showing posts with label edition. Show all posts

Sunday, March 25, 2012

Analysis service does not remain started

I have installed SQL Server 2005 Standard Edition for our Team Foundation Server install. I have verified the installation and all seems well, except that the Analysis Services service does not remain started. I get a message like "Some services stop if there is nothing to do." The Analysis service needs to be running in order for the TFS install to succeed. How can I get the Analysis Services service to remain started?

Thanks in Advance

Are you using the autostart parameters during install? The default is to not start these services. Here's the snippet from template.ini:

;--
; To use the *AUTOSTART features, specify 1 to start automatically or 0 to start manually.
; NOTE: If you decide to start SQL Agent automatically, then SQL is also started automatically.
; If *AUTOSTART is not specified on the command line, startup is set to manual.

SQLBROWSERAUTOSTART=0
SQLAUTOSTART=0
AGTAUTOSTART=0
ASAUTOSTART=0
RSAUTOSTART=0

Thanks,
Samuel Lester (MSFT)

|||I didn't use those parameters - I followed the "How To: Install SQL Server 2005 for Team Foundation Server" doc. I installed it all interactively.|||

Since the default is to not start these services, this should be the correct behavior then. Are you checking the box during install to autostart the services?

Thanks,
Sam Lester (MSFT)

|||Yes. The problem is that Team Foundation Server will not install if the Analysis Services service is not running, and it is not. When I start it, it stops immediately.|||

Ah, so after installing SQL, the AS service does not start? I thought you were looking to autostart during install. Can you send the exact error message that you get after starting it? Are there any messages in event viewer? And are you trying to connect with a domain account or with local system?

Thanks,
Sam

sql

Sunday, February 19, 2012

AMD Opteron 64-bit Processors - SQL Server 2000...

I was also wondering if SQL Server 2000 can run on Opteron processors (With
Windows 2003, x64 edition)?
Thanks...Answered in your post a few minutes ago "Windows 2003, x64 edition - SQL
Server 2000"
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"BATMAN" <BATMAN@.discussions.microsoft.com> wrote in message
news:56B87790-EEB4-4888-A08E-CD853C5747F7@.microsoft.com...
>
> I was also wondering if SQL Server 2000 can run on Opteron processors
> (With
> Windows 2003, x64 edition)?
> Thanks...

AMD Opteron 64 & SQL 2000 32 bit

Are there any known issues with the AMD Opteron 200 Series running Windows
2003 Ent. Edition and SQL 2000 Ent in a cluster?
In a few threads I have seen remarks that SP 4 is needed, but in the feature
list of SP4 there is no mention about this.
Thanks,
JanThere's is only a 64 bit version of SQL Server 2000 for the Intel Itanium pr
ocessor. Running 32 bit
SQL Server on WOW (Windows on Windows), where Windows emulates 32 bit on 64
bit HW using the x64
processor architecture and OS wasn't supported until sp4. This link might ha
ve some details:
http://www.microsoft.com/downloads/...&displaylang=en
As for issues, I don't know. I imagine that this isn't a very common setup.
And with SQL Server 2005
out where there exists an x64 version, it might not be a common setup either
?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Jan" <Jan@.discussions.microsoft.com> wrote in message
news:3F4C6DF9-5D21-4F70-AC48-7BF6EE2A14A0@.microsoft.com...
> Are there any known issues with the AMD Opteron 200 Series running Windows
> 2003 Ent. Edition and SQL 2000 Ent in a cluster?
> In a few threads I have seen remarks that SP 4 is needed, but in the featu
re
> list of SP4 there is no mention about this.
> Thanks,
> Jan

AMD Opteron 64 & SQL 2000 32 bit

Are there any known issues with the AMD Opteron 200 Series running Windows
2003 Ent. Edition and SQL 2000 Ent in a cluster?
In a few threads I have seen remarks that SP 4 is needed, but in the feature
list of SP4 there is no mention about this.
Thanks,
Jan
There's is only a 64 bit version of SQL Server 2000 for the Intel Itanium processor. Running 32 bit
SQL Server on WOW (Windows on Windows), where Windows emulates 32 bit on 64 bit HW using the x64
processor architecture and OS wasn't supported until sp4. This link might have some details:
http://www.microsoft.com/downloads/d...displaylang=en
As for issues, I don't know. I imagine that this isn't a very common setup. And with SQL Server 2005
out where there exists an x64 version, it might not be a common setup either?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Jan" <Jan@.discussions.microsoft.com> wrote in message
news:3F4C6DF9-5D21-4F70-AC48-7BF6EE2A14A0@.microsoft.com...
> Are there any known issues with the AMD Opteron 200 Series running Windows
> 2003 Ent. Edition and SQL 2000 Ent in a cluster?
> In a few threads I have seen remarks that SP 4 is needed, but in the feature
> list of SP4 there is no mention about this.
> Thanks,
> Jan

AMD Opteron 64 & SQL 2000 32 bit

Are there any known issues with the AMD Opteron 200 Series running Windows
2003 Ent. Edition and SQL 2000 Ent in a cluster?
In a few threads I have seen remarks that SP 4 is needed, but in the feature
list of SP4 there is no mention about this.
Thanks,
JanThere's is only a 64 bit version of SQL Server 2000 for the Intel Itanium processor. Running 32 bit
SQL Server on WOW (Windows on Windows), where Windows emulates 32 bit on 64 bit HW using the x64
processor architecture and OS wasn't supported until sp4. This link might have some details:
http://www.microsoft.com/downloads/details.aspx?FamilyID=8E2DFC8D-C20E-4446-99A9-B7F0213F8BC5&displaylang=en
As for issues, I don't know. I imagine that this isn't a very common setup. And with SQL Server 2005
out where there exists an x64 version, it might not be a common setup either?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Jan" <Jan@.discussions.microsoft.com> wrote in message
news:3F4C6DF9-5D21-4F70-AC48-7BF6EE2A14A0@.microsoft.com...
> Are there any known issues with the AMD Opteron 200 Series running Windows
> 2003 Ent. Edition and SQL 2000 Ent in a cluster?
> In a few threads I have seen remarks that SP 4 is needed, but in the feature
> list of SP4 there is no mention about this.
> Thanks,
> Jan

Thursday, February 16, 2012

Am I missing something when trying to connect via ASP.NET 2.0?

I am at my wit's end trying to set up a simple test to retrieve some records from with ASP.NET and C#. I'm using the Express Edition on my development laptop. Whenever I try to run my application, I get the following error:

ERROR: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

I have researched this problem, and done everything I can find online to fix it but no avail. I have gone to SQL Server Configuration Manager and enabled Named Pipes and TCP/IP. I have stopped and restarted the server. Local and Remote connections (Both TCP/IP and Named Pipes) are enabled in the Surface Area Configuration. I added it to the Exceptions list of the Windows firewall. And yet nothing works. I can connect to it fine with Management Studio Express, but I am totally unable to connect to the database from within my code. I've spent probably about two weeks wracking my brain trying to figure this out; does anybody know what might be causing the problem and what could fix it?what does your connection string look like.|||"Server=ORPHEUS;Database=TestDB;User ID=sa;Password=mypass;Trusted_connection=False"

I've also tried specifyinig the instance of SQL Server (e.g. Server=ORPHEUS\SQLExpress) but that does not work either.
|||

If you're trying to connect to an instance name, then i'm pretty sure you have to specify it in your connection string.

Have you tried using the examples in the docs, like this one? http://msdn2.microsoft.com/en-us/library/ms247257.aspx

|||Well what do you know... turns out I wasn't specifying it in the right format.. I should have had it was "Database=ORPHEUS\\SQLEXPRESS".

Thanks a ton! Sometimes its the most obvious things that you end up missing...