When I logged on to The WinQual site this morning the update message below was displayed. I'm slightly confused by the wording of the last paragraph. Does this mean that "support" will no longer be available for WER for XP. Or that there will no longer be xp/errors reports logged and process?
Attention Required: Scheduled Winqual Site Downtime Starting February 9, 2012 during which all Winqual services will be unavailable.
On February 9, 2012 at 6:00 P.M. Pacific Standard Time, Winqual will go offline and service will return on or before February 16, 2012 at 12:00 P.M. Pacific Standard Time. During this period, the Winqual site will be unavailable. We ask you to plan ahead for this interruption of Winqual service. There will be no method available during this time to view or perform Logo submissions, Device Metadata submissions, obtain VeriSign certificates, sign legal agreements or use any other services currently provided through the Winqual site.
This is scheduled maintenance and mail will be sent to all Winqual
members when service returns.
Attention Required: Windows Error Reports discontinuing support for Windows XP and Windows Server 2003 error reports Based on the
mainstream support lifecycle of Windows, we are discontinuing support
of Windows XP and Windows Server 2003 Windows Error Reporting (WER)
data. Support will end on February 9, 2012.
I was confused by that statement as well and sent an e-mail to winqual support asking if it meant WER will no longer collect crash reports for Windows XP? which I found hard to believe since it still fairly widely used OS. the response I got was not quite clear either...
**This change is based on mainstream support lifecycle of Windows.
In general though for generic bugs on Win 7 you should get coverage across multiple OS. Overall we are seeing a very low percentage of the data flow through based Windows XP. Also Windows XP data can only classify issues as an Event/Bucket level (see this blog for more information on Buckets versus server side analysis), which can provide a misleading analysis of the faulting issue.**
so I was just waiting for the WinQual site to come back online and see what's available.
(FYI, I visited the site for the first time today and none of my programs and crash reports were available and I added that as a separate question here on StackOverflow)
Related
I had installed ColdFusion 2018 recently and with the installation less than a month old (and my understanding of the technology even less), my Cold Fusion service has stopped working. I have tried a number of things and have referred to a number of articles and out of many such errors where the service is not being accessible, some of them were able to get it resolved. However, some other obscure reason that may be causing this error have been untouched and unknown.
Whenever, I try to restart the service, I get an error as shown below:
Windows could not start the ColdFusion 8 Application Server on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to server-specific code error 2.”
Without much understanding, I started to google it out. Looking into every one of these posts, I tried
Configure JRE and try to relaunch the service by looking at "JAVA_HOME" variable and JVM.config
Run the batch files in every possible combination to find if anything clicks
Check if the present JAVA version works and is compatible with Coldfusion version installed
Fiddling with the "SessionStorage" var in neo-runtime.xml file as some suggested
and few other tricks coupled with a numerous service restart attempts and a few machine reboots as well.
A service that renders Cold Fusion pages should be shut down abruptly. To add to agony, the CF Admin also depends on the service and hence does not work.
Any pointers to any potential solutions?
After my laptop froze yesterday I rebooted, and now the ColdFusion 9 Application Server service starts and restarts endlessly! Although it's set to start automatically, upon bootup it does not start. So I start it manually. Then I look at the Windows Event Viewer which reports:
The ColdFusion 9 Application Server service for the "coldfusion" server was started. PID is 5788.
That's good. But then, about 9 seconds later, Event Viewer reports:
The ColdFusion 9 Application Server service for the "coldfusion" server is restarting.
16 seconds later, the Event Viewer reports that the service has, in fact, started again. And 9 seconds after that, it reports that the service is starting again.
Unless I manually stop the service, this cycle continues, with the CF service restarting itself every 25 seconds, give or take a second. Needless to say, I can't use ColdFusion. When I try to reach a page, I get error 500: There is no web application configured to service your request
I am running the developer edition of CF9, Windows. Computer behaves normally otherwise.
[Edit]
The coldfusion-out.log includes this:
Server coldfusion ready (startup time: 9 seconds)
A fatal error has been detected by the Java Runtime Environment:
EXCEPTION_IN_PAGE_ERROR (0xc0000006) at pc=0x6d6e2424, pid=5456, tid=7724
JRE version: 6.0_17-b04
Java VM: Java HotSpot(TM) Server VM (14.3-b01 mixed mode windows-x86 )
Problematic frame:
C [nio.dll+0x2424]
An error report file with more information is saved as:
C:\ColdFusion9\runtime\bin\hs_err_pid5456.log
If you would like to submit a bug report, please visit:
http://java.sun.com/webapps/bugreport/crash.jsp
The crash happened outside the Java Virtual Machine in native code.
See problematic frame for where to report the bug.
The detailed error report, C:\ColdFusion9\runtime\bin\hs_err_pid5456.log, has a ton of information, but I don’t understand much of it. I’ll be happy to post it all if you think you might be able to make heads or tails of it.
In the event that the only solution is to reinstall CF, can you tell me where to find the config files? I know I will need jrun-web.xml (and I know where it is), but where, for example, are the datasource definitions found? I can’t seem to find any folder or file with the settings from the CF Admin. (The CF Admin won’t run, so I can’t view them that way.)
I installed ColdFusion 10 Enterprise Edition 64 bit. But after 30 days it is converted into Developer edition automatically. Now when i try to give new KEY through System Settings, it displays the message "Server has been updated successfully" but it still shows in the System Settings that it is "Developer Edition" and i am getting following error message when more than 2 persons try to access the ColdFusion applications on the server
"You tried to access the Developer Edition from IP address (192.1.221.83). Already two IP addresses are accessing ColdFusion concurrently. The Developer Edition supports access by any IP address, but only two at a time, apart from the localhost. The additional IP addresses accessing ColdFusion are: 192.1.221.5,192.168.0.168"
Can anyone help on that please? When i am giving the KEY why it isn't converting it into Enterprise edition?
Your best bet is to take advantage of the free installation support Adobe offers. Email: cf.install#adobe.com.
I've heard of this sort of thing happening before, but am unaware of a generic answer. But Adobe will sort it out for you.
Couldn't figure it out
I had to move back to CF9
I have a service (C++) that during its startup might sleep for 10 minutes (error case).
in 2003 - it worked fine, when I migrated the code to 2008 product, Windows Services notify me that the service could not start (my application still alive - but from windows perspective after 1 minute it claims there is a problem..)
-> Though the code was migrated to newer version no change in code flow
-> there is only one thread that starts everything.
-> I can't start the application if this error occurs (I must sleep).
-> Is there any change in 2008 behavior?
Thanks.
There are changes in how session-ids are maintained. The interactive logged-in user would get session-id starting with 1 (In Windows 7/2008), which used to be 0 for previous versions of Windows.
Along with that there are restrictions on how services can interact with the desktop. If service creates/shows windows, it will NOT be rendered to session that belongs to current user, but it would be shown via session-id 0' desktop.
You may check this discussion
I'm trying to write an application that connects to my company's wireless network automatically on windows XP.
I've found the Wireless LAN API but it requires me to have some hotfix installed on the machine, and you need to have sp2 or higher(There are machines with SP1, and I'm required to support any XP machine).
I've tried to find some samples about Wireless Zero Configuration on MSDN but with no luck, only samples I've found are for WinCE, I think Microsoft stopped supporting it. In addition I couldn't find where to download the dll and header file for working with the WZC.
There must be a way to do it and work on any service pack because I've found Zwlancfg by ENGL
Point out that any change you'll have to introduce to these old XP machines will be similar in magnitude to the SP2 update, except that (1) you don't have the insight into the network stack that Microsoft has, (2) you don't have the experience in Windows development that Microsoft collectively has and (3) you don't have the testing resources (including beta testers) that Microsoft has. So your change will be more risky and less stable than the SP2 update.
Couldn't you just setup the wireless password and tell XP to auto-join when it sees the network?
Maybe I'm missing something but it happens automatically, so I don't see why you need to code an app to do this.
I would encourage you to advocate for upgrading those XP machines at least to Service Pack 2 as it was a major upgrade in terms of functionality and security. It's also been at least 5 years since it was rolled out so I can't imagine you'd have compatibility issues with 3rd party software.
That being said.
Wireless for XP was seriously reworked with Service Pack 2 and the Wireless Network Policy was created that allows you to push out policy to all machines on your network via the Group Policy MMC.
You should try native wifi api but it will work with XP SP2
There is one WLANCONNECT() methos try that one
with that you will be able to connect to network with your program