Lightswitch works on a local server instance but not on network db instance

[Former Member]

New Microsoft vs 10 Lightswitch works on a local server instance of SQL Anywhere 11.0.1.2634 using the entity framework but fails on network db instance. Tried changing and or using the same dsn name.. Local database development works great. But when I change to network server instance it cannot return the data.. I assume it is going thru WCF Ria in the background. I am not sure if it is the connection path of the EDM model not being in the weg config or whatever.. Same issue with WCF Ria services in Silverlight project.

[MarkCulp]

Please give us some more information: How are you starting your database? What is your connection string (or DSN settings)?

[Former Member]

The connection string is the DSN connectionString="DataSourceName=powershop" a database server or connectionString="DataSourceName=powershoplocal" my development server

I have been working with Lightswitch lab against a Sybase SQLAnywhere 11.0.1.2634 database on my local development machine both 2 tier and 3 tier (ria). It works great on local workstation connection using DSN name but not against a server connection same (both same EDM 2634). Has anyone else experienced this? I can get a silverlight RIA soltuion to work against a server DB instance by changing the dsn name but not in lightswitch. I have tried changing the connection string on deloyment for the 2 tier also.

[Former Member]

The connection string is the DSN connectionString="DataSourceName=powershop" a database server or connectionString="DataSourceName=powershoplocal" my development server

[MarkCulp]

Ok, so what is in your DSN? I.e. you are going to have to give us more information in order for anyone to help you. How are you starting your network server - give us your command line (options)? Have your read through the troubleshooting connections section in the docs? http://dcx.sybase.com/index.html#1101/en/dbadmin_en11/conhow.html

[former_SQLA_member1694868]

You might check if other communication to the db across the network is working. Perhaps set up an ODBC connection to the database and test that.

You could also ensure that the firewall on the remote machine is either turned off or allowing your traffic to hit the db.