Error executing User Defined function on another server

Hi All,
Facing a problem while executing a user defined function (UDF) which resides
on another sql server ( we have access on this sql server to execute the
UDF). This UDF accepts a varchar parameter with max length 8. When we
execute the function as
Select * from
SERVERNAME.DBName.dbo. fn_GetConsulteesDataForReport('00118179'
) it throws an
error as given below.
Server: Msg 170, Level 15, State 31, Line 1
Line 2: Incorrect syntax near '('.
Please let me know what is the issue in my SQL statement and how we can
resolve this.
Thanks in advance.
SuhasThere's a workaround for this hm... feature. Use the OPENQUERY function:
select *
from openquery(SERVERNAME, '
select *
from
DBName.dbo. fn_GetConsulteesDataForReport('00118179'
)
')
ML
http://milambda.blogspot.com/|||Hi ML,
Thank you for giving this suggestion. But please let me know whether open
query does accept variable as an input to the function ? I mean, can I
execute the same as given below.
declare @.empid varchar(8)
select @.empid = '00118179'
select *
from openquery(SERVERNAME, '
select *
from
DBName.dbo.fn_GetConsulteesDataForReport(@.empid)
')
Becuase we need to dynamically change this employee ID.
Thank you.
Suhas
"ML" wrote:

> There's a workaround for this hm... feature. Use the OPENQUERY function:
> select *
> from openquery(SERVERNAME, '
> select *
> from
> DBName.dbo. fn_GetConsulteesDataForReport('00118179'
)
> ')
>
> ML
> --
> http://milambda.blogspot.com/|||For actual production use I'd suggest designing a local UDF, that references
tables in the database on the linked server. This way you can call the
function directly, and still access the data remotely.
ML
http://milambda.blogspot.com/|||Sorry, I forgot to mention, that OPENQUERY does not accept parameters or
variables. Read more here:
http://msdn.microsoft.com/library/d...br />
5xix.asp
ML
http://milambda.blogspot.com/

ERROR EXECUTING EXTENDED STORED PROCEDURE Specified user can not login

Hello All,
I'm wrote a program that uses the extended stored procedure XP_CMDSHELL .
The user is not an admin and I'm not sure how to set up a Proxy account.
I'm getting the following error when I try to add the user into the
Non-SysAdmin job step proxy account.
ERROR EXECUTING EXTENDED STORED PROCEDURE Specified user can not login
I gave the users domain rights to the master database on the server and then
gave permission to use the XP_CMDSHELL procedure.
My knowledge on permissions in SQL SERVER 2000 is hazy and I would like to
know what steps I have to take to add a non-admin user to be able to use the
XP_CMDSHELL procedure. Do I have to set anything outside of SQL SERVER
2000?...
Any help will be greatly appreciated.
Thanks,
Matt
If the user invoking xp_cmdshell is not a member of the sysadmin role, the
proxy account will be used.
The proxy account is setup using the dialog on the SQL Agent property page
in SQL Enterprise Manager (Job System tab) or using the extend stored
procedure xp_sqlagent_proxy_account, see
http://msdn.microsoft.com/library/de...aa-sz_8sdm.asp
See http://www.databasejournal.com/featu...le.php/3372131 for
more background.
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2005 All rights reserved.
"Matthew Beirn" <mbeirn@.ssimed.com> wrote in message
news:u7EruuMTFHA.3336@.TK2MSFTNGP10.phx.gbl...
> Hello All,
> I'm wrote a program that uses the extended stored procedure XP_CMDSHELL .
> The user is not an admin and I'm not sure how to set up a Proxy account.
> I'm getting the following error when I try to add the user into the
> Non-SysAdmin job step proxy account.
> ERROR EXECUTING EXTENDED STORED PROCEDURE Specified user can not login
> I gave the users domain rights to the master database on the server and
> then gave permission to use the XP_CMDSHELL procedure.
> My knowledge on permissions in SQL SERVER 2000 is hazy and I would like to
> know what steps I have to take to add a non-admin user to be able to use
> the XP_CMDSHELL procedure. Do I have to set anything outside of SQL
> SERVER 2000?...
> Any help will be greatly appreciated.
> Thanks,
> Matt
>

ERROR EXECUTING EXTENDED STORED PROCEDURE Specified user can not login

Hello All,
I'm wrote a program that uses the extended stored procedure XP_CMDSHELL .
The user is not an admin and I'm not sure how to set up a Proxy account.
I'm getting the following error when I try to add the user into the
Non-SysAdmin job step proxy account.
ERROR EXECUTING EXTENDED STORED PROCEDURE Specified user can not login
I gave the users domain rights to the master database on the server and then
gave permission to use the XP_CMDSHELL procedure.
My knowledge on permissions in SQL SERVER 2000 is hazy and I would like to
know what steps I have to take to add a non-admin user to be able to use the
XP_CMDSHELL procedure. Do I have to set anything outside of SQL SERVER
2000?...
Any help will be greatly appreciated.
Thanks,
MattIf the user invoking xp_cmdshell is not a member of the sysadmin role, the
proxy account will be used.
The proxy account is setup using the dialog on the SQL Agent property page
in SQL Enterprise Manager (Job System tab) or using the extend stored
procedure xp_sqlagent_proxy_account, see
sz_8sdm.asp" target="_blank">http://msdn.microsoft.com/library/d.../>
sz_8sdm.asp
See http://www.databasejournal.com/feat...cle.php/3372131 for
more background.
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2005 All rights reserved.
"Matthew Beirn" <mbeirn@.ssimed.com> wrote in message
news:u7EruuMTFHA.3336@.TK2MSFTNGP10.phx.gbl...
> Hello All,
> I'm wrote a program that uses the extended stored procedure XP_CMDSHELL .
> The user is not an admin and I'm not sure how to set up a Proxy account.
> I'm getting the following error when I try to add the user into the
> Non-SysAdmin job step proxy account.
> ERROR EXECUTING EXTENDED STORED PROCEDURE Specified user can not login
> I gave the users domain rights to the master database on the server and
> then gave permission to use the XP_CMDSHELL procedure.
> My knowledge on permissions in SQL SERVER 2000 is hazy and I would like to
> know what steps I have to take to add a non-admin user to be able to use
> the XP_CMDSHELL procedure. Do I have to set anything outside of SQL
> SERVER 2000?...
> Any help will be greatly appreciated.
> Thanks,
> Matt
>

ERROR EXECUTING EXTENDED STORED PROCEDURE Specified user can not login

Hello All,
I'm wrote a program that uses the extended stored procedure XP_CMDSHELL .
The user is not an admin and I'm not sure how to set up a Proxy account.
I'm getting the following error when I try to add the user into the
Non-SysAdmin job step proxy account.
ERROR EXECUTING EXTENDED STORED PROCEDURE Specified user can not login
I gave the users domain rights to the master database on the server and then
gave permission to use the XP_CMDSHELL procedure.
My knowledge on permissions in SQL SERVER 2000 is hazy and I would like to
know what steps I have to take to add a non-admin user to be able to use the
XP_CMDSHELL procedure. Do I have to set anything outside of SQL SERVER
2000?...
Any help will be greatly appreciated.
Thanks,
MattIf the user invoking xp_cmdshell is not a member of the sysadmin role, the
proxy account will be used.
The proxy account is setup using the dialog on the SQL Agent property page
in SQL Enterprise Manager (Job System tab) or using the extend stored
procedure xp_sqlagent_proxy_account, see
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_xp_aa-sz_8sdm.asp
See http://www.databasejournal.com/features/mssql/article.php/3372131 for
more background.
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright © SQLDev.Net 1991-2005 All rights reserved.
"Matthew Beirn" <mbeirn@.ssimed.com> wrote in message
news:u7EruuMTFHA.3336@.TK2MSFTNGP10.phx.gbl...
> Hello All,
> I'm wrote a program that uses the extended stored procedure XP_CMDSHELL .
> The user is not an admin and I'm not sure how to set up a Proxy account.
> I'm getting the following error when I try to add the user into the
> Non-SysAdmin job step proxy account.
> ERROR EXECUTING EXTENDED STORED PROCEDURE Specified user can not login
> I gave the users domain rights to the master database on the server and
> then gave permission to use the XP_CMDSHELL procedure.
> My knowledge on permissions in SQL SERVER 2000 is hazy and I would like to
> know what steps I have to take to add a non-admin user to be able to use
> the XP_CMDSHELL procedure. Do I have to set anything outside of SQL
> SERVER 2000?...
> Any help will be greatly appreciated.
> Thanks,
> Matt
>sql

Error Creating User on Database

Hi there,

I am setting up a database for the first time using SQL Server Express.

I have managed to create a database and create a table with data etc, all straight forward.

The problem I am having is when I come to creating a user for the database. I have the following users in there already, which I am guessing are put in by default:

dbo

guest

INFORMATION_SCHEMA

sys

When I try creating a new user via this screen I get the following error:

TITLE: Microsoft SQL Server Management Studio Express

Create failed for User 'growstudiouser'. (Microsoft.SqlServer.Express.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Create+User&LinkId=20476

ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.Express.ConnectionInfo)

'growstudio' is not a valid login or you do not have permission. (Microsoft SQL Server, Error: 15007)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=15007&LinkId=20476

I was wondering if anybody could advise me as to what I'm doing wrong. I am typing in the name as "growstudiouser" and the login name as "growstudio".

Or am I just using the wrong section to do what I want. I'm trying to create a user so that when the database is built I can connect to it using a username and password that I have created. I'm not sure I'm taking to the correct route as there is no password option anywhere when creating a new user.

Thanks in advance,

Kevin

hi Kevin,

usually a database user is associated with a server's login, if you do not define a user as

USE tempdb; GO CREATE USER testUser WITHOUT LOGIN WITH DEFAULT_SCHEMA = dbo; GO DROP USER testUser;

where the database user is not associated with a server level principal, but this is another story..

so you should first create the server login as

USE master; CREATE LOGIN testLogin WITH PASSWORD = 'his strong password'; GO USE tempdb; GO CREATE USER testUser FOR LOGIN testLogin WITH DEFAULT_SCHEMA = dbo; GO DROP USER testUser; GO USE master; GO DROP LOGIN testLogin;

regards

|||

SQL Server follows two level security architecture. Login and User . Login is to access to the server. If you have login it does not mean that you have access to all the databases in that server. NO. To access database, the Login has to be mapped/added to the database as user. So , in your case what your are probably doing is you are not maping the user with a login . You should select a login while creating user

Madhu

Error creating datasource

A user is getting an error "Cannot update, database or object is read-only"
when creating a datasource.
The user has db_owner role of the database that's being connected to.
I know very little of Analysis Server and any help would be appreciated.
Thanks.
RonThis is the typical error when two or more users are using SQL Analysis
Manager and the Olap repository is still in MS Access database, which it's
oppened in exclusive mode by Analysis Manager.
Try migrating Olap Repository to SQL Server and hopefully your problem is
gone.
Michael Prendergast
"Ron" <Ron@.discussions.microsoft.com> escribi en el mensaje
news:CC03234F-0585-41A7-8128-078EB865B5AA@.microsoft.com...
>A user is getting an error "Cannot update, database or object is read-only"
> when creating a datasource.
> The user has db_owner role of the database that's being connected to.
> I know very little of Analysis Server and any help would be appreciated.
> Thanks.
> Ron
>|||There's no Access involved - just SQL Server
Ron
"MPS" wrote:

> This is the typical error when two or more users are using SQL Analysis
> Manager and the Olap repository is still in MS Access database, which it's
> oppened in exclusive mode by Analysis Manager.
> Try migrating Olap Repository to SQL Server and hopefully your problem is
> gone.
> Michael Prendergast
>
> "Ron" <Ron@.discussions.microsoft.com> escribió en el mensaje
> news:CC03234F-0585-41A7-8128-078EB865B5AA@.microsoft.com...
>
>|||How do you migrate the OLAP Repository (Access) to a SQL Server?
"MPS" wrote:

> This is the typical error when two or more users are using SQL Analysis
> Manager and the Olap repository is still in MS Access database, which it's
> oppened in exclusive mode by Analysis Manager.
> Try migrating Olap Repository to SQL Server and hopefully your problem is
> gone.
> Michael Prendergast
>
> "Ron" <Ron@.discussions.microsoft.com> escribió en el mensaje
> news:CC03234F-0585-41A7-8128-078EB865B5AA@.microsoft.com...
>
>|||Open Analysis Manager, select the server name in the list (typically one),
right click over the server name and there you are, MIGRAR DEPOSITO in
Spanish, MIGRATE REPOSITORY I guess in English (I use Spanish version
You will need a DB created in SQL Server and connect to it with owner
privileges over that database
"Rodrigo" <Rodrigo@.discussions.microsoft.com> escribi en el mensaje
news:515C83DA-0157-4E12-9832-DAD3A18AC8E8@.microsoft.com...
> How do you migrate the OLAP Repository (Access) to a SQL Server?
>
> "MPS" wrote:
>
>|||Just in case, default installation for MS Analysis Services manages Olap
repository in an Access Database.
Probably you do not have any data in Access, but the repository, if is not
migrated yet, It's still in a MS Access Database. The file is named
msmdrep.mdb and has two tables, OlapObjects and Server.
Hope it helps,
Michael Prendergast
"Ron" <Ron@.discussions.microsoft.com> escribi en el mensaje
news:6DB504F8-F1CB-4EFB-A216-8A50909012E5@.microsoft.com...
> There's no Access involved - just SQL Server
> Ron
> "MPS" wrote:
>
>|||That did the trick - Thanks MPS.
"MPS" wrote:

> Just in case, default installation for MS Analysis Services manages Olap
> repository in an Access Database.
> Probably you do not have any data in Access, but the repository, if is not
> migrated yet, It's still in a MS Access Database. The file is named
> msmdrep.mdb and has two tables, OlapObjects and Server.
> Hope it helps,
> Michael Prendergast
> "Ron" <Ron@.discussions.microsoft.com> escribió en el mensaje
> news:6DB504F8-F1CB-4EFB-A216-8A50909012E5@.microsoft.com...
>
>|||Good to hear that
Michael Prendergast
"Ron" <Ron@.discussions.microsoft.com> escribi en el mensaje
news:0727D691-8903-4472-97BC-1A9F65508608@.microsoft.com...
> That did the trick - Thanks MPS.
> "MPS" wrote:
>
>

Error Count not obtain information about Windows NT group/user

We receive an error as the server attempts to create a publication. The user
has permissions on both the server as an administrator and as an sa. This
conflict should not occur. Can anyone help to explain this? It has been
suggested we go to SP4. There are concerns about firmware and blue screening
on the primary server at this time may preclude sp4 as an option.
Regards,
Jamie
Is there a possibility that when an Enterprise 2005 version of SQL encounters
a Standard version 2000, that this error pops up?
Regards,
Jamie
"thejamie" wrote:

> We receive an error as the server attempts to create a publication. The user
> has permissions on both the server as an administrator and as an sa. This
> conflict should not occur. Can anyone help to explain this? It has been
> suggested we go to SP4. There are concerns about firmware and blue screening
> on the primary server at this time may preclude sp4 as an option.
> --
> Regards,
> Jamie

Error connecting

Cannot open database requested in login <DatabaseName>. Login fails.
Login failed for user <DOMAINNAME\User>.
Please help."Viktor Zadro" <viktor.zadro@.tel.net.ba> wrote in message
news:ukzXI7IcEHA.3016@.tk2msftngp13.phx.gbl...
> Cannot open database requested in login <DatabaseName>. Login fails.
> Login failed for user <DOMAINNAME\User>.
>
How are you attempting to connect? Can you reproduce this using Query
Analyzer? What login and database permissions have you defined for this
user?
Steve|||Hello, Steve,
How can I manage SQL Server's users, for example, how to change the 'sa' pas
sword?
Is it can only be done by using 'Enterprise Manager'?
LLF
--
There's an unfinished grid inside my head...
"Steve Thompson" wrote:

> "Viktor Zadro" <viktor.zadro@.tel.net.ba> wrote in message
> news:ukzXI7IcEHA.3016@.tk2msftngp13.phx.gbl...
> How are you attempting to connect? Can you reproduce this using Query
> Analyzer? What login and database permissions have you defined for this
> user?
> Steve
>
>|||LLF,
You can use Enterprise Manager if you wish. Enterprise
Manager is really just executing T-SQL commands for you so
you can manage these through Query Analyzer or any other
tool that can connect to and execute queries on SQL Server.
Passwords are changed using sp_password.
You can add logins using sp_grantlogin for Windows logins or
sp_addlogin for SQL logins.
You can add users to a database using sp_grantdbaccess.
You can find all of these system stored procedures
documented in SQL Server Books Online.
-Sue
On Tue, 27 Jul 2004 10:01:37 -0700, LLF
<LLF@.discussions.microsoft.com> wrote:

>Hello, Steve,
>How can I manage SQL Server's users, for example, how to change the 'sa' pa
ssword?
>Is it can only be done by using 'Enterprise Manager'?
>LLF|||Thanks a lot !
LLF
There's an unfinished grid inside my head...
"Sue Hoegemeier" wrote:

> LLF,
> You can use Enterprise Manager if you wish. Enterprise
> Manager is really just executing T-SQL commands for you so
> you can manage these through Query Analyzer or any other
> tool that can connect to and execute queries on SQL Server.
> Passwords are changed using sp_password.
> You can add logins using sp_grantlogin for Windows logins or
> sp_addlogin for SQL logins.
> You can add users to a database using sp_grantdbaccess.
> You can find all of these system stored procedures
> documented in SQL Server Books Online.
> -Sue
> On Tue, 27 Jul 2004 10:01:37 -0700, LLF
> <LLF@.discussions.microsoft.com> wrote:
>
>

Error connecting

Cannot open database requested in login <DatabaseName>. Login fails.
Login failed for user <DOMAINNAME\User>.
Please help.
"Viktor Zadro" <viktor.zadro@.tel.net.ba> wrote in message
news:ukzXI7IcEHA.3016@.tk2msftngp13.phx.gbl...
> Cannot open database requested in login <DatabaseName>. Login fails.
> Login failed for user <DOMAINNAME\User>.
>
How are you attempting to connect? Can you reproduce this using Query
Analyzer? What login and database permissions have you defined for this
user?
Steve
|||Hello, Steve,
How can I manage SQL Server's users, for example, how to change the 'sa' password?
Is it can only be done by using 'Enterprise Manager'?
LLF
There's an unfinished grid inside my head...
"Steve Thompson" wrote:

> "Viktor Zadro" <viktor.zadro@.tel.net.ba> wrote in message
> news:ukzXI7IcEHA.3016@.tk2msftngp13.phx.gbl...
> How are you attempting to connect? Can you reproduce this using Query
> Analyzer? What login and database permissions have you defined for this
> user?
> Steve
>
>
|||LLF,
You can use Enterprise Manager if you wish. Enterprise
Manager is really just executing T-SQL commands for you so
you can manage these through Query Analyzer or any other
tool that can connect to and execute queries on SQL Server.
Passwords are changed using sp_password.
You can add logins using sp_grantlogin for Windows logins or
sp_addlogin for SQL logins.
You can add users to a database using sp_grantdbaccess.
You can find all of these system stored procedures
documented in SQL Server Books Online.
-Sue
On Tue, 27 Jul 2004 10:01:37 -0700, LLF
<LLF@.discussions.microsoft.com> wrote:

>Hello, Steve,
>How can I manage SQL Server's users, for example, how to change the 'sa' password?
>Is it can only be done by using 'Enterprise Manager'?
>LLF
|||Thanks a lot !
LLF
There's an unfinished grid inside my head...
"Sue Hoegemeier" wrote:

> LLF,
> You can use Enterprise Manager if you wish. Enterprise
> Manager is really just executing T-SQL commands for you so
> you can manage these through Query Analyzer or any other
> tool that can connect to and execute queries on SQL Server.
> Passwords are changed using sp_password.
> You can add logins using sp_grantlogin for Windows logins or
> sp_addlogin for SQL logins.
> You can add users to a database using sp_grantdbaccess.
> You can find all of these system stored procedures
> documented in SQL Server Books Online.
> -Sue
> On Tue, 27 Jul 2004 10:01:37 -0700, LLF
> <LLF@.discussions.microsoft.com> wrote:
>
>

error code sql server

Good morning
MOM server 2005 prompt this message during the installation
Failed to setup database security.
Error code: -2147217900 (user, group, or role 'SC DW DTS'
already exist in the current database)
what can i do in this case
http://groups.google.co.uk/group/mic...hread/thread/9
fc353baf7bde8b8/45c77c865aeb54a8?lnk=st&q=user%2C+group%2C+or+role +'SC+DW+DT
S'+already+exists&rnum=1&hl=en#45c77c865aeb54a8
"Djeff" <e.djeff@.free.fr> wrote in message
news:mn.b33c7d5c80e5082d.46131@.free.fr...
> Good morning
> MOM server 2005 prompt this message during the installation
> Failed to setup database security.
> Error code: -2147217900 (user, group, or role 'SC DW DTS'
> already exist in the current database)
> what can i do in this case
>

error code sql server

Good morning
MOM server 2005 prompt this message during the installation
Failed to setup database security.
Error code: -2147217900 (user, group, or role 'SC DW DTS'
already exist in the current database)
what can i do in this casehttp://groups.google.co.uk/group/mi...thread/thread/9
fc353baf7bde8b8/45c77c865aeb54a8?lnk=st&q=user%2C+group%2C+or+role+'SC+DW+DT
S'+already+exists&rnum=1&hl=en#45c77c865aeb54a8
"Djeff" <e.djeff@.free.fr> wrote in message
news:mn.b33c7d5c80e5082d.46131@.free.fr...
> Good morning
> MOM server 2005 prompt this message during the installation
> Failed to setup database security.
> Error code: -2147217900 (user, group, or role 'SC DW DTS'
> already exist in the current database)
> what can i do in this case
>

error code sql server

Good morning
MOM server 2005 prompt this message during the installation
Failed to setup database security.
Error code: -2147217900 (user, group, or role 'SC DW DTS'
already exist in the current database)
what can i do in this casehttp://groups.google.co.uk/group/microsoft.public.mom/browse_thread/thread/9
fc353baf7bde8b8/45c77c865aeb54a8?lnk=st&q=user%2C+group%2C+or+role+'SC+DW+DT
S'+already+exists&rnum=1&hl=en#45c77c865aeb54a8
"Djeff" <e.djeff@.free.fr> wrote in message
news:mn.b33c7d5c80e5082d.46131@.free.fr...
> Good morning
> MOM server 2005 prompt this message during the installation
> Failed to setup database security.
> Error code: -2147217900 (user, group, or role 'SC DW DTS'
> already exist in the current database)
> what can i do in this case
>

Error Code of 3238395904 and 3240034316

I get the following error for a cube that used to process just fine.

Executed as user: PREMIER_AD\SQLExec. ...ts xmlns="http://schemas.microsoft.com/analysisservices/2003/xmla-multipleresults"><root xmlns="urn:schemas-microsoft-com:xml-analysis:empty"><Exception xmlns="urn:schemas-microsoft-com:xml-analysis:exception" /><Messages xmlns="urn:schemas-microsoft-com:xml-analysis:exception"><Error ErrorCode="3238395904" Description="OLE DB error: OLE DB or ODBC error: Unspecified error." Source="Microsoft SQL Server 2005 Analysis Services" HelpFile="" /><Error ErrorCode="3240034316" Description="Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Vw PASBSCD1291 Fact', Name of 'Drillthrough Data' was being processed." Source="Microsoft SQL Server 2005 Analysis Services" HelpFile="" /><Error ErrorCode="3240034317" Description="Errors in the OLAP storage engine: An error occurred while the 'Reason' attribute of the 'Drillthrough Data' dimension from the 'Pas' database was being processed." Source="Microsoft SQL Server 200... The step succeeded.

I have no idea what Error Codes 3238395904 and 3240034316 are.

Looks like error belongs to the OLEDB provider you are using.

The error message reported by OLEDB provider is just "Unspecified error"

Looks like something went wrong with your relational database connection. Test your conneciton. See if you can process any other objects based on the same data source.

Hope that helps.

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

|||

Thanks, Edward.

The problem seems to have resolved itself. I believe the connectivity issues might be related to capacity problems were were having with our relational database late last week.

Dan

Error Code of 3238395904 and 3240034316

I get the following error for a cube that used to process just fine.

Executed as user: PREMIER_AD\SQLExec. ...ts xmlns="http://schemas.microsoft.com/analysisservices/2003/xmla-multipleresults"><root xmlns="urn:schemas-microsoft-com:xml-analysis:empty"><Exception xmlns="urn:schemas-microsoft-com:xml-analysis:exception" /><Messages xmlns="urn:schemas-microsoft-com:xml-analysis:exception"><Error ErrorCode="3238395904" Description="OLE DB error: OLE DB or ODBC error: Unspecified error." Source="Microsoft SQL Server 2005 Analysis Services" HelpFile="" /><Error ErrorCode="3240034316" Description="Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Vw PASBSCD1291 Fact', Name of 'Drillthrough Data' was being processed." Source="Microsoft SQL Server 2005 Analysis Services" HelpFile="" /><Error ErrorCode="3240034317" Description="Errors in the OLAP storage engine: An error occurred while the 'Reason' attribute of the 'Drillthrough Data' dimension from the 'Pas' database was being processed." Source="Microsoft SQL Server 200... The step succeeded.

I have no idea what Error Codes 3238395904 and 3240034316 are.

Looks like error belongs to the OLEDB provider you are using.

The error message reported by OLEDB provider is just "Unspecified error"

Looks like something went wrong with your relational database connection. Test your conneciton. See if you can process any other objects based on the same data source.

Hope that helps.

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

|||

Thanks, Edward.

The problem seems to have resolved itself. I believe the connectivity issues might be related to capacity problems were were having with our relational database late last week.

Dan

Error Code if Row is locked

Hallo,
if a row is locked in SQLExpress and an other user want to update this row,
SQLExpress waits until timeout. And than I get the errormessage "timeout".

What I need is an immediately errormessage "row is locked" !

So that the user dont need to wait if the row is locked
and I need the correct errormessage so that I can check
if there is a databaseproblem or only the row locked
because an other user is editing the same rows.

Thx Wolfgang
(please excuse my english)

hi,

SQL Server does not provide this feature as this should be managed on the client side of the application and not server side on SQL Server...

you can thus set an appropriate timeout on the ado/ado.net command you are using, and then take the required decision once the command result in an exception..

but you have to fine tune your timeout, depending on SQL Server load, bandwidth, network trafic, ..

regards

|||

Thank you for your help!

I need a small timeout if the Updatecommand "meets" locked rows.
I do not want to reduce the timeout for the SqlCommand itself.

The solution i have found is to use the keyword NOWAIT in the SQL-Statement.

UPDATE table WITH (NOWAIT) SET ......

I think this works okay, but I have not found something to set timeout for locks to 1 sec
and timeout for SQLCommand to 15 sec.

Thany you for your help.
Wolfgang

Error Authentication User Informations

Hey Gang, I get a error message "Authentication Failed for SQL Server
instance: local with friendly name local SQL Server does not exist or
access denied". I have a Just loaded SQL Server on my virtual box and loaded
Microsofts bpa and microsoft security anlyzer. The security scan work but the
bpa scan does
not. I also look at the database,I can get access to and notice a new
database schema(sqlbpa). Any help would be appreciated.

Thanks
Garry DGarry D (garrydawkins@.hotmail.com) writes:
> Hey Gang, I get a error message "Authentication Failed for SQL Server
> instance: local with friendly name local SQL Server does not exist or
> access denied". I have a Just loaded SQL Server on my virtual box and
> loaded Microsofts bpa and microsoft security anlyzer. The security scan
> work but the bpa scan does not. I also look at the database,I can get
> access to and notice a new database schema(sqlbpa). Any help would be
> appreciated.

The message means that the specified SQL Server does not exist. (Or that
your network permissions prevented you from finding it).

If you have SQL Server running on your virtual box, and BPA running on your
host machine and have specified (local) as your SQL Server, that won't
fly. You need to specify the name of the virtual machine.

And, of course, you have to make sure that SQL Server is running.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Thanks, that work perfectly. By Identifying the server name within bpa
it took off and authenticated and is running as we speak.

GDawkins

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Error at: The user is not associated with a trusted SQL Server connection

Hi I've got a common error using SQL server 2005

"The user is not associated with a trusted SQL Server connection"

I'm building a application using C# when using a standalone environment, it worked well. But, now I have the following environment.

A.
SQL server
Domain XXX

B. Remote machine
Application
Domain YYY

I changed SQL server to support SQL and WIN authentication mode and I have changed SQl server surface area configuration to support TCP/IP and Named Pipes for remote connections. But I still have two problems:

1. When using the IP - serverName of the dataserver, the error is

System.Data.SqlClient.SqlException: Login failed for user ''. The user is not associated with a trusted SQL Server connection..

1. When using the server name(MYServerName), I have this error:
System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

Besides, I have tried from my remote machine to use a sqlcmd -E -S tcp:myhost command but I have the same answer.

Any help, I will thank.I believe you set Mixed Authentication in your SQL server in the domain XXX.
And you have an NT login in the application YYY domain.

You could try two things:

Check if you have the same NT login in XXX domain.
The XXX domain needs to trust the YYY domain to allow this to occur. You
could use SQL Server authentication instead if you don't want this trust to
occur. Trouble is you need to pass the password for the SQL login, but worth to try.|||this should work as long as the xxx domain trusts the yyy domain. if it doesn't, windows auth won't work.

is it possible to login to a box in XXX with an nt account in YYY? if not then there is no trust.

Error Adding User

Hello, I have a problem with adding users to a database using sp_adduser.
The user I'm using is a member of db_owner but I receive the following error:
sp_adduser adam, adam, DEFAULT_USERS
Server: Msg 15247, Level 16, State 1, Procedure sp_adduser, Line 35
User does not have permission to perform this action
It only works when I log in as a System Administrator. However if I login as
the db_owner account which generates the above error and run the following:
exec sp_grantdbaccess adam
exec sp_addrolemember DEFAULT_USERS, adam
It works fine. The problem is that it is a piece of 3rd party software that
is trying to add the users and won't be easy to get them to change it as
sp_adduser should work. Also I don't want them logging in as System
Administrator when I could try and fix it. Any ideas?
One solution is to drop the user from the database, and then make its login
the owner of the database:
sp_dropuser 'the_user'
go
use the_database
go
sp_changedbowner 'the_login'
go
Linchi
"Adam Sankey" wrote:

> Hello, I have a problem with adding users to a database using sp_adduser.
> The user I'm using is a member of db_owner but I receive the following error:
> sp_adduser adam, adam, DEFAULT_USERS
> Server: Msg 15247, Level 16, State 1, Procedure sp_adduser, Line 35
> User does not have permission to perform this action
> It only works when I log in as a System Administrator. However if I login as
> the db_owner account which generates the above error and run the following:
> exec sp_grantdbaccess adam
> exec sp_addrolemember DEFAULT_USERS, adam
> It works fine. The problem is that it is a piece of 3rd party software that
> is trying to add the users and won't be easy to get them to change it as
> sp_adduser should work. Also I don't want them logging in as System
> Administrator when I could try and fix it. Any ideas?
>
|||Thanks very much that worked fine - I still don't understand why I had this
problem in the first place. Do you have an insight in to this?
Thanks again
Adam
"Linchi Shea" wrote:
[vbcol=seagreen]
> One solution is to drop the user from the database, and then make its login
> the owner of the database:
> sp_dropuser 'the_user'
> go
> use the_database
> go
> sp_changedbowner 'the_login'
> go
> Linchi
> "Adam Sankey" wrote:

Error Adding User

Hello, I have a problem with adding users to a database using sp_adduser.
The user I'm using is a member of db_owner but I receive the following error:
sp_adduser adam, adam, DEFAULT_USERS
Server: Msg 15247, Level 16, State 1, Procedure sp_adduser, Line 35
User does not have permission to perform this action
It only works when I log in as a System Administrator. However if I login as
the db_owner account which generates the above error and run the following:
exec sp_grantdbaccess adam
exec sp_addrolemember DEFAULT_USERS, adam
It works fine. The problem is that it is a piece of 3rd party software that
is trying to add the users and won't be easy to get them to change it as
sp_adduser should work. Also I don't want them logging in as System
Administrator when I could try and fix it. Any ideas?One solution is to drop the user from the database, and then make its login
the owner of the database:
sp_dropuser 'the_user'
go
use the_database
go
sp_changedbowner 'the_login'
go
Linchi
"Adam Sankey" wrote:
> Hello, I have a problem with adding users to a database using sp_adduser.
> The user I'm using is a member of db_owner but I receive the following error:
> sp_adduser adam, adam, DEFAULT_USERS
> Server: Msg 15247, Level 16, State 1, Procedure sp_adduser, Line 35
> User does not have permission to perform this action
> It only works when I log in as a System Administrator. However if I login as
> the db_owner account which generates the above error and run the following:
> exec sp_grantdbaccess adam
> exec sp_addrolemember DEFAULT_USERS, adam
> It works fine. The problem is that it is a piece of 3rd party software that
> is trying to add the users and won't be easy to get them to change it as
> sp_adduser should work. Also I don't want them logging in as System
> Administrator when I could try and fix it. Any ideas?
>|||Thanks very much that worked fine - I still don't understand why I had this
problem in the first place. Do you have an insight in to this?
Thanks again
Adam
"Linchi Shea" wrote:
> One solution is to drop the user from the database, and then make its login
> the owner of the database:
> sp_dropuser 'the_user'
> go
> use the_database
> go
> sp_changedbowner 'the_login'
> go
> Linchi
> "Adam Sankey" wrote:
> > Hello, I have a problem with adding users to a database using sp_adduser.
> > The user I'm using is a member of db_owner but I receive the following error:
> >
> > sp_adduser adam, adam, DEFAULT_USERS
> >
> > Server: Msg 15247, Level 16, State 1, Procedure sp_adduser, Line 35
> > User does not have permission to perform this action
> >
> > It only works when I log in as a System Administrator. However if I login as
> > the db_owner account which generates the above error and run the following:
> >
> > exec sp_grantdbaccess adam
> > exec sp_addrolemember DEFAULT_USERS, adam
> >
> > It works fine. The problem is that it is a piece of 3rd party software that
> > is trying to add the users and won't be easy to get them to change it as
> > sp_adduser should work. Also I don't want them logging in as System
> > Administrator when I could try and fix it. Any ideas?
> >

Error Adding User

Hello, I have a problem with adding users to a database using sp_adduser.
The user I'm using is a member of db_owner but I receive the following error
:
sp_adduser adam, adam, DEFAULT_USERS
Server: Msg 15247, Level 16, State 1, Procedure sp_adduser, Line 35
User does not have permission to perform this action
It only works when I log in as a System Administrator. However if I login as
the db_owner account which generates the above error and run the following:
exec sp_grantdbaccess adam
exec sp_addrolemember DEFAULT_USERS, adam
It works fine. The problem is that it is a piece of 3rd party software that
is trying to add the users and won't be easy to get them to change it as
sp_adduser should work. Also I don't want them logging in as System
Administrator when I could try and fix it. Any ideas?One solution is to drop the user from the database, and then make its login
the owner of the database:
sp_dropuser 'the_user'
go
use the_database
go
sp_changedbowner 'the_login'
go
Linchi
"Adam Sankey" wrote:

> Hello, I have a problem with adding users to a database using sp_adduser.
> The user I'm using is a member of db_owner but I receive the following err
or:
> sp_adduser adam, adam, DEFAULT_USERS
> Server: Msg 15247, Level 16, State 1, Procedure sp_adduser, Line 35
> User does not have permission to perform this action
> It only works when I log in as a System Administrator. However if I login
as
> the db_owner account which generates the above error and run the following
:
> exec sp_grantdbaccess adam
> exec sp_addrolemember DEFAULT_USERS, adam
> It works fine. The problem is that it is a piece of 3rd party software tha
t
> is trying to add the users and won't be easy to get them to change it as
> sp_adduser should work. Also I don't want them logging in as System
> Administrator when I could try and fix it. Any ideas?
>|||Thanks very much that worked fine - I still don't understand why I had this
problem in the first place. Do you have an insight in to this?
Thanks again
Adam
"Linchi Shea" wrote:
[vbcol=seagreen]
> One solution is to drop the user from the database, and then make its logi
n
> the owner of the database:
> sp_dropuser 'the_user'
> go
> use the_database
> go
> sp_changedbowner 'the_login'
> go
> Linchi
> "Adam Sankey" wrote:
>