Book a Demo

Author Topic: SQL Server Problem  (Read 5687 times)

PostMsg

  • EA Novice
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
SQL Server Problem
« on: June 30, 2004, 06:41:54 am »
I am trying to connect to a SQL Server database from the lastest version of EA.

All the prompts seem to work except (Connection OK), but when I get to the last one where it asks you to enter the server user name and password, it doesn't work.

The message is that the ODBC configuration is invalid (even though it connected fine in the earlier steps).

The ODBC connection I set up also succeeded.

Any ideas what's wrong?

Thanks in advance!!!

AdamHearn

  • EA User
  • **
  • Posts: 58
  • Karma: +0/-0
    • View Profile
Re: SQL Server Problem
« Reply #1 on: June 30, 2004, 10:04:42 am »
What happens if you try using an OLEDB connection?

Simple to follow steps in case you're unsure!

Click on "Connect to Server Repository..."
The Data Link Properties dialog appears
From the list, select Microsoft OLE DB Provider for SQL Server
Press Next
1. Enter or select the SQLServer instance where your model is stored
2. Choose the required authentication method (Windows Integrated or SQLServer controlled).
3. Choose the Database that contains your model.
Test the connection. All should be fine if you've setup the previous steps correctly.
Close the Data Link dialog
Enter a name for the Repository
Press OK

EA should connect and present the model.

« Last Edit: June 30, 2004, 10:06:02 am by AdamHearn »

PostMsg

  • EA Novice
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Re: SQL Server Problem
« Reply #2 on: June 30, 2004, 11:11:53 am »
The connection part works (with "Connection Succeded"), but then whether I use the OLE DB for SQL Server or the OLE DB for ODBC, I am asked *AGAIN* for a password.

In either case, that is, for OLE DB for SQL Server or OLE DB for ODBC, I get the following message after entering the password the second time.

"Invalid Object Name: usys_system"

Then, EA coughs up a lung and exits....

:(

There was another posting with exactly this same issue.

Any ideas what's causing this?

Thanks.

AdamHearn

  • EA User
  • **
  • Posts: 58
  • Karma: +0/-0
    • View Profile
Re: SQL Server Problem
« Reply #3 on: June 30, 2004, 12:28:19 pm »
If you are asked again for a password, it suggests that the OLEDB client cannot authenticate with the SQLServer instance. If this is the case, I think you'll find that it is actually asking for the SA password to the DB you specified.

This is exactly the same scenario I have when I VPN in to work. The SQLServer instance is setup for Windows authentication but as I'm a VPN connected client my client credentials are not good enough. However, I use the SA password - which is not the default blank ;) when I'm prompted for the password and connection to the repository is fine.

As for getting the error "Invalid Object Name: usys_system"... this means you've *not* chosen a SQLServer DB that contains an EA repository. You need to create the repository structure 1st or perform a data transfer EAP->RDBMS before you can use it!

Hope that helps.

PostMsg

  • EA Novice
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Re: SQL Server Problem
« Reply #4 on: July 01, 2004, 06:35:39 am »
Thanks for your reply.

I suppose I was thinking that EA would also double as an ERD design and deploy tool.

However, it is too complicated to get this working for ERD if it *can* be used that way.

Again, thanks very much for your kind reply. <s>

AdamHearn

  • EA User
  • **
  • Posts: 58
  • Karma: +0/-0
    • View Profile
Re: SQL Server Problem
« Reply #5 on: July 01, 2004, 11:56:02 am »
Not sure I understand your last post. You can indeed use EA to be an ERD tool. It can forward or reverse engineer a DB schema. The forward engineer is through the creation of SQL scripts that contain the dialect of SQL DDL for use with the chosen DB engine.

None of that has anything to do with your connection problems. Please explain what you want to acheive and you'll get some answers.

thomaskilian

  • Guest
Re: SQL Server Problem
« Reply #6 on: July 01, 2004, 05:19:51 pm »
« Last Edit: July 01, 2004, 05:20:48 pm by thomaskilian »