Showing posts with label connect. Show all posts
Showing posts with label connect. Show all posts

Thursday, March 8, 2012

Another licensing question

I have a software (weblogic) that users (I have 2500 users) connect to.
Behind Weblogic I run a SQL 2000 server standard edition.
It is only Weblogic that connects to SQL (require 5 connections)
My question is, I was told to buy a SQL processor license instead of a User
or Device CAL?
Why spend 15000$ for a processor license when I can only get 5 CALS ?
Thanks for any help
JP
JP Breton wrote:
> I have a software (weblogic) that users (I have 2500 users) connect
> to.
> Behind Weblogic I run a SQL 2000 server standard edition.
> It is only Weblogic that connects to SQL (require 5 connections)
> My question is, I was told to buy a SQL processor license instead of
> a User or Device CAL?
> Why spend 15000$ for a processor license when I can only get 5 CALS ?
> Thanks for any help
> JP
Q. How do I license SQL Server 2000 CALs in a multiplexed
environment?
A. In most cases Microsoft requires a CAL for every device that
accesses or uses the services of SQL Server 2000. If you are unsure
whether a CAL is required, you should contact your Microsoft sales
representative or account manager. Inquires can be directed to Microsoft
Licensing by calling (800)426-9400.
David Gugick
Quest Software
www.imceda.com
www.quest.com

Another licensing question

I have a software (weblogic) that users (I have 2500 users) connect to.
Behind Weblogic I run a SQL 2000 server standard edition.
It is only Weblogic that connects to SQL (require 5 connections)
My question is, I was told to buy a SQL processor license instead of a User
or Device CAL?
Why spend 15000$ for a processor license when I can only get 5 CALS '
Thanks for any help
JPJP Breton wrote:
> I have a software (weblogic) that users (I have 2500 users) connect
> to.
> Behind Weblogic I run a SQL 2000 server standard edition.
> It is only Weblogic that connects to SQL (require 5 connections)
> My question is, I was told to buy a SQL processor license instead of
> a User or Device CAL?
> Why spend 15000$ for a processor license when I can only get 5 CALS '
> Thanks for any help
> JP
Q. How do I license SQL Server 2000 CALs in a multiplexed
environment?
A. In most cases Microsoft requires a CAL for every device that
accesses or uses the services of SQL Server 2000. If you are unsure
whether a CAL is required, you should contact your Microsoft sales
representative or account manager. Inquires can be directed to Microsoft
Licensing by calling (800)426-9400.
David Gugick
Quest Software
www.imceda.com
www.quest.com

Another licensing question

I have a software (weblogic) that users (I have 2500 users) connect to.
Behind Weblogic I run a SQL 2000 server standard edition.
It is only Weblogic that connects to SQL (require 5 connections)
My question is, I was told to buy a SQL processor license instead of a User
or Device CAL?
Why spend 15000$ for a processor license when I can only get 5 CALS '
Thanks for any help
JPJP Breton wrote:
> I have a software (weblogic) that users (I have 2500 users) connect
> to.
> Behind Weblogic I run a SQL 2000 server standard edition.
> It is only Weblogic that connects to SQL (require 5 connections)
> My question is, I was told to buy a SQL processor license instead of
> a User or Device CAL?
> Why spend 15000$ for a processor license when I can only get 5 CALS '
> Thanks for any help
> JP
Q. How do I license SQL Server 2000 CALs in a multiplexed
environment?
A. In most cases Microsoft requires a CAL for every device that
accesses or uses the services of SQL Server 2000. If you are unsure
whether a CAL is required, you should contact your Microsoft sales
representative or account manager. Inquires can be directed to Microsoft
Licensing by calling (800)426-9400.
David Gugick
Quest Software
www.imceda.com
www.quest.com

Another issue with Linked Server

