-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Page Not Displayed on IIS8 and Windows Server 2012 #2590
Comments
In URL Rewrite there is a rule that redirects all requests to HTTPS. That rule needs to be disabled if you don't want the redirect to happen. |
Clear your cache in IE, or try a different browser. They usually remember redirects. |
Clearing Cache didnt work. |
Ok, what about trying a different browser or trying to access the site from a different computer? If it's still redirecting, you may have to slog through the Web.config file and make sure that there isn't anything in there that seems like it would be causing the redirect. |
Ive tried to access the site both on my work laptop and the VM that the server is hosted on. I tried on both IE and Chrome. |
@korio77 , Thank you for the response, can you tell me the exact locations of the log files. Im not sure where they are. Also upon checking the file and changing the ip and putting it in quote, When I restarted the page and went to the link I get HTTP Error 500. |
@korio77 , The main error I see are [13-Sep-2016 09:05:40 America/New_York] PHP Warning: require(C:\inetpub\wwwroot\snipe-it\bootstrap/../vendor/autoload.php): failed to open stream: No such file or directory in C:\inetpub\wwwroot\snipe-it\bootstrap\autoload.php on line 17 I can upload the whole log file if you would like |
Thats nice, now we know whats happening. That error is related to composer, seems like your is not installed or something happened when you installed it. Check the common issues page https://snipe-it.readme.io/docs/common-issues There you can find this error and how to solve it. Check it out and tell us when everything works again :D |
@korio77 , I followed the guide, Downloaded the composer, Moved the .exe into the C:\inetpub\wwwroot\snipe-it folder and right click and installed. The help files you linked are broken and give me a 404 when trying to get to them. |
I see. Check this https://snipe-it.readme.io/docs/install-dependencies at the bottom, once you have done that keep following the documentation to finish the installation. |
@korio77 I followed the directions, Please see attached pictures. |
The documentation is a bit weird in some places because its made almost entirely for a "linux" enviroment, some things works different in windows. Having that in mind, and as i can see in the pics, seems like you have composer properly installed, have you used the comand "composer install" in the cmd window before? |
@korio77 This what what happens when I try to run composer install after navigating to c:\inetpub\wwwroot\snipe-it. |
@korio77 , I have all of those enabled accept php_ldap.dll and php_pdo_sqlsrv.dll Please see attached. |
Then there is something wrong with your php installation or config. Check the php.ini file and look for the extensions if they are enabled there too, sometimes you can have multiple php.ini files so use a folder search and check all of them. |
@korio77 , I think I found an issue, There were two php install directories here(root and program files). I changed it to the C:\PHP that composer was looking for and changed the IIS Server to look at that php-cgi and the composer was able to be installed. |
I generated a new key, restarting the server. |
Good news, keep going! |
@korio77 , I restarted the server and now the errors im getting in the PHP Log are. [13-Sep-2016 09:53:03 America/New_York] PHP Fatal error: Uncaught UnexpectedValueException: The stream or file "C:\inetpub\wwwroot\snipe-it\storage/logs/laravel.log" could not be opened: failed to open stream: Permission denied in C:\inetpub\wwwroot\snipe-it\bootstrap\cache\compiled.php:13906 |
that error is related to the bootstrap folder permisions, i cant remember this one well (i had this problem a long time ago), but i have 2 iis users onE is the one you have, the other one is this one try to check if you have this user too (change "esagprdwsus" with your server name). In the end you need to grant permisions to the user the iis server is using , in the past i had to check our friend google for more info about that to see which one was the real user the iis server was using. |
Judging by |
enable the debug mode in the .env file, restart the iis server and reload the page (deleting cookies) you should get some error logs there, and check the php log again to see if there is anything new! |
Well, there's no mystery there. Check the credentials that you put in your .env file and check the permissions on your database. |
@ddreier Working on it right now. I will let you know. |
remember the single quotes ;) |
@korio77 @ddreier , Thank you both. Looks like were working now. However when I hit the Create Database Tables, It shows Whoops, looks like something went wrong. |
Syntax error or access violation: 1142 CREATE command denied to user 'snipe_user'@'localhost' for table 'migrations' From the Debug file. was "grant all on snipeit to 'snipe_user'@'localhost' identified by 'YOUR_DB_PASSWORD_HERE';" correct to assign permissions |
Did you give your Snipe-IT database user permissions to create tables? It's easiest just to give that user all privileges on that database. |
@ddreier im having issues guiving the user permissions. "grant all on snipeit to 'snipe_user'@'localhost' identified by 'YOUR_DB_PASSWORD_HERE';" is giving me an error |
I got it going Thank you both for all your help |
If you're 100% up and running, please close the Issue. |
Hey Everyone I read your discussion. I had same problem |
Hi All,
I am getting the attached screen while trying to access the Snipe IT site from IIS server.
I followed the steps as mentioned the Snipe IT manual Guide.
I am using PHP V7.0 and IIS 8
Any and All Help is appreciated.
Please see the screen shots below.
The text was updated successfully, but these errors were encountered: