→ Having trouble accessing our new support portal or creating a ticket? Please notify our team here

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Noobmode
Engaged Sweeper III
Microsoft SQL Server 2014 SP3 CU1
Lansweeper 7.0.151.4

SQL lives on a different server than Lansweeper. All permissions appear to be correct on the database and the user being utilized to scan has local administrator permissions on the endpoints.

All systems display this error: Column 'AssetID' does not belong to table

I was unable to find a thread with this specific error outside of an old lansweeper post: https://www.lansweeper.com/forum/yaf_postst2710_Column-nonactive-does-not-belong-to-table-theTable.aspx#post12727

I am using collation Latin_General_CI_AI and there are no issues with memory or CPU.

I believe this issue may have started to occur once the database was moved from SQLCompact to 2014. I followed the KB and have verified that all steps were taken.
1 ACCEPTED SOLUTION
Esben_D
Lansweeper Employee
Lansweeper Employee
I've seen this before when the database connection is giving some errors. So I would recommend following the steps in this KB article: https://www.lansweeper.com/knowledgebase/a-network-related-or-instance-specific-error-occurred/

View solution in original post

4 REPLIES 4
Esben_D
Lansweeper Employee
Lansweeper Employee
Best to open a ticket. The errorlog might contain errors that indicate a cause.
Noobmode
Engaged Sweeper III
Thank you for the reply and information.

I reviewed that document and all of my settings are inline with the document. Any other ideas or should I open a ticket with support?
Esben_D
Lansweeper Employee
Lansweeper Employee
I've seen this before when the database connection is giving some errors. So I would recommend following the steps in this KB article: https://www.lansweeper.com/knowledgebase/a-network-related-or-instance-specific-error-occurred/

Noobmode
Engaged Sweeper III
Esben.D wrote:
I've seen this before when the database connection is giving some errors. So I would recommend following the steps in this KB article: https://www.lansweeper.com/knowledgebase/a-network-related-or-instance-specific-error-occurred/



I wanted to provide an RCA on my issue.

So it turns out the db server uses an iSCSI vlan on a separate NIC to serve the database files from a LUN. The IP information for that vlan was missing from the SQL Server TCP/IP settings completely. We believe it was the iSCSI NIC was added after SQL server was set up. So I had to add that IP to the TCP/IP list in SQL Configurations to resolve the error after support gave me this same step as a first step.