Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No access to mapped network drives? #28

Open
ruinit opened this issue Apr 2, 2016 · 9 comments
Open

No access to mapped network drives? #28

ruinit opened this issue Apr 2, 2016 · 9 comments

Comments

@ruinit
Copy link

ruinit commented Apr 2, 2016

Branch/Commit:Branch: master Commit: 529c7cec3c2bc79b05f7dab501a45e9a29e03efc
OS:Windows 10
What you did: New Install
What happened:Starts but can't access my mapped drives
What you expected: Access to mapped drives

With the trouble on synology I decided to make a windows install and still use my disk station for storage. I got it installed and all but I can not access my mapped drives? I don't use a password for this windows computer. I have looked around a bunch and can't seem to get a solution. I used the windows installer package.

Thanks for any help

@roscopwnz
Copy link

Hey I was wondering if you found a solution for this, currently experiencing the same issues now.

@OmgImAlexis
Copy link
Collaborator

@VinceVal

@zoochie
Copy link

zoochie commented Apr 28, 2016

Please tell me you've found a solution to this, i've tried everything that everyone's suggested in previous threads, with no luck.

thanks a bunch

@VinceVal
Copy link
Owner

Windows services cannot access mapped drives. So, you can either run SR as a regular (non-service) application under your user account after logging in, or, what I would do, is just use UNC (\server\share) style paths.

@zoochie
Copy link

zoochie commented Apr 28, 2016

ive tried UNC style paths, it still wont find my mapped network drive, how do i run it as a non service application?

thanks

@Hydro8
Copy link

Hydro8 commented May 9, 2016

Same problem here, can't access to mapped drives and can't access to network folder with \192.168.1.51\Show for example

@Jackinow
Copy link

I have the same problem, so i don't use the sickrage service and load the sickrage via a command.
For exemple, this is mine:
"C:\SickRage\SickRage\SickBeard.py" --nolaunch --port=8081 --datadir="C:\SickRage\Data"

and in my c:\SickRage\Data\config.ini
I modify 2 lines to specify my network drives:

root_dirs = 0|\192.168.1.85\seriesTV
tv_download_dir = \192.168.1.85\transmission\telechargements

and it's ok for me.

@29z
Copy link

29z commented Mar 6, 2017

I wasted 8 hours on this crap, and thought I would add what I did to fix it. Info: I used the installer several months ago(2-3) and had never shutdown my sickrage, that is until yesterday. Upon trying to restart my sickrage by restarting my computer the service would load and say running but my sickrage wouldn't have a webui. This is where I lost most of my time. After running sickrage in cmd I realized that unrar.exe installation was stopping my sickrage from continuing in startup and wouldn't proceed. So long story short I-

Installed unrar to data/unrar/
opened config file in data and changed the unrar path to the new installed unrar in data dir.
restarted my sickrage service.

Everything now works.

I realize this topic is almost 1 year old but for some reason this just happend to me. The answer to my problem came from this thread, so thanks for that.

@GaryUSMC
Copy link

I am having an issue with my GUI not loading and this did not fix it. It worked fine until yesterday. Was there another update that broke it? Any help would be greatly appreciated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants