Online Database

sure you online?

As we speak I am ripping CDs and AMG is working fine. It must be something to do with your setup.

In System, System Status is 'Internet Accessible = True  ?  

If not, that's why.  If so, power cycle your HDX/US.

(BTW don't forget to keep your fingers crossed while checking   )

Thanks for the replies. Internet status is true and has been since last software upgrade. The CD lookup service version in system settings is  4.05.31 and I assume this is perfectly normal. I also checked the system messages for ripping and all say "a better match was found using FreeDB" so I assume it quickly passed over AMG and I didn't spot it. I'll check carefully next time I do a rip.

Tim

Adding to odd things with the Unitiserve.

The Up Time clock seems to be counting backwards at least the hours and minutes do. Currently it is at -22 days, -12 hours, -42 minutes, -33 seconds. Just noticed this and with the scan date and time of my network share being 1753-01-01 and the time being 00:00:00 I am wondering if the internal clock is screwed up?

Do others have this on their unit. I emailed Naim over a month ago about the date and time issue but have not heard anything back.

Tim

It just gets worse. Now I've lost a load of ripped albums. They are on the NAS (thank goodness) but loads seem to have gone missing. I have now demoted the store to a share and am rescanning it and hope to promote it to a store when it's done.

I'm really getting pissed off with this bloody product, for gods sake NAIM what happened to the reliability aspect!!

Tim

Are you sure you are online?

I asked before, I'll ask again.

If you set an IP on it, I would be pointing a dirty little stare at the DNS settings, because it seems you are LAN, but not WAN.

Yep it is online and the system reports that the network store is scanning it. The application reports 1087 albums but only shows 536. The network share which is on the same device is online and showing all 97 albums.

Tim

Did you recently update to 1.7a? I know a few serves have had issues when the 1.7a update has not been applied correctly and they do funny things like thinking they are now HDX's.

Interesting you mention that. I'll keep an eye on the unitiserve.

In the meantime I think I have resolved the issue by shutting down the unitiserve and then rebooting the NAS and then re-starting the unitiserve when the NAS was back up to speed. Both share and store were scanned and are functioning normally. The uptime is now reporting normal time and not in a negative context.

But I wonder why/how this happened in the first place.

Tim

Lots of people miss the step after each disc ejection reboot you should shut it down then power it back up. I am guessing you may not have shut it down after it rebooted after the 1.7a disc was ejected?

Hi - yes I have completed the 1.7a update correctly and did the shutdown etc.

It would be tempting fate but I wonder if it might be beneficial to run the 1.7a update again and see what happens. I will check with Naim and ask about the risks.

Tim

It sounds like some of those issues have resolved, in which case I'd not do anything!  Well I would do one thing -- shut it down again, start it up, and see how it goes.  If all proceeds . . . you are all set.

I'm not sure how long it takes, or is supposed to take, the uServe to "see" a share (or store for that matter) that is on a nas that is not on the network.  In other words, if you boot up the uServe, and the nas is offline, then you boot up the nas, how long does it take the uServe to see it?  I'm not sure what the "right" answer is.

Even if the automatic share discovery is quite ok, I have started to always enter the important ones manually (''add network shares''). It is faster and in many Apple environments I have had to troubleshoot, the only way (I have found...)  to do it. You just copy and past the full path from Finder to N-Serve for MAC or Explorer to DTC.

Thanks for the comments guys. 

Entering the NAS share path manually is quite easy I just type it in for example \\spooky\mymusic and then it connects, scans and updates and there we have it. The problem is that the scan date and time for those shares added manually is 1753-01-01 and time 00:00:00 which doesn't affect sound or access quality but implies the unitiserve is not working as it should. The system date and time on the unitiserve is perfect.

Tim