Jump to content


james.mcdonald2899

Established Members
  • Posts

    4
  • Joined

  • Last visited

Everything posted by james.mcdonald2899

  1. We are having a problem pushing our client installs and manually installing them. Regardless of the way we try to install them we continue to receive the same 2 errors: Failed to correctly receive a WEBDAV HTTP request. Failed to successfully complete HTTP request. (StatusCode at WinHttpQueryHeaders: 405) Among other things that have not had a difference, I have deleted the MP, removed the WEBDAV service from the IIS role, added back WEBDAV, and reinstalled the MP. WEBDAV and the MP both installed without any errors. We have had the particular site server running for about 2-3 years without this problem. This just started happening recently. Any help would be appreciated. Also, I have looked and the applicationhost.config, and WebDAV_schema.xml files, and all seems ok with those.
  2. My reporting point just stopped working all of the sudden. I have had a reporting point for about 2-3 years on this site server and have used it multiple times without any problem. I went to run a report and received the "HTTP Error 500 - Internal Server Error. Module IsapiModule Notification ExecuteRequestHandler Handler ASPClassic Error Code 0x800700aa Requested URL http://<siteserver>/<reporting_point>/reports.asp Physical Path c:\inetpub\wwwroot\SMSReporting_KS1\reports.asp Logon Method NTLM Logon User NG\svc.sccm.ngks Failed Request Tracing Log Directory C:\inetpub\logs\FailedReqLogFiles I took a look at other websites i have in IIS, but they are working fine. It looked like it was localized to just my reporting point, I I tried deinstalling it. That was when I noticed this error in the rsetup.log: Initialize variables. Deinstallation beginning IIS is installed. Start web services. Configuring Registry. Executing: ReportingInstall /s /m=C:\PROGRA~2\MIE096~1\bin\i386\rep.val /deinstall ReportingInstall.exe returned 0 Cannot remove the Reporting registry key - Still in use. Finished After I noticed that problem, I went ahead and tried to re-install the reporting point. It looked like it worked judging by the same log: Initialize variables. IIS is installed. Start web services. Configuring Registry. Executing: ReportingInstall /s /m=C:\PROGRA~2\MIE096~1\bin\i386\rep.val ReportingInstall.exe returned 0 Finished So I tried to run a report again and still got the 500 error. I tried deinstalling it again, but saw the same "Cannot remove the Reporting registry key - Still in use." entry in the log. So I went to the SMSReportingInstall.LOG and saw this: ----------------------------------------------------------------------------------------------- Begin Install CMDLINE=/s /m=C:\PROGRA~2\MIE096~1\bin\i386\rep.val /deinstall Error running smswwwroot.vbs script ----------------------------------------------------------------------------------------------- Begin Install CMDLINE=/s /m=C:\PROGRA~2\MIE096~1\bin\i386\rep.val Error running smswwwroot.vbs script ----------------------------------------------------------------------------------------------- I have tried re-registering vbscript, but that did not resolve the issue. Any help would be appreciated. Thank you.
  3. I have a working USMT hardlink TS and was wondering, If i would want to run a SFC /SCANNOW and a CHKDSK /f /r, to make sure there were no errors before I started migrationg the data, where would I put it in the TS?
  4. I am getting a slight problem when i run the offline hardlink TS. When it runs my runscanstate.bat file, it comes up with a "Settings store argument specified is invalid 0x00000091. I have been at it for a while and i need a second, third, and maybe even fourth eye on this. I have included the TS (xml) and the runscanstate syntax (txt). Please tell me what i am missing. Im starting to see double. runscanstate.txt USMT-HARDLINK-TEST(Offline).xml
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.