ODBC errors - Foundscan
Having trouble connecting to Foundscan DB. I have an LS non EA implementation and have followed the documentation to the letter, but I get the following error:13 2009/09/29 15:09:01.792 EDT 10.5.0.160 %NIC-1-919010: NIC:McKessonDDC:McKessonDDC-AS1 stamp=Sep 29 12:07:47 type=1603 level=1 niccategory=16 event_category=1603110000 addr=10.122.0.161 deviceclass=Network.System msg_id=605102 view_id=40e82b37-e62b-460d-b8b5-79f7df54fcd9 view_name=NIC-View-ATL device_id=52bcfa83-6495-4eaa-bee9-434d07f32c7c lp=10.122.0.161:6316:120817443 status=0 coreid= ipmatch=0 ip_addr_1= ip_count_1=0 ip_addr_2= ip_count_2=0 ip_addr_3= ip_count_3=0 device_type=100 source_ipr= destin_ipr= msg=%NIC-3-605102: ODBC, ODBC, -, -, -, -, Detail: 3632: foundscan:Rsa09ENV77atabase connection failed: dsn=foundscan, uid=Rsa09ENV77, retcode=-1, sqlstate=IM002, native_error=0, msg=[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
The Test on the LC DSN worked fine. Anyone seen this before?
You check the DSN spelling, ensure its the VIP if its a MS cluster on the Foundscan? Load sql tool on the LC and test the connection and pull using the same credentials? Check the logs on the foundscan box itself? You are using the 32bit ODBC connection on the appliances correct? Default MS SQL driver right?
Going by the error you are getting, check if you are making the DSN in envision. I got this error once bcoz i made the DSN in the founscan device itself. Back then i didnt know what a DSN was .
Other things you can check .
1. Port 1433 b/w envision and sql database is open.
2. User credentials have db_owner and db_denywriter priviledges
3. Add the foundscan DSN details in asset services. And then check assets tab -> browse assets -> browse to see if ou are getting anything.
4. Check if you have reports in the sql table. If not, try generating.
On the Envision Appliance go into ODBC Sources (32-Bit) and go to your DSN. Test your connection. This will help you eliminate the Windows part as the issue. If you successfully connect then you can move to the Envision configuration and make sure you have everything correct there.