http://support.microsoft.com/?id=814398
I read this article. Maybe Im just plain dumb, but I get this error when I
try to connect to a Linked Access database via sql server. Now the article
states to login using the SQL Server start up account. Im assuming that this
account is the one thats stated in the MSSQLSERVER service under the LogOn
tab.
Well, if it is, then the logon account is "system" in my case. And I cant
physically login to the computer as system now can I?
How difficult can it be to create a linked server to a access database thats
password protected?
Girish
Hi Girish,
From your descriptions, I understood you would like to link an secured
Access mdb file as Linked Server in SQL Server. Have I understood you? If
there is anything misunderstood, please feel free to let me know.
First of all, I would like to answer the question what "system" is. If you
see "System" is selected in LogOn tab of MSSQLServer service, it means
MSSQLServer is started by the account you start Windows. For example,
assuming you are login as "Girish" in you Windows 2003 (or other Windows
Operation System) and "Girish" is in Administartor Group of Windows 2003,
your SQL Server is started as "Girish".
Secondly, I am not sure you encounter exactly the scenario KB:814398
described. Based on my scope, I think the following documents will be
helpful for you.
HOWTO: Use a SQL Server 7.0 Distributed Query with a Linked Server to
Secured Access Databases
http://support.microsoft.com/default...;en-us;Q246255
You receive a "Could not find installable ISAM" error message or some file
types are missing when you import files, export files, or link files in
Access 2000
http://support.microsoft.com/default...;EN-US;Q209805
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||Thanks for your reply.
What does SQL Server use to logon to if I do not login interactively?
Its a service so must still run all the time right?
Girish
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:VbRBzDZhEHA.2632@.cpmsftngxa10.phx.gbl...
> Hi Girish,
> From your descriptions, I understood you would like to link an secured
> Access mdb file as Linked Server in SQL Server. Have I understood you? If
> there is anything misunderstood, please feel free to let me know.
> First of all, I would like to answer the question what "system" is. If you
> see "System" is selected in LogOn tab of MSSQLServer service, it means
> MSSQLServer is started by the account you start Windows. For example,
> assuming you are login as "Girish" in you Windows 2003 (or other Windows
> Operation System) and "Girish" is in Administartor Group of Windows 2003,
> your SQL Server is started as "Girish".
> Secondly, I am not sure you encounter exactly the scenario KB:814398
> described. Based on my scope, I think the following documents will be
> helpful for you.
> HOWTO: Use a SQL Server 7.0 Distributed Query with a Linked Server to
> Secured Access Databases
> http://support.microsoft.com/default...;en-us;Q246255
> You receive a "Could not find installable ISAM" error message or some file
> types are missing when you import files, export files, or link files in
> Access 2000
> http://support.microsoft.com/default...;EN-US;Q209805
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
|||Hi Girish,
MSSQLServer is run as a background services, you could also make it started
automatically or manually. In General Tab of MSSQLServer, you could change
"Startup type" between Automatic, Manual and Disable, while you could click
the button under Serivce status to make it start, stop and pause (resume).
If you choose Manual, MSSQLServer will be started only after you click the
"start" button, if Automatic is choosen, MSSQLServer will be started every
time Windows started up.
Additional, we could also use DOS-prompt to start/stop a service like
MSSQLServer. For example, "net start mssqlserver" or "net stop mssqlserver"
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||My mistake... I didnt mean "how" does it start up...
I meant.. when it starts up automatically, what account does it use to login
if I choose "system" and Im NOT interactively logged into the computer.
Im getting confused because my MSSQLServer does run in the background... and
Ive choosen it to login as system... and you said in an earlier email that
system means; if I LOGIN as Girish, then system = Girish. If I login as XYZ,
then system = XYZ.
Now my Q is; if I DONT login at all and MSSQLServer is automatic and a
background service and is set to login as system; then system = ?
Girish
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:cagdUwchEHA.2632@.cpmsftngxa10.phx.gbl...
> Hi Girish,
> MSSQLServer is run as a background services, you could also make it
started
> automatically or manually. In General Tab of MSSQLServer, you could change
> "Startup type" between Automatic, Manual and Disable, while you could
click
> the button under Serivce status to make it start, stop and pause (resume).
> If you choose Manual, MSSQLServer will be started only after you click the
> "start" button, if Automatic is choosen, MSSQLServer will be started every
> time Windows started up.
> Additional, we could also use DOS-prompt to start/stop a service like
> MSSQLServer. For example, "net start mssqlserver" or "net stop
mssqlserver"
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
|||Hi Girish,
I feel sorry for my poor understanding, thanks for your kindest
explaination.
If MSSQLServer is selected to be started as Local System account, it will
be started as NT AUTHORITH\SYSTEM. This account is internal and invisable
no matter what username you choosed to login.
Here are some descriptions fro BOL, which I think will be helpful
explaining it
The local system account does not require a password, does not have network
access rights in Windows NT 4.0, and may restrict your SQL Server
installation from interacting with other servers.
Note In Windows 2000, the local system account does allow network access.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||Hi Girish,
I am just checking on your progress regarding the information that was sent
you! If you encounter any difficulty, please do not hesitate to let me
know. Please post here and let me know the status of your issue. Without
your further information, it's very hard for me to continue with the
troubleshooting.
Looking forward to hearing from you soon. Thank you for your patience and
cooperation.
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

