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

built-in debugger doesn't work with an error (Azure SDK) #116

Closed
vasili-zolotov opened this issue Dec 14, 2011 · 12 comments
Closed

built-in debugger doesn't work with an error (Azure SDK) #116

vasili-zolotov opened this issue Dec 14, 2011 · 12 comments

Comments

@vasili-zolotov
Copy link

After installing Azure SDK on a Windows 7 windows dev box VM (Parallels), built in debugger doesn't work. At the same time log over http works when enabled.

GET http://localhost/server.js/debug/

Results in:

The iisnode module is unable to deploy supporting files necessary to initialize the debugger. Please check that the identity of the IIS application pool running the node.js application has read and write access permissions to the directory on the server where the node.js application is located.

Granted NTFS permissions to 'Everyone'. Tried running the app pool as SYSTEM. To no avail. The only thing that worked for debugging was to add "--debug" via Web.Config and to install standalone node-inspector. Now I get it, but it wasn't straightforward for a newcomer.

@tjanczuk
Copy link
Owner

Did you have any version of iisnode installed on the machine prior to installing Azure SDK?
Can you check if you have %programfiles%\iisnode\iisnode-inspector.dll file?

@vasili-zolotov
Copy link
Author

No I didn't. First time using node.js.
Nope. No iisnode-inspector.dll in program files.

Directory: C:\Program Files\iisnode

Mode LastWriteTime Length Name


-a--- 11/21/2011 4:11 PM 884 etw.bat
-a--- 12/9/2011 5:23 PM 122640 iisnode.dll
-a--- 11/29/2011 9:27 PM 566 LICENSE.txt

@tjanczuk
Copy link
Owner

The version of iisnode referenced from the Web Platform Installer for Windows Azure SDK for node.js does not support debugging node.js applications. This will change in future releases.

In the meantime, in order to enable debugging as described in http://tomasz.janczuk.org/2011/11/debug-nodejs-applications-on-windows.html, please uninstall 'iisnode for iis 7.x' from the Control Panel, then install a full version that supports debugging from http://go.microsoft.com/?linkid=9784330 (x86 version) or http://go.microsoft.com/?linkid=9784331 (x64 version).

After installation, you should be able to see the %programfiles%\iisnode\iisnode-inspector.dll file, and debugging should work as described at http://tomasz.janczuk.org/2011/11/debug-nodejs-applications-on-windows.html.

@tjanczuk
Copy link
Owner

Please reopen if the problem persists.

@vasili-zolotov
Copy link
Author

OK, thanks for the information. Is there a way to make this work in the staging environment? How would one currently go about debugging something that's been published?

@ghost
Copy link

ghost commented Dec 3, 2012

hi tjanczuk,

when I'm trying install iisnode for iis 7.x (x86) from the link you gave I retrieve the next error message:
"Microsoft Visual C++ 2012 Redistributable Package (x86) is required but not installed. Please install it then rerun this installer."
I'm doing so, installing the needed package, but still retrieving the same error message... :/

By the way, I'm doing so because when I install Node Power Tools on webMatrix it causing a crash and I'm getting the following error: "PrivilegedExe has stopped working." and right away retrieve the next massage:
"There was an error coping iisnode-inspector.dll into \iisnode-dev\release\x86\iisnode-inspector.dll. the exit code was -532459699."

Appreciate your help.
Gil.

@tjanczuk
Copy link
Owner

tjanczuk commented Dec 4, 2012

This is duplicate of #243. Please see a temporary workaround there.

@ghost
Copy link

ghost commented Dec 4, 2012

Well tnx.
Now, I succeed installing iisnode-full-iis7-v0.2.1-x86.msi but is seems not to fix the problem I'm having:

I've installed the extension Node Power Tools on webMatrix.
Now, When I try to open a file associated with WebMatrix I get a "Allow NodeElavator.exe to make changes to your computer" massage, I agree and then I get the following error: "PrivilegedExe has stopped working." I click on "Close Program" and then retrieve the next massage:
"There was an error coping iisnode-inspector.dll into \iisnode-dev\release\x86\iisnode-inspector.dll. the exit code was -532459699."

Any suggestions?

Gil.

@JustinBeckwith
Copy link

Greetings gilpo123, this seems like its isolated to NodePowerTools - could you create an issue over here?
https://github.com/MicrosoftWebMatrix/NodePowerTools

It may turn out that NodePowerTools makes a few assumptions about how iisnode is installed. Just to make sure - try this:
1.) Open WebMatrix
2.) Create a new site from template using one of the node templates
3.) Run the site, verify IISNode/IIS Express/ WebMatrix are living together happily
4.) Restart WebMatrix

Let me know how it goes!

@ghost
Copy link

ghost commented Dec 5, 2012

Hi JustinBeckwith,

Everything is working just fine as long as I'm not installing NodePowerTools (via extensions on Web Matrix).
I've open an issue as asked here:
MicrosoftWebMatrix/NodePowerTools#2

@henllyee
Copy link

Just copy the dll file to the folder.

@Arumugham
Copy link

http://stackoverflow.com/questions/7334216/iis7-permissions-overview-applicationpoolidentity, I followed these instructions and it worked. Its primarily because the application pool of the deployed node application doesn't have the read write permission.

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

5 participants