Check the .Net version of the library and consumer. It should match or lower version.
The ‘System.Web.Security.SqlMembershipProvider’ requires a database schema compatible with schema version ‘1’
INSERT INTO dbo.aspnet_SchemaVersions
(‘common’, 1, 1),
(‘membership’, 1, 1),
(‘role manager’, 1, 1),
(‘health monitoring’, 1, 1),
(‘personalization’, 1, 1),
(‘profile’, 1, 1);
iisnode encountered an error when processing the request. HRESULT: 0x2 HTTP status: 500 HTTP subStatus: 1002 HTTP reason: Internal Server Error You are receiving this HTTP 200 response because system.webServer/iisnode/@devErrorsEnabled configuration setting is 'true'. In addition to the log of stdout and stderr of the node.exe process, consider using debugging and ETW traces to further diagnose the problem. The node.exe process has not written any information to stderr or iisnode was unable to capture this information. Frequent reason is that the iisnode module is unable to create a log file to capture stdout and stderr output from node.exe. 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. Alternatively you can disable logging by setting system.webServer/iisnode/@loggingEnabled element of web.config to 'false'.
Add line app.listen(process.env.PORT); in app.js
if you accidently delete your submodule folder and there are enteries in your .git config files, you have to manually remove from
- .git/modules/<submodule folder>
remove following entries
[submodule ".\\services\\projectWCFService"] url = https://github.com/jagsmcp/project1.git active = true
if you still see the error, use
If you have been asked to upgrade the project structure or taken over some tasks to revamp your git repository in more meaningful manner- definitely, there will challenges ahead and among them would be inter-dependency of projects on common library developed in-house or 3rd party, which has its own life-cycle – master, dev, hotfix, and release.
Setup your common library projects
- Upload your projects to git repository as usual projects.
- Upload your Main project to git repository as usual projects.
Linking / Sub-module
git submodule add https://github.com/jagsmcp/fileFactory
git commit -am 'added fileFactory module'
git push origin master
git clone https://github.com/jagsmcp/MainProject
git submodule init
git submodule update
or use one simple command
git clone --recursive https://github.com/jagsmcp/MainProject
if you are trying to clone git repository at root or current folder following command and switch –
PS C:\work\projects\repos\project1>git clone <repo> .
The “.” at the end denotes current folder
If you often come across this error it is likely you need to add additional step when you push existing source code to new repository.
PS C:\work\projects\repos>git remote add origin <repo> PS C:\work\projects\repos>git push -u origin master
if you see an error during git push, use following steps –
PS C:\work\projects\repos>git remote add origin <repo> PS C:\work\projects\repos>git add -- all PS C:\work\projects\repos>git commit -m "initial master" PS C:\work\projects\repos>git push -u origin master
- Windows Server 2016 x64
- IIS 10.0
Confirm IIS is up and running using http://localhost/
Tools/libraries you need
- IIS URL Rewrite extension – https://www.iis.net/downloads/microsoft/url-rewrite
- latest node.js x64 binaries – https://nodejs.org
- latest iisnode v0.22.1 x64 – https://github.com/tjanczuk/iisnode/releases/download/v0.2.21/iisnode-full-v0.2.21-x64.msi
- node is installed using the version check
- iisnode is registered in your IIS module
Register sample files from iisnode under Default Website in IIS.
Once it is done, verify samples are accessible via browser http://localhost/node.
Please note – if sample node sites fail to run at first, add IUSR and Network Service users to allow access sample files folder.