Documentation
Back to website >

Startup error

Error when starting"Line with duplicate key"

EULANDA does not start. One of the following error messages is displayed. This error only occurs for individual users on specific PCs. The error occurs only in connection with a program update, a new user or new hardware.

Native Error 512
The subquery returned more than one value. This is not allowed if the subquery follows =, !=, <, <=, > or >= or is used as an expression.

native error 512
Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.

 

Debonding

Execute the following SQL command until the results area shows that none or zero rows are affected:

update cnProcesses
set program_name = RTRIM(program_name) + 'X'
where id in (
select min(id)
from cnProcesses
group by
uid, sid,hostname,program_name,nt_domain,nt_username,net_address,net_library,loginame
having count(*)>1
)

Database owner is a Windows user

EULANDA does not start - not even as administrator. One of the following messages or a similar message appears when starting the program - if necessary also elsewhere in the program:

Message 15517
The execution as database principal is not possible
because the principal"dbo" is not available, no identity change is possible for this type
of principal, or you do not
have the required authorization.

Message 15517
Cannot execute as the database principal because the
principal "dbo" does not exist, this type of principal cannot
be impersonated, or you do not have permission.

In other cases EULANDA® can be started, but certain functions - for example copying addresses - fail. The above or following message is then displayed:

Message 15404
Information about Windows NT group or user'dbo' could not be retrieved, error code 0xffff0002.

Message 15404
Could not obtain information about Windows NT group\user 'dbo', error code 0xffff0002.

 

Possible cause

The database owner is not the predefined SQL Administrator"sa", but a Windows logon name. This is the case, for example, if no logon name was entered when creating the database. In this case, the logged on Windows user is stored as the database owner.

Check the currently stored database owner

To find out the currently stored database owner in SQL Management Studio, right-click the database and select Properties.

Alternatively, you can determine the owner using the following SQL command. You can execute this in the EULANDA SQL Designer, for example:

select suser_sname(owner_sid) 
from master.sys.databases 
where database_id = db_id()

select suser_sname(sid) 
from sys.database_principals 
where name = 'dbo'

Both queries must result in"sa". Although the case that the expenses differ is rarer.

Debonding

Change the database owner to"sa".

To do this, the following SQL command must be executed. Before making any changes, make a backup of your entire system.

sp_changedbowner @loginame ='sa'

Technical background

Some server-side procedures have been created with the EXECUTE AS clause - as in the following example:

ALTER PROC [dbo].[ProzedurName]
with execute as owner
AS
SET NOCOUNT ON
(...)