This should be an easy one.....I run 3.4.1 loggernet admin on my server which can't collect from one of our new 200x installs....I can see it and timecheck but it hangs on downloading the tables. I can collect with 4.0 w/o problems. I figure 3.4.1 doesn't have any lib files.....what and where do I have to copy files into my 3.4.1 instance to recify this, short of switching everything over to 4.1 to accomodate the 200x station (59 station network). thanks
when connecting to the cr200x, try forcing update of the table definitions using one of the menu options in connect. if it still fails, get a copy of your loggernet logs and contact your campbell office.
thanks very much Sam for your reply....our csi office says probably due to virtual server (but I run 510's, 10x's (with table OS's), CR200's, 1K's and 800's with no problem on 3.4.1)) When I look at the comm log for the table def transaction....it fails....sometimes it brings down 2 of the 3 tables on the logger, but always hangs on the third.......
"Read table degs failed","Unsupported field type specified", then receives a bit and says "Read table defs failed","Db::ColumnDef::add_piece--invalid piece added"
When I dig deep I can see it downloading OS vers also which 3.4.1 doesn't know (CR200x ver2)
guess I'm toast....really wish CSI would support WIN server...
Thanks again for your help Sam, short of trying to work out the kinks with LN 4 on the virtual slice, I guess I can go on a local box with LN4 and collect the data, post it up to an ftp site, download from Virtual instance of 3.4.1 and bring it into RTMC as a file.....I may have to replace header to do it though.
cheers
Mike
Please try commenting out the offending 3rd table and retrying. If all is well, try reordering the tables to see if the update process is affected by the order. If so, then we need to get a copy of the CR200X program and dig into what is going on with that 3rd table def. Based on your description, it doesn't seem logical to say this is related to a WIN server or virtualization issue. On that note we have customers running LN on WIN servers and in virtualized environments.