You are viewing limited content. For full access, please sign in.



A SQL error has occurred. (A SQL error has occurred.) (LMO28)

asked on September 18

Hi guys,

I have been trying to make a sql connection to the LFDS server and I receive this error msg -- >"A SQL error has occurred. (A SQL error has occurred.) (LMO28)".

My sql server is on a different server and my LFDS is installed in a different server. But I can successfully telnet from my application server to the database server which ensures that there is no communication problem between the two. 

I have attached a screenshot of the settings I am trying to enter in the fields.

Can someone please guide me how to make a successful connection?

Error.png (35.94 KB)
0 0


replied on September 18

Does event viewer give any clearer error message?


I have also seen that issue when there are login issues. Has the server been configured for mixed mode authentication? More often than not when I get that error it is set to windows auth only.

2 0
replied on September 18

System.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)


this is the event viewer's log. 


the serve is configured for mixed mode authentication

0 0
replied on September 18

Is the SQL using a named instance? In your example, is it running as something like\SQLExpress or\Laserfiche


What port is the SQL server using? I would try explicitly declaring the port. I believe forms defaults to trying on 1433, but I could be wrong. In this case you would try or\(InstanceName) 

1 0
replied on September 19

Hi Brett, 

Our SQL server was configured only for windows authentication which caused the problem. Thank you so much :-)

0 0


You are not allowed to reply in this post.
You are not allowed to follow up in this post.

Sign in to reply to this post.