Cannot see Login account properties

Hi everybody !!!

I have SQLServer 2005 installed and I think a login account is corrupted because Im not able to connect to a database. I get an Timeout expiration error after I clicked on Login Properties or when I try to make a connection to SQLServer 2005 using that login account. Also I cannot review the script needed to create the login, but I do can review the database user properties mapped to this login account.

Is there a way to recreate or repair a login account?

The only solution I have right now is create another login accout, but this involves to modify database connection properties within my code.

Any help, comment or suggestion is really appreciated.

Thans a lot.

I am guessing you are using Microsoft SQL Management Studio object browser to look at the properties, correct? It may be a problem in the tool, I would recommend asking about this one in the tools forum (http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=84&SiteID=1).

To quickly verify if there is indeed something wrong with this particular login, you can try the following statement:

SELECT * FROM sys.server_principals WHERE name = 'login_name'

Go

You can also try the following statement to make sure the system is able to use this login as a valid principal:

EXECUTE AS LOGIN = 'login_name'

Let us know if you encountered any problem while running these statements.

Thanks a lot,

-Raul Garcia

SDE/T

SQL Server Engine

Cannot see Login account properties

Hi everybody !!!

I have SQLServer 2005 installed and I think a login account is corrupted because Im not able to connect to a database. I get an Timeout expiration error after I clicked on Login Properties or when I try to make a connection to SQLServer 2005 using that login account. Also I cannot review the script needed to create the login, but I do can review the database user properties mapped to this login account.

Is there a way to recreate or repair a login account?

The only solution I have right now is create another login accout, but this involves to modify database connection properties within my code.

Any help, comment or suggestion is really appreciated.

Thans a lot.

I forgot to say that I get the same Timeout expiration error when I try to drop the login account.

Thanks in advance.

Cannot restore / Create Analysis Database

Hi everybody,

I've installed SSAS 2008.

When I try to create a new database or to restore a database, I've many errors :

Create Database :

Either the 'TLS\christophe.laporte' user does not have permission to create a new object in 'PC-LAPORTE', or the object does not exist.
(Microsoft.AnalysisServices)

Program Location:

at Microsoft.AnalysisServices.AnalysisServicesClient.SendExecuteAndReadResponse(ImpactDetailCollection impacts, Boolean expectEmptyResults, Boolean throwIfError)
at Microsoft.AnalysisServices.AnalysisServicesClient.Alter(IMajorObject obj, ObjectExpansion expansion, ImpactDetailCollection impact, Boolean allowCreate)
at Microsoft.AnalysisServices.Server.Update(IMajorObject obj, UpdateOptions options, UpdateMode mode, XmlaWarningCollection warnings, ImpactDetailCollection impactResult)
at Microsoft.AnalysisServices.Server.SendUpdate(IMajorObject obj, UpdateOptions options, UpdateMode mode, XmlaWarningCollection warnings, ImpactDetailCollection impactResult)
at Microsoft.AnalysisServices.MajorObject.Update(UpdateOptions options, UpdateMode mode, XmlaWarningCollection warnings)
at Microsoft.AnalysisServices.MajorObject.Update()
at Microsoft.AnalysisServices.ManagementDialogs.OlapCreateDB.SendDataToServer()

Restore Database when I click on browse button:

Database administrator or server administrator permissions are required to execute SystemGetLogicalDrives command. (Microsoft SQL Server code name "Katmai" Analysis Services)

Program Location:

at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Microsoft.AnalysisServices.AdomdClient.IExecuteProvider.ExecuteTabular(CommandBehavior behavior, ICommandContentProvider contentProvider, AdomdPropertyCollection commandProperties, IDataParameterCollection parameters)
at Microsoft.AnalysisServices.AdomdClient.AdomdCommand.ExecuteReader(CommandBehavior behavior)
at Microsoft.AnalysisServices.AdomdClient.AdomdCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet)
at Microsoft.AnalysisServices.Controls.FileSystemBrowser.Call(String function)
at

Any idea ?

I've installed Katmai on Vista. My account is in the administrators group on the computer. All services are started with a domain admin account ( and I'am too).

Maybe I've te setup katmai again ?

Thanks.

Christophe.

France.

Oups, sorry,

SSMS launched with administrator privileges is OK.

But why I get this error ? MMy account is administrator ...

And why SSMS don't query about privilege elevation when browsing for files or creating a database ?

Chrisstophe.

France.

|||

Chris,

I am not surprised that you have issues with SSAS on Vista PC. Actually on CTP download page Microsoft has a note regarding this:

The SQL Server 2008 June CTP has known compatibility issues with Windows Vista and Windows Server 2008 Beta. We do not recommend testing this CTP on this configuration. Instead, test this CTP on Windows Server 2003 Enterprise Edition with SP1 installed for 32-bit x86 and 64-bit x64 editions, and Windows XP Professional Edition with SP2 installed for 32-bit x86 and 64-bit x64 editions.

So I think you just will have to wait for future CTPs and see if they fixed issues on Vista.

Vidas Matelis

http://www.ssas2008-info.com

Cannot resolve the collation conflict.

Hello everybody,

I need help urgently.

After upgraded my sql server to SP2, i have this problem:

Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AI" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.

Why? any solution?

best reguards

It would be useful to know the context in which this error occurs:

When running certain queries?