Cannot make changes in FM Model after datasource change

[fml55555]

Hi Gurus,

I have a FM model built on a datasource X. I had to change the datasource to X2. Both these datasources have the same structure (it is basically the same DB but I had to change it as the second one refreshes more often). After the change I am unable to modify the model in any way(no new connection or even testing the query subjects). I get the error

QE-DEF-0285 The logon failed.
QE-DEF-0322 The connection string is invalid.
RQP-DEF-0068 Unable to connect to at least one database during a multi-database attach to 1 database(s) in:
US_EDW_LONDON

UDA-SQL-0031 Unable to access the "US_EDW_LONDON" database. Check that the connection parameters to the database are configured correctly. For example, ensure that the data source connection contains the signon information, such as a password, to connect to the database.
UDA-SQL-0534 Invalid connection string.
UDA-SQL-0206 The OLEDB driver returned the following value: HRESULT= -2147221164".

I did some digging and found that the earlier connection(X) had

Type: microsoft SQL server (microsoft SQL server (OLE DB)

and the current one has

Type: microsoft SQL server(SQL 2008 Native Client)

I found this in IBM Docs : http://www-01.ibm.com/support/docview.wss?uid=swg21647579


On my PC I do not have "SQL Server 2008 R2". Is this the reason for the whole thing?

One more thing, A friend on mine has this on his PC and he is able to access the Model just fine.

Thank you!

[bi4u2]

I always select OLE DB when I create a connection to a SQL DB. Are you able to recreate your new datasource using the OLE DB one and see if that works?

[MFGF]

On my PC I do not have "SQL Server 2008 R2". Is this the reason for the whole thing?

One more thing, A friend on mine has this on his PC and he is able to access the Model just fine.

Yes. You need the SQL Server 2008 client libraries installed locally on your PC to be able to connect from within FM.

MF.

[fml55555]

Thank you so much guys !! It worked. I loaded the SQL and I was able to edit it!