Wednesday, March 7, 2012

Another - Cannot connect to Database Issue.

I've read several issues and resolutions related to my problem, but none of the resolutions have worked.

I have Visual Studio 2005 installed on my local machine.

My SQL Server 2005 is on a Member Server.

On a fresh Web application, I have no problem accessing the ASP.NET Configuration File to set up Users and Roles. The reason is obvious, the data is in SQLExpress and Local. You can see the database ASPNETDB.MDF residing under the App_Data Folder of the project.

How do I get this in the SQL Server 2005 System on the Member server?

Whenever I do the Copy Web Site procedure to post my application to the Web Server, I get an error stating that SQLExpress is not installed on the target server. That's correct because my target server has SQL 2005.

I've tried changing the Machine.Config. I've tried changing the Web.Config. Neither solution was successful. Both send me errors that no connection can be made.

I've also seen various recommendations concerning the ASPNET database. One camp says store your members and roles in the same database as your Data. The other camp says keep them seperate. Is there a rhyme or reason for either one? The data housed in this Database is what I'm after but how in the world to I get there?

I am on week #4 trying to get something going. I'm starting to feel like Thomas Edison when he said he discovered 900 different ways his experiment did not work.

Hi,

you will have to copy the database to the remote server, attach it on the (non SQL Server Express) system using the GUI or sp_attachdb. THen you will have to change the connectionstring not to use the UserInstance anymore (because you now will have the instance connected to a server instance rather than a user instance).

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||

OK. For my case, I think I found the solution.

Here is the situation:

SQL Server 2005 is on a member Server.

VS 2005 is on Windows XP Work Station.

Development project is on Windows XP Work Station.

When running ASP.NET Configuration, all Users, roles, etc. end up in the App_Data folder in the ASPNETDB database. After testing application, it is copied to Server but the ASPNETDB errors out because it is looking for SQLExpress and not SQL Server 2005.

Here is what I did to get around the issue:

1. Made sure the SQL Server DB had the ASPNETDB.

if it is not there,

run aspnet_regsql.exe

click next

Select Configure SQL server for applications

Click next

Add the server name and LEAVE the database as <default>

Click next

Click next

That will create the ASPNETDB.

2. From inside my application, used Server Explorer to Connect to the SQL ASPNETDB database.

3. Right click on the ASPNETDB, select properties, locate connection string, and copy connection string.

4. Inside my Web.Config file, I created a new connection string as such.

<appSettings/>

<connectionStrings>

<remove name="LocalSqlServer"/>

<add name="LocalSqlServer" connectionString="Data Source=<myServer>;Initial Catalog=aspnetdb;Integrated Security=True;"/>

</connectionStrings>

