Exeption raised in the backend: [Win Error 5] about lauhdutin HOT 13 CLOSED

Try setting the value of the skin's Python path setting to python to show the terminal, loading the skin again, and then post either a screenshot or a text copy of what is printed in the terminal.

from lauhdutin.

after a restart everything worked :)..
sorry ^^

but the skin is loading more than a minute and the console stucks at

Processing Steam games...
                Failed to process 'sharedconfig.vdf'
                Failed to process 'localconfig.vdf'

could you help me?

from lauhdutin.

I've uploaded a Video, where you can see it :)
https://drive.google.com/file/d/0BxCdQ_0niCMFQ2RFQVBhUmp0Q00/view?usp=sharing

from lauhdutin.

The log pertaining to the original issue would indicate that Windows' permission system is interfering with the execution of a VBScript file, which is used by the skin to process shortcuts (.lnk and .url files) in order to get paths to the executables that the shortcuts point to. I haven't touched files relevant to those parts of the skin in a while so perhaps a recent Windows update is causing the problem?

EDIT: I don't have Windows 10 so unfortunately I cannot personally test issues that might be related to the OS's permission system.

from lauhdutin.

Okay. The original issue was solved by a simple restart now, as I said.

Yes, C:\Program Files\Rainmeter is my Rainmeter directory. But the skins are stored in D:\Documents\Rainmeter\Skins\..

from lauhdutin.

Should I open a new ticket/issue for the other Problem?

from lauhdutin.

Sure. It may make it easier to find an answer if someone else has the same issue in the future and there is an issue with a title matching their issue.

from lauhdutin.

I have the bug now again. A simple reboot only helps sometimes.

from lauhdutin.

I tried to look for reports of similar issues elsewhere on the internet, but it looks like in most of those cases the cause was an attempt to remove a file that was being accessed by another process (e.g. antivirus). However, in your case the issue seems to arise when attempting to execute a VBScript file that returns the path that a shortcut (.lnk or .url) points to. My impression is also that in those other cases it was happening consistently.

Does the error occur at the same point every time (i.e. is a specific shortcut causing the issue or is it seemingly random)?

If the error only occurs during certain sessions and can be resolved by rebooting, then figuring this out is going to be quite tricky to say the least.

from lauhdutin.

It's seemingly random.. :/

I figured out, that it must be an error from my external shortcuts. When I removed them and reloaded the skin, the error didnt occur.

from lauhdutin.

When I removed my shortcuts, the WinError 5 error did not occur, but if I now hover over a game, the error occurs that Steam / Blizzard is not running (thats wrong).

from lauhdutin.

Could you check what the names of the Steam and Blizzard processes are in Windows Task Manager? The skin expects them to be Steam.exe and Battle.net.exe.

Another thing that you could check is the values of two measures: SteamMonitor and BattlenetMonitor. Open Rainmeter's log, go to the Skins tab, select the skin, and you should see a list of measures and variables on the right-hand side of the window. Starting and closing Steam and/or Blizzard App should change the values of those two measures. Keep in mind that you need to hover your mouse cursor over the skin in order for those measures to update.

Checking these things will hopefully help to narrow down the source of the issue. I assume there are no errors in Rainmeter's log since you didn't mention any.

from lauhdutin.

No, I do not think that's the problem. The error occurs only when I have the WinError5 and then Reload the skin without the shortcuts. With the shortcuts, the skin does not even start. And without the shortcuts this error occurs.
If the skin starts (so the WinError5 error message does not come) I also dont have this problem.

I believe that this is generally connected with the Windows right system. Somehow it seems, as if Python simply do not get enough rights for whatever reason.

from lauhdutin.