![]() This was not encountered in TEST environment as the unit test scenarios covered Common test accts. Regarding how this happened still seems to be a puzzle which is hard to find as this file was supposed to be auto-generated and no manual edits should have taken place. The problem is this logic seem to be replaced with a manual hard code referencing test webservice URL. NET conversion process from 1.1 to 3.5, there is a Auto Generated web reference source file (Reference.cs under web reference) that contained the logic to get the correct Production URL for configuration file (web.config). Server did not recognize the value of HTTP Header SOAPAction: xx.xx.xx.101\ServiceName\MethodName.ĭuring the. If I change the URL in the web.config to something other than what the project was compiled with, I get an error when calling the web service: In the Live environment, I need to point them at xx.xx.xx.102, or whatever.Ĭurrently, we've got all of the URLs stored in keys in the web.config file, so that we can change them dynamically. In the Staging environment, I need to point the services at xx.xx.xx.101 We have two environments that I need to deploy this project to, with different URLs for the different remote servers. No joy.I have inherited a web app project that makes use of a number of WCF Web Services hosted on a remote server. I have run Windows Update again and installed the latest patches. After doing so and rebooting the server I was able to install the MXDW and QuickBooks was able to generate PDFs! Yay! The following week, without installing any updates whatsoever, the problem returned. I decided to uninstall the most recent security updates. The one time I enjoyed any success was last week. Step - DISM /Online /Cleanup-Image /StartComponentCleanup /ResetBase I have also tried using the install ISO as a source.** ** NOTE: I have tried using a known good server, live and running, as a source. ![]() Step - DISM /Online /Cleanup-Image /RestoreHealthĭeployment Image Servicing and Management tool Supported in offline servicing scenarios. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. Windows Resource Protection found corrupt files but was unable to fix some This process will take some time.īeginning verification phase of system scan. The handle is invalid.īeginning system scan. >Printer Name - "Microsoft XPS Document Writer v4" >Use an existing printer driver on the computer - select from dropdown menu - "Microsoft XPS Document Writer v4" >Add a new printer using an existing port: PORTPROMPT: (Local Port) >Right click "Printers" under SERVER, select "Add Printer" When attempting to install the printer through the Print Management interface: >Replace the current driver - ERROR "Printer driver was not installed. >Use the driver that is currently installed - ERROR "Unable to install printer. >Two different errors are generated depending on what is selected next: ** NOTE: Have done this from Windows Update, and also selecting the actual driver from the driver store by selecting "have disk"** >Select driver "Microsoft XPS Document Writer v4" >Use an existing port - PORTPROMPT: (Local Port) >Add a local printer with manual settings ![]() When attempting to install the printer manually with the Add Printer Wizard: I cannot get the server to actually install a printer using that driver, which QuickBooks needs to generate PDFs. The driver for the MXDW is still installed in the system. After troubleshooting the cause it turns out that the XPS Document Writer had disappeared. This server is set up to be an application server, hosting QuickBooks Enterprise 2021.Ī few weeks ago QuickBooks was suddenly unable to generate PDFs. I have a copy of Windows Server 2016 running as a VM on a Dell PowerEdge with VMWare.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |