SQL2005 & network error

[MAJA]

I transfered a .EAP to SQL2005
I'm a admin on the SQLserver machine and can connect to the project. So far so good.

Now another user tries to connect to the project
following the 'Connect to a SQL Server Data Repository' procedure...
- The user tries to connect using Windows Integrated security.
- The Test Connection (step 7) succeeds.
- Steps 8 through 11 also complete
The user presses the Open button and a messagebox pops up:
'Enterprise Architect has experienced a network error and will close down.'

I can connect to the project so the EAP was transferd to SQL2005 correctly.
The connection test worked ok for the user so he has access to the EAdb.

What's wrong?
Has any body else experienced these problems?
Are there any other privileges needed for this user?
Please Help!


SQLserver...
I've created a windows login for this user on the SQL server
The login has the server role public
The login has access to the EAdb
The login has been assigned all database roles for the EAdb

Version info ...
EA (Corporate Edition)
7.0.815
Microsoft SQL Server Management Studio
9.00.3042.00
Microsoft Analysis Services Client Tools
2005.090.3042.00
Microsoft Data Access Components (MDAC)
2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML
2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer
7.0.5730.11
Microsoft .NET Framework
2.0.50727.832
Operating System XP SP2
5.1.2600

[MAJA]

addition...

The user can connect if I give him the server role 'sysadmin'

The system admin for the SQLserver won't allow this
setting. I can't say I can blame him.

Is there any middle ground?
Why does EA need this ridiculous high access?

[Martin Terreni]

If he can open project with sysadmin then it is probably a permissions problem.
I work with MSSQL2005 but I went for a different approach, the  login user is the db owner and it is the same log in for all users of the project.
Try to see if one of the users can connect through MSSQL client with  the log in you created for him, and that he is capable of read\write on all tables.
If he isn't then there is your problem. If there is no problem I would suggest to turn to Sparx support.

[MAJA]

Got it running with a SQL user account.
steps

[*]create new DB
run script base model on new DB
transfer data to DB
add SQL user
map SQL user to DB
add data read and data write roles to mapped DB user
[/list]

Did not find a real cause for my earlier problems though.

Testing for user access to the database from within SSMS helped.

Thanks for the suggestion.

[Martin Terreni]

Wellcome