5. I deleted the ASPNETDB from the app_data folder on my local drive.

Now when I run ASP.NET Configuration or my application, I'm posting data to the SQL Server and not the App_Data folder.

While looking for solutions, I ran across a couple of sites that recommended having users and roles inside the application database. Other recommended using the ASPNETDB database. I never did find a specific answer for one way or the other. All I know, what I have is now working and after 4 weeks of frustration, I'm going to stick with this for a while until someone can show me a better way.

Saturday, February 25, 2012

Anonymous Access from Pivot Table to OLAP 2005

My asp-net web application connect to Analysis Services 2005 through Pivot Table client.

To use anonymous access with AS2000 i used to add this property to the connection string of the pivot: "SSPI=anonymous".

Which property give me the same thing with AS2005?

Thanks!

Hi,

The SSPI connection property is still there, so it should work the same. Are you getting an error?

David Botzenhart

|||

Hey David - good to hear from you !

Yes, you could still use SSPI=anonymous, but I really recommend in AS2005 to use standard OLEDB property for this purpose, i.e.

Protection Level=none

It has slightly better (more standard) behavior.

Mosha (http://www.mosha.com/msolap )

|||

Thanks, it's working.

But, if i set "Impersonation Level" property to Anonymous? Is this the same of SSPI=anonymous?

Thursday, February 16, 2012

Analysis Services through Management Studio: cannot connect. Possible workaround.

I have a SQL server 2005 developer edition installation on my Windows XP SP2 workstation. SQL Server was installed after Visual Studio 2005 pro, and therefore after SQL Express. From what I recall, SQL Browser was also installed with SQL Express using the Local System account as the Browser service account.

As per best-security practice, I have installed 2005 developer edition with the accounts for the services as local accounts (different account for each service). Obviously, due to the VS2005 install, Browser was installed using the Local System account. I therefore created a local account for the Browser, and put it into the SQLServer2005SQLBrowserUser$MACHINENAME security group. I then switched the Browser service account to the local account using Configuration Manager, which therefore restarted the Browser service.

Next, when accessing Analysis Services (SSAS) through the management studio (SSMS) I got the following error:

Cannot connect to MACHINENAME\INSTANCENAME
|
--A connection cannot be made to redirector. Ensure that 'SQL Browser' service is running. (Microsoft.AnalysisServices.AdomdClient)
|
--No connection could be made because the target machine actively refused it (System)

Changing the Browser logon account back to Local System allowed me to connect to SSAS through SSMS (after a Browser service restart).

Reading BOL for 2005, it states that the security permissions required for the Browser service account are:
90\shared\msmdlocal.ini
Read
90\shared
Read, Execute
90\shared\Errordumps
Read, Write
Looking at those folders, I could see that this was the set correctly, as implied through the SQLServer2005SQLBrowserUser$MACHINENAME security group membership which SYSTEM (set through the installation of SQL express, presumably) and the local account were members of. msmdlocal.ini does not exist on my installation.

However, the major clue that I could see was that SYSTEM account had Full access to the Shared and ErrorDumps folders by default; so I then elevated the SQLServer2005SQLBrowserUser$MACHINENAME security permissions to Full on the Shared and ErrorDumps folders, set the Browser service back to the local user account and restarted it. Bingo! I can now access the SSAS through SSMS.

Better still, I immediately reduced the SQLServer2005SQLBrowserUser$MACHINENAME to the recommended settings, restarted the Browser service, and I can still access SSAS through SSMS.

My question is ... why? What happened during my restart under elevated permissions that let the Browser service work properly? I suspect it is something along the lines of the local account taking ownership of something :-s, although I really have no idea. Is this a recognised problem? Is there a KB article on it? Do we have to do similar things to this when we change service accounts for other SQL services?

Andy

Did you use SQL Server Configuration Manager to change account or Windows Computer Manager?

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Configuration Manager. Though I take it you mean the Service console snap-in rather than Computer Manager directly? However the answer is still SSCM.

Andy

|||

In this case I dont see any explanation to the behavior you describe.

Can you please try an contact Customer support about this situation.

Thanks.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||I'll set up a virtual machine and try and reproduce it. Once I know I can I will get in touch with customer support.|||

There was something in your original description that may explain what is going on. According to your 1st post, you:

1. Change the account of the SQL Browser

2. Then added the account to the SQL Browser User group.

3. Then updated the account through SQL Computer Manger.

You should have only done step 3.

By doing 1 and 2, the SQL Computer Manger could have been tricked into thinking you only wished to changes the password. SQL Computer Manager needs to do other operation, individual to each service, than change the account and update the user group.

This also fits with the problem "going away" after you "fixed" the problem.

Does this seem like a possibility?

|||

I had the exact problem as you described, SQL Browser started fine, allowed access to a SQL instance, but actively refused connection to a SSAS instance.

Switching to System solved the problem, but the permanent fix was to increase the permissions to the Shared + Error dump folders as described above.

|||

Thanks so much for posting the details of your experience! I had the same problem and was able to fix it because of your post.

Cheers!

Analysis Services through Management Studio: cannot connect. Possible workaround.

I have a SQL server 2005 developer edition installation on my Windows XP SP2 workstation. SQL Server was installed after Visual Studio 2005 pro, and therefore after SQL Express. From what I recall, SQL Browser was also installed with SQL Express using the Local System account as the Browser service account.

As per best-security practice, I have installed 2005 developer edition with the accounts for the services as local accounts (different account for each service). Obviously, due to the VS2005 install, Browser was installed using the Local System account. I therefore created a local account for the Browser, and put it into the SQLServer2005SQLBrowserUser$MACHINENAME security group. I then switched the Browser service account to the local account using Configuration Manager, which therefore restarted the Browser service.

Next, when accessing Analysis Services (SSAS) through the management studio (SSMS) I got the following error:

Cannot connect to MACHINENAME\INSTANCENAME
|
--A connection cannot be made to redirector. Ensure that 'SQL Browser' service is running. (Microsoft.AnalysisServices.AdomdClient)
|
--No connection could be made because the target machine actively refused it (System)

Changing the Browser logon account back to Local System allowed me to connect to SSAS through SSMS (after a Browser service restart).

Reading BOL for 2005, it states that the security permissions required for the Browser service account are:
90\shared\msmdlocal.ini
Read
90\shared
Read, Execute
90\shared\Errordumps
Read, Write
Looking at those folders, I could see that this was the set correctly, as implied through the SQLServer2005SQLBrowserUser$MACHINENAME security group membership which SYSTEM (set through the installation of SQL express, presumably) and the local account were members of. msmdlocal.ini does not exist on my installation.

However, the major clue that I could see was that SYSTEM account had Full access to the Shared and ErrorDumps folders by default; so I then elevated the SQLServer2005SQLBrowserUser$MACHINENAME security permissions to Full on the Shared and ErrorDumps folders, set the Browser service back to the local user account and restarted it. Bingo! I can now access the SSAS through SSMS.

Better still, I immediately reduced the SQLServer2005SQLBrowserUser$MACHINENAME to the recommended settings, restarted the Browser service, and I can still access SSAS through SSMS.

My question is ... why? What happened during my restart under elevated permissions that let the Browser service work properly? I suspect it is something along the lines of the local account taking ownership of something :-s, although I really have no idea. Is this a recognised problem? Is there a KB article on it? Do we have to do similar things to this when we change service accounts for other SQL services?

Andy

Did you use SQL Server Configuration Manager to change account or Windows Computer Manager?

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Configuration Manager. Though I take it you mean the Service console snap-in rather than Computer Manager directly? However the answer is still SSCM.

Andy

|||

In this case I dont see any explanation to the behavior you describe.

Can you please try an contact Customer support about this situation.

Thanks.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||I'll set up a virtual machine and try and reproduce it. Once I know I can I will get in touch with customer support.|||

There was something in your original description that may explain what is going on. According to your 1st post, you:

1. Change the account of the SQL Browser

2. Then added the account to the SQL Browser User group.

3. Then updated the account through SQL Computer Manger.

You should have only done step 3.

By doing 1 and 2, the SQL Computer Manger could have been tricked into thinking you only wished to changes the password. SQL Computer Manager needs to do other operation, individual to each service, than change the account and update the user group.

This also fits with the problem "going away" after you "fixed" the problem.

Does this seem like a possibility?

|||

I had the exact problem as you described, SQL Browser started fine, allowed access to a SQL instance, but actively refused connection to a SSAS instance.

Switching to System solved the problem, but the permanent fix was to increase the permissions to the Shared + Error dump folders as described above.

|||

Thanks so much for posting the details of your experience! I had the same problem and was able to fix it because of your post.

Cheers!

Sunday, February 12, 2012

Analysis Services connection using AMO

Hi,

I have AS2005 running on a development machine, and i am trying to connect to it via my application running on another machine.

The code is using the Analysis Mangement Object (AMO) API.

Currently, my application code only tries to connect and disconnect from the server.

Server svr = new Server();

svr.Connect(connectionString); < Exception thrown here

svr.Disconnect();

The connectionString simply contains the remote server's name. I have also tried different connection strings but it has not helped.

I have also enabled remote connections on AS, and opened the default port number on the server's firewall.

Every time it tries to connect the exception thrown is:

"Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host."

Can anybody help me with this problem?

I'm not sure if this will help, but I was getting a similar error with

the BI Development Studio. In that case it was a security

issue. Basically, becasue the machine was on a different domain,

I had to create a user on that machine with the same username /

password as the one that I log into my machine with. Have you

tried connecting in any other way?|||

Is the "other machine" an AS2K5 instance?

_-_-_ Dave

Analysis Services Connection problem

I can't connect to Analysis Services accroding execl
pivottable. The error message is "Unable to open
connection. Cannot connect to cube
file. '10.97.69.212',file may be in use." The TCP/IP is
well but the client is not a domain user.What is the
prolem? How to resolve it?Are you specifying an IP address instead of a computer name?
243093 FIX: Using an IP Address for OLAP Data Source Connection Property
Causes
http://support.microsoft.com/?id=243093
Are you going across domains? If so, you'll need to follow these
instructions:
280431 How to Enable Commerce Server 2000 OLAP Reports Over HTTPS with SQL
http://support.microsoft.com/?id=280431
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.

Thursday, February 9, 2012

Analysis Services 2005 Authntication

Hi,

I have a small problem i.e. in SQL Server 2005 Management Studio i can connect to database engine as "Windows Authentication" as well as "Sql Server Authentication". But for connecting Analysis Services Database, Authentication is disabled and by default it is "Windows Authentication". To Enable the Authentication for logging as "SQL Server Authentication" what is the procedure to do.

Can you please help me in this.

Thanks

Dinesh

Hi,

As far as I was aware you can't enable it, based on the fact that the SQL Server logins are associated with a database engine not the Analysis Services engine.

http://technet.microsoft.com/en-us/library/ms144288.aspx

Near the end of that page

Specifying Analysis Services Authentication Mode

SQL Server 2005 Analysis Services supports only Windows Authentication.

Cheers

Matt

|||

Hello! SSAS2005 and earlier only supports windows authentication. Like Matt told you SQL Server authentication is a feature only in the database engine.

Regards

Thomas Ivarsson

|||How does this affect Reporting Services where Forms authentication is being used? We have changed our SSRS to use Forms Authentication although the report connects to an SSAS cube - I am now having problems connecting to this data source. Is it possible to have SSAS also use Forms Authentication?|||

I am not familiar with the Forms Authentication, but because Analysis Services only supports integrated authentication, would it be possible for you to impersonate the specified Windows user (with the Windows account name and password specified, I assume, in the forms) in the application that connects to SSAS ?