CaptainMurphy 0 Posted May 25, 2009 (edited) Ah, another useless error message courtesy of M$. http://www.eventid.net/display.asp?eventid=11708&eventno=1686&source=MsiInstaller&phase=1 That is the only reference I can find about it that makes any sense. Using the admin user should be fine. At least with the items installed you should be able to change the application pool to the correct one. Did it at least install it as an application? It can be installed manually, just as long as the service is there and it has a directory that you can modify to complete the rest of it. If we have to we can commit the changes manually. The installer package was SUPPOSED to make it easy. As far as uninstalling, it should be fairly straightforward. Normally just removing the directory will destroy any references to the settings. Edited May 25, 2009 by CaptainMurphy Share this post Link to post Share on other sites
gruber 10 Posted May 25, 2009 Ah, another useless error message courtesy of M$.http://www.eventid.net/display.asp?eventid=11708&eventno=1686&source=MsiInstaller&phase=1 That is the only reference I can find about it that makes any sense. Using the admin user should be fine. At least with the items installed you should be able to change the application pool to the correct one. Did it at least install it as an application? It can be installed manually, just as long as the service is there and it has a directory that you can modify to complete the rest of it. If we have to we can commit the changes manually. The installer package was SUPPOSED to make it easy. As far as uninstalling, it should be fairly straightforward. Normally just removing the directory will destroy any references to the settings. Theres no appication there just the web service part running but i cant do anything with it how do you install it manually???? Share this post Link to post Share on other sites
CaptainMurphy 0 Posted May 25, 2009 By application I meant a web application. It shows the directory as a little gear looking icon in the IIS MMC. The setup is kind of standard for a web application. You just make sure that the directory or virtual directory you are setting it up is has the right name, then you right click on the directory and view the properties. General Tab - Set an application name (if one is not already set) Execute Pemissions = Scripts only Application Pool = Your created app pool name ASP.NET Tab - ASP.NET Version = 2.0.XXXXX In theory if the directory is installed as part of the inetpub\wwwroot\ then you won't have to change any file permissions for the application directory. Share this post Link to post Share on other sites
gruber 10 Posted May 26, 2009 By application I meant a web application. It shows the directory as a little gear looking icon in the IIS MMC. The setup is kind of standard for a web application. You just make sure that the directory or virtual directory you are setting it up is has the right name, then you right click on the directory and view the properties. General Tab - Set an application name (if one is not already set) Execute Pemissions = Scripts only Application Pool = Your created app pool name ASP.NET Tab - ASP.NET Version = 2.0.XXXXX In theory if the directory is installed as part of the inetpub\wwwroot\ then you won't have to change any file permissions for the application directory. Got the little gear icon but cant find a directory or virtual directory in the inetpub\wwwroot\ one of the server admins who is a bit better with this type of thing is going to look at it for me and see if i have done anything wrong. Share this post Link to post Share on other sites
CaptainMurphy 0 Posted May 28, 2009 Any update from your admin? Hopefully they got it figured out. The web service portion is really not that complicated for a regular windows admin to see what it needs to do once they read the doc. I am not much for converting geek speak into laymans terms, so if anyone feels like making the doc a little more readable you are welcome to have at it. Share this post Link to post Share on other sites
gruber 10 Posted May 28, 2009 Any update from your admin? Hopefully they got it figured out. The web service portion is really not that complicated for a regular windows admin to see what it needs to do once they read the doc. I am not much for converting geek speak into laymans terms, so if anyone feels like making the doc a little more readable you are welcome to have at it. He's looking at it now ill post back when hes done. Share this post Link to post Share on other sites
CaptainMurphy 0 Posted June 2, 2009 (edited) I figured out the problem with the namespace. It was a bout of stupidity. I kept looking at the web service portion for the answer, and the problem was the client was not looking for the latest web service build. It had not been synced in a while to the latest version so it was still looking for the wrong name. It is now fixed and the latest version deployed on the DUCK server for download. Special thanks to gruber for help in figuring out the problem and getting access to their server for testing! Edited June 2, 2009 by CaptainMurphy added more Share this post Link to post Share on other sites
CaptainMurphy 0 Posted March 29, 2011 This project is now open on Codeplex for anyone interested in helping work on it. http://armamanager.codeplex.com/ Right now the code is in a bit of disarray and needs a bit of cleanup but so far it is a stable copy. Share this post Link to post Share on other sites
