So I am trying to get the new sonar viewer to work. When I add an .sl2 file, and try to "edit" it, I get the error message:

Unhandled Exception:

Could not find a part of the path ****sl2.sl2'. (I've removed the path).


at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
at #=q6eEXuSEP37z5wl50xZsjD7suSWiO5rc2VpWIB3KE7BaMXxUN9YUhp_3z0BWt6WWx3XjggQaiaYEqurYbM$Q$Kw==.#=q2EIX4Ou8BCjdfxSElrNzAmAcROujla4NhOA4X0tSAhQ=(String #=qkZLc2bwL7ok0pLbSkBZMFQ==)
at #=q6eEXuSEP37z5wl50xZsjD7suSWiO5rc2VpWIB3KE7BaMXxUN9YUhp_3z0BWt6WWx3XjggQaiaYEqurYbM$Q$Kw==.#=qbDufIhWfee7QXPtmAvjAmeOIqvcpdATUW8ElIJC8O1w=()
at #=q6eEXuSEP37z5wl50xZsjD7suSWiO5rc2VpWIB3KE7BaMXxUN9YUhp_3z0BWt6WWx3XjggQaiaYEqurYbM$Q$Kw==..ctor(#=q6QOnCOuaIScqYKjPLbHdGwXc55vHRG16RC6LzTSJV_R31lBEDHEVfzj_LkpiEPkRVBG3OYSqVfnXaRbWRBSSDA== #=qHLb9m197mVV190baAFoTAw==, #=qblz46DDkgWdpU6RMUn7EJi4d1IuDQfVAiLXsHwWkiEo= #=qhDBwF9oCH32dGuzLSnIO1g==)

Click close and then another unhandled exception pops up, and then another. I can pass these along too if it helps with troubleshooting.

Thanks,
Craig

Oh yeah, and when I try to look at the sonar, I see nothing for any of the various channels. I know there is data, because I can see it in Dr. Depth.

Cheers,
Craig

Hi Craig,
That's interesting. Is the sl2 file being added from a memory card or the local disk?
So you are importing a sonar log, and immediately going to edit it and getting this error? In the import window, does the track show as having track-points ("Elements" column non-zero) ?

Also, the original sonar log file must be available when using the sonar viewer - is there any chance it has been removed, or the path become unavailable? This *should* be checked in the edit track window, and the sonar button disabled if the file is not found, but one (slim) possibility is that the file has been removed once the track edit window has been opened, and we are not catching that properly.

thanks,
Matt

Hi Matt,

The .sl2 is on the local disk. I should clarify also that this is happening for every .sl2 file that I have tried so far (5 or so). I import one, and when I click "edit", the sequence of errors pops up. The elements columns for all the .sl2s contain non-zero value (e.g. 1127) during the import process.

Nothing has changed with regards to the path, nothing should be inaccessible. Once the errors are bypassed the track shows up in the edit window. If I click on the sonar button, nothing is displayed. However, if I click "show track points", they show up on both the primary and downscan channel.



One thing that I should probably mention is that for all my files, I have gone through the Dr. Depth "Sonar Lab" process, to filter/correct the assigned depths based on the visual signal return patterns. So each .sl2 has been edited....I hope this isn't the root of the issue, because I have done this to all of my files to improve the accuracy.

Thanks

Thanks Craig,
I don't know what the DD process does to the files (I assume it just replaces the depth values), but if the file imports into RM OK then that is unlikely to be the problem.
I'm wondering now if there is something about the path to your files which the sonar viewer doesn't like, since the error that you are getting is that the file cannot be found. It's odd though, because we do a pre-check when the track is opened for editing, and if a "file exists" call fails for the sonar file, then we don't enable the sonar button (or try to load sonar).
It's also possible that there is an issue with the way the file path has been stored in the RM DB.

What would be useful now is to get an example of full path of one of these files, along with the full text of the error message (including the full path of the file that it is trying to open). If you don't want to put that on the forum, please send to This email address is being protected from spambots. You need JavaScript enabled to view it. .

thanks,
Matt

Craig,
This is fixed in the latest maintenance release. The issue was apostrophe characters in the file path not being correctly retrieved from the database. You should not need to reimport any files.
Matt