|
Please help...subnet and rescan issue..drive mapping
|
|
22-02-2021, 13:45
Post: #1
|
|||
|
|||
|
Please help...subnet and rescan issue..drive mapping
I'm at my wit's end.....I'm using a QNap with Minimserver to play music from my Naim NDX streamer. It's been in use for about a year and it's been sweet...sounds great and then..... about a month ago Minimserver stopped working in terms of refreshing. It still works but won't rescan or update library and comes up with a subnet issue. I've tried removing my avast upgraded anti virus incase there was Java issue...to no avail. I've tried remapping and I've got to a point now where Minimserver will see the Qnap and refresh but has re-desgnated as Minimserver (mypc) rather than Qnap as server so it will only work now when the PC is on....and it sees the whole of my PC which I don't want...any ideas?
![]()
|
|||
|
22-02-2021, 15:30
Post: #2
|
|||
|
|||
|
RE: Please help...subnet and rescan issue..drive mapping
Are you still seing the subnet issue? If so, what is the complete exact wording of the message you are seeing?
The best approach for your setup is to run MinimServer on the QNAP and run MinimWatch (not MinimServer) on your PC. At the moment, it sounds like you are running both MinimWatch and MinimServer on your PC and this can be confusing because the system tray icons and the menus for these icons look similar. The first step towards resolving the problem with the QNAP is to find the MinimWatch minim icon in your Windows system tray. You can tell which this is because when you right-click on it, the menu has some extra choices: Close, Options and Refresh. The MinimServer minim icon menu does not have these options. From this menu, select Options > Show log (watch). This opens the MinimWatch log window. Check that you have the correct window by looking in the title bar, which should say "MinimWatch Log". Copy and paste the contents of this log window into a post here. |
|||
|
22-02-2021, 16:22
Post: #3
|
|||
|
|||
RE: Please help...subnet and rescan issue..drive mapping
(22-02-2021 15:30)simoncn Wrote: Are you still seing the subnet issue? If so, what is the complete exact wording of the message you are seeing? It’s about 500 Plus lines long |
|||
|
22-02-2021, 17:15
Post: #4
|
|||
|
|||
| RE: Please help...subnet and rescan issue..drive mapping | |||
|
22-02-2021, 20:12
Post: #5
|
|||
|
|||
|
RE: Please help...subnet and rescan issue..drive mapping
I hope you can make more sens eof this than I can....As requested; first lot:
15:19:14.574 main: setFile: logFileName=minimwatch.log append=false 15:19:14.576 main: setFile: logFile is C:\Users\Sam\AppData\Roaming\MinimWatch\data\minimwatch.log 15:19:14.576 main: setFile: logDir is C:\Users\Sam\AppData\Roaming\MinimWatch\data 15:19:14.576 main: saveProperty: compName=null propName=configVersion propValue=2.0.134 15:19:14.576 main: getSaveValue: compName= propName=configVersion propValue=2.0.134 saveValue=2.0.134 15:19:14.577 main: writeConfigProperty: propFullName=.configVersion propValue=2.0.134 15:19:14.589 main: updateActiveProfile: propFullName=.configVersion 15:19:14.589 main: active modules: [C:\Users\Sam\AppData\Roaming\MinimWatch\libext\ohnet(windows)-1.30.3937.zip, C:\Users\Sam\AppData\Roaming\MinimWatch\libext\minimui-2.0.122.jar, C:\Users\Sam\AppData\Roaming\MinimWatch\libext\jminim-2.0.134.jar, C:\Users\Sam\AppData\Roaming\MinimWatch\libext\minimscript$-2.0.104.jar, C:\Program Files\MinimWatch\lib\minimwatch-2.0.102.jar, C:\Users\Sam\AppData\Roaming\MinimWatch\libext\minimlaunch$-2.0.103.jar] 15:19:14.590 main: inactive modules: [C:\Program Files\MinimWatch\lib\minimui-2.0.113.jar, C:\Program Files\MinimWatch\lib\jminim-2.0.119.jar, C:\Program Files\MinimWatch\lib\ohnet(windows)-1.28.3736.zip, C:\Program Files\MinimWatch\lib\minimlaunch$-2.0.102.jar, C:\Program Files\MinimWatch\lib\minimscript$-2.0.102.jar] 15:19:14.590 main: packages: [C:\Program Files\MinimWatch\lib\minimwatch-2.0.8.jmpkg, C:\Users\Sam\AppData\Roaming\MinimWatch\libext\minimwatch-update-90.jmpkg] 15:19:14.591 main: package minimwatch-2.0.8 adding conflict package {ge}minimwatch-0.8-update-1 15:19:14.591 main: package minimwatch-2.0.8 adding conflict package {le}minimwatch-update-81 15:19:14.591 main: package minimwatch-2.0.8 adding removal package {ge}minimwatch-0.8-update-1 15:19:14.591 main: package minimwatch-2.0.8 adding removal package {le}minimwatch-update-81 15:19:14.591 main: package minimwatch-update-90 adding required package {ge}minimwatch-2.0.8 15:19:14.592 main: checkRequiredPlatform: packageName=minimwatch-2.0.8 platform=null platforms= 15:19:14.592 main: checkRequiredProduct: packageName=minimwatch-2.0.8 product=windows products= 15:19:14.592 main: checkConflictPlatform: packageName=minimwatch-2.0.8 platform=null platforms= 15:19:14.592 main: checkConflictProduct: packageName=minimwatch-2.0.8 product=windows products= 15:19:14.592 main: checkPackageLicenseType: packageName=minimwatch-2.0.8 licenseTypeConflict= 15:19:14.592 main: checkPackageUpdatesExpiry: packageName=minimwatch-2.0.8 packageDate= 15:19:14.592 main: isRemovalRequired: packageName=minimwatch-update-90 15:19:14.592 main: isRemovalRequired: removeName=minimwatch-0.8-update-1 comparator={ge} 15:19:14.592 main: isRemovalRequired: removeName=minimwatch-update-81 comparator={le} 15:19:14.592 main: isRemovalRequired: packageName=minimwatch-update-90 15:19:14.592 main: checkPackageLicenseType: packageName=minimwatch-update-90 licenseTypeConflict= 15:19:14.592 main: checkPackageUpdatesExpiry: packageName=minimwatch-update-90 packageDate= 15:19:14.593 main: validating extension package minimwatch-update-90 Last lot: 15:35:58.018 Thread-33: checkConflictPlatform: packageName=minimstreamer-2.0.6 platform=windows platforms= 15:35:58.018 Thread-33: checkConflictProduct: packageName=minimstreamer-2.0.6 product=windows products= 15:35:58.018 Thread-33: ServerControl.isPackageRequired: packageName=ffmpeg-4.1-melco-2.0 15:35:58.019 Thread-33: isPackageRequired: ffmpeg-4.1-melco-2.0 is required 15:35:58.019 Thread-33: PackageManager: cached resourcePrefix is http://minimworld.com/ 15:35:58.089 Thread-33: checkRequiredPlatform: packageName=ffmpeg-4.1-melco-2.0 platform=windows platforms= 15:35:58.089 Thread-33: checkRequiredProduct: packageName=ffmpeg-4.1-melco-2.0 product=windows products=melco 15:35:58.090 Thread-33: RefreshPackagesPanel: refreshAvailPackageList returned true 15:35:59.363 Thread-34: TrayView: refreshing module list 15:35:59.363 Thread-34: TrayView: allModuleStatus=jminim-2.0.119.jar,Inactive+Original,jminim-2.0.134.jar,Active,minimlaunch$-2.0.102.jar,Inactive+Original,minimlaunch$-2.0.103.jar,Active,minimscript$-2.0.102.jar,Inactive+Original,minimscript$-2.0.104.jar,Active,minimui-2.0.113.jar,Inactive+Original,minimui-2.0.122.jar,Active,minimwatch-2.0.102.jar,Active+Original,ohnet(windows)-1.28.3736.zip,Inactive+Original,ohnet(windows)-1.30.3937.zip,Active 15:38:23.062 Thread-1: disposing properties dialog 19:08:58.459 AWT-EventQueue-0: TrayView: show log action 19:08:58.460 Thread-35: ServerControl: showLog action 19:08:58.460 Thread-35: Remote runtime log level: trace 19:08:58.509 Thread-35: ServerControl: setLogUpdates action, logUpdates=true 19:08:58.509 Thread-35: ServerControl: checkNewVersion action 19:08:58.509 Thread-35: doNextCheckNow: lastNewVersionCheck lastCheckedTime=0 19:08:58.509 Thread-35: getNonUpdatePackages result=[MinimWatch] 19:08:58.509 Thread-35: getProgramProperty progName=MinimWatch propName=.newVersion result= 19:08:58.509 Thread-35: getProgramProperty progName=MinimWatch propName=.newVersionURL result= 19:08:58.509 Thread-35: getProgramProperty progName=MinimWatch propName=.versionUpdate result= 19:08:58.509 Thread-35: getProgramProperty progName=MinimWatch propName=.versionUpdateURL result= 19:08:58.509 Thread-35: getProgramProperty progName=MinimWatch propName=.update result=minimwatch-2.jmupd 19:08:58.509 Thread-35: getUpdateProperties: updateFile=minimwatch-2.jmupd 19:08:58.510 Thread-35: PackageManager: cached resourcePrefix is http://minimworld.com/ 19:08:58.570 Thread-35: getProgramProperty progName=MinimWatch propName=.version result=2.0.8 19:08:58.570 Thread-35: getNewVersionInfo: newVersion= name=MinimWatch 19:08:58.570 Thread-35: TrayView: returning from showLog method 19:09:05.443 Thread-1: disposing log frame 19:09:05.466 Thread-1: ServerControl: setLogUpdates action, logUpdates=false 19:09:18.394 AWT-EventQueue-0: TrayView: show log action 19:09:18.394 Thread-36: ServerControl: showLog action 19:09:18.394 Thread-36: Remote runtime log level: trace 19:09:18.432 Thread-36: ServerControl: setLogUpdates action, logUpdates=true 19:09:18.432 Thread-36: ServerControl: checkNewVersion action 19:09:18.432 Thread-36: doNextCheckNow: lastNewVersionCheck lastCheckedTime=0 19:09:18.433 Thread-36: getNonUpdatePackages result=[MinimWatch] 19:09:18.433 Thread-36: getProgramProperty progName=MinimWatch propName=.newVersion result= 19:09:18.433 Thread-36: getProgramProperty progName=MinimWatch propName=.newVersionURL result= 19:09:18.433 Thread-36: getProgramProperty progName=MinimWatch propName=.versionUpdate result= 19:09:18.433 Thread-36: getProgramProperty progName=MinimWatch propName=.versionUpdateURL result= 19:09:18.433 Thread-36: getProgramProperty progName=MinimWatch propName=.update result=minimwatch-2.jmupd 19:09:18.433 Thread-36: getUpdateProperties: updateFile=minimwatch-2.jmupd 19:09:18.433 Thread-36: PackageManager: cached resourcePrefix is http://minimworld.com/ 19:09:18.511 Thread-36: getProgramProperty progName=MinimWatch propName=.version result=2.0.8 19:09:18.511 Thread-36: getNewVersionInfo: newVersion= name=MinimWatch 19:09:18.511 Thread-36: TrayView: returning from showLog method 19:10:54.409 AWT-EventQueue-0: TrayView: show log action 19:10:54.410 Thread-37: ServerControl: showLog action 19:10:54.414 Thread-37: TrayView: returning from showLog method |
|||
|
22-02-2021, 22:22
Post: #6
|
|||
|
|||
|
RE: Please help...subnet and rescan issue..drive mapping
Thanks for this. I am having difficulty making sense of it because you have changed the logging level from Info to either Debug or Trace. Please do the following:
1) In the MinimWatch log window, set the logging level to Info 2) Close the MinimWatch log window 3) Exit MinimWatch 4) Launch MinimWatch again by double-clicking the desktop icon 5) Wait one minute 6) Post the first part and last part of the log again |
|||
|
23-02-2021, 10:59
Post: #7
|
|||
|
|||
|
RE: Please help...subnet and rescan issue..drive mapping
I've deleted Minimwatch and Minimserver after advice on Naim forum and ||I'm about to install V2. Do I need to put the server in the Qnap Mdrive and Watch on desktop?
|
|||
|
23-02-2021, 11:51
Post: #8
|
|||
|
|||
RE: Please help...subnet and rescan issue..drive mapping
(23-02-2021 10:59)sam Wrote: I've deleted Minimwatch and Minimserver after advice on Naim forum and ||I'm about to install V2. Do I need to put the server in the Qnap Mdrive and Watch on desktop? MinimServer 2 on a QNAP |
|||
|
23-02-2021, 12:45
(This post was last modified: 23-02-2021 12:45 by simoncn.)
Post: #9
|
|||
|
|||
RE: Please help...subnet and rescan issue..drive mapping
(23-02-2021 10:59)sam Wrote: I've deleted Minimwatch and Minimserver after advice on Naim forum and ||I'm about to install V2. When you deleted MinimServer 0.8 from your QNAP, your configuration settings will have been lost. If you previously had any custom settings, you will need to re-enter these settings after installing MinimServer 2. |
|||
|
23-02-2021, 18:29
Post: #10
|
|||
|
|||
|
RE: Please help...subnet and rescan issue..drive mapping
Hi, I'm trying to download Minimserver 2 onto a QNap TS-128A via a Windows 10 PC. But it won't download and also I need to find a way of seeing the Qnap musicserver contenst when the PC is off which it used to do before Minimserver 1 decided to stop working.
A step by step guide would be really appreciated. I don't mind payingbut I'd like to see it works first.... |
|||
|
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 2 Guest(s)

Search
Member List
Calendar
Help





