DllRegisterServer in MSCOMCT2.OCX failed - windows-xp-sp3

I tried to register MSCOMCT2.OCX at MS Win XP Prof 2002 SP 3. I got this error message - DllRegisterServer in MSCOMCT2.OCX failed. I checked it under C:\WINDOWS\system32. It's already there. But still got this error.

Related

Error : Sox has exited with error code 1. How can i this error debug?

I am testing recongnize.js among Google speech api.
But now I have an error related to the Sox.
How can I debug?
it is error.
Listening, press Ctrl+C to stop.
sox has exited with error code 1.
Enable debugging with the environment variable DEBUG=record.
I've installed all of the versions 14.1.1 and 14.1.2 and entered them into $Path.
I need your help

kernel debugger error when running my solution on window mixed reality portal

I've been doing some UWP development and when i run my application on mixed reality portal it throws the below error :
CallContext:[\PublicAPIActivity]
onecoreuap\windows\analog\input\mirage\stubdll\holographicspace.cpp(390)\Windows.Perception.Stub.dll!0F7C1A21: (caller: 03F18204) ReturnHr(2725) tid(2eac) 80070057 The parameter is incorrect.
Exception thrown at 0x772D08B2 (KernelBase.dll) in MSIApp.exe: 0x40080201: WinRT originate error (parameters: 0x80070057, 0x00000057, 0x05AAEB64).
analog\input\mirage\publicapi\holographicspace.cpp(340)\Windows.Mirage.dll!067CA971: (caller: 0F7C1A04) ReturnHr(2728) tid(2eac) 80070057 The parameter is incorrect.
Anybody has any idea why this error occurs repetitively?
VS used : Vs 2017 community latest edition 15.5.6
VGA : Geforce GTX 1060
Thank you
it seems there is an issue with microsoft os and my laptop they are working on it

assert at occcount.cpp 926 line in visual studio 2008

I have source code based on MFC in visual studio 2008 and Windows 10. When I build as Win 32 debug mode , occured the accert fail at runtime
show assertion message
So I found the solutions to resolve this problem at below link.
https://support.microsoft.com/en-us/help/949107/debug-assertion-failed-in-occont.cpp-line-926
But it is not helpful because I don't have the extra dll, or ocx.
I could find the assertion point. please see the below code.
if(m_objSearchDlg.Create(IDD_SEARCH_DLG, (CWnd*)this) == FALSE)
return bResult;
m_objSearchDlg.ShowWindow(SW_SHOW);
After m_objSearchDlg was created, occured the assert when calling the "ShowWindow" method.
I thought that m_objSearchDlg instance is not normal.
Please help me.
Thanks

mysql and c++ in vs 2010: sqlstatementhandle and connection error

I finally solved my problem:
I had been using a lib of mysql that was not compiled with the same settings as the VS10 project. Doing this solved my issue
This was my issue
I am having some trouble, and i was wondering if anyone could give me a push in the wright direction.
I am trying to connect to a local Mysql database, using c++ in VS 2010.
On phpmyadmin i can see that an attempt to connect is made but doesn't succeed.
When building the application, i get some errors.
The first where char* errors. I solved that by changing from unicode to multi byte.
The most important error, i think, is this one:
warning C4700: uninitialized local variable 'sqlstatementhandle' used.
After the application crashes i get this in visual studio:
Run-Time Check Failure #3 - The variable 'sqlstatementhandle' is being used without being initialized.
In the console i get this:
Connecting to SQL...
Connect() - SQL_ERROR
Message: [Microsoft][ODBC SQL Server Driver]Fout in het dialoogvenster
SQLSTATE: IM008
In the documentation i found that error code 008 refers to:
Dialog failed
SQLDriverConnect
But i don't really now how this can help? Is the driver not able to connect, or is the driver not loaded at all? As I told earlyer, i can see in phpmyadmin that there are failed attempts to connect.
my setup: visual studio 2010 and a mysql server administrated true Xampp. A 64bit windows 7 machine.
In connection string, Driver shows "Sql Server". Perhaps Connection String is problem. Try to change it. This site will help you.
http://www.connectionstrings.com/mysql#p31

svcutil failing on IIS7 server, but not on Visual Studio 2010 temporary web server

I've created a LINQ to SQL class and a Silverlight-enabled WCF Service to a Silverlight 4.0 solution I'm working on. I'm in the process of publishing it to a local IIS7 server, instead of running inside the Visual Studio temporary web server. Whenever I build the project with the service running on the temporary web server, it works fine, but once I move it to my IIS7 web server, it fails with the following errors:
Warning 1 Custom tool warning: Cannot import wsdl:portType
Detail: An exception was thrown while running a WSDL import extension: System.ServiceModel.Description.DataContractSerializerMessageContractImporter
Error: Schema with target namespace '' could not be found.
XPath to Error Source: //wsdl:definitions[#targetNamespace='']/wsdl:portType[#name='SpaceGameDBService'] C:\Users\MindWorX\documents\visual studio 2010\Projects\MindWorX.Spacegame\MindWorX.Spacegame\Service References\DBServiceReference\Reference.svcmap 1 1 MindWorX.Spacegame
Warning 2 Custom tool warning: Cannot import wsdl:binding
Detail: There was an error importing a wsdl:portType that the wsdl:binding is dependent on.
XPath to wsdl:portType: //wsdl:definitions[#targetNamespace='']/wsdl:portType[#name='SpaceGameDBService']
XPath to Error Source: //wsdl:definitions[#targetNamespace='http://tempuri.org/']/wsdl:binding[#name='CustomBinding_SpaceGameDBService'] C:\Users\MindWorX\documents\visual studio 2010\Projects\MindWorX.Spacegame\MindWorX.Spacegame\Service References\DBServiceReference\Reference.svcmap 1 1 MindWorX.Spacegame
Warning 3 Custom tool warning: Cannot import wsdl:port
Detail: There was an error importing a wsdl:binding that the wsdl:port is dependent on.
XPath to wsdl:binding: //wsdl:definitions[#targetNamespace='http://tempuri.org/']/wsdl:binding[#name='CustomBinding_SpaceGameDBService']
XPath to Error Source: //wsdl:definitions[#targetNamespace='http://tempuri.org/']/wsdl:service[#name='SpaceGameDBService']/wsdl:port[#name='CustomBinding_SpaceGameDBService'] C:\Users\MindWorX\documents\visual studio 2010\Projects\MindWorX.Spacegame\MindWorX.Spacegame\Service References\DBServiceReference\Reference.svcmap 1 1 MindWorX.Spacegame
Warning 4 Custom tool warning: No endpoints compatible with Silverlight 4 were found. The generated client class will not be usable unless endpoint information is provided via the constructor. C:\Users\MindWorX\documents\visual studio 2010\Projects\MindWorX.Spacegame\MindWorX.Spacegame\Service References\DBServiceReference\Reference.svcmap 1 1 MindWorX.Spacegame
Warning 5 Custom tool warning: Exception has been thrown by the target of an invocation. C:\Users\MindWorX\documents\visual studio 2010\Projects\MindWorX.Spacegame\MindWorX.Spacegame\Service References\DBServiceReference\Reference.svcmap 1 1 MindWorX.Spacegame
Error 6 Custom tool error: Failed to generate code for the service reference 'DBServiceReference'. Please check other error and warning messages for details. C:\Users\MindWorX\documents\visual studio 2010\Projects\MindWorX.Spacegame\MindWorX.Spacegame\Service References\DBServiceReference\Reference.svcmap 1 1 MindWorX.Spacegame
Now, I believe that warning 4 and 5 and error 6 is a result of warning 1, 2 and 3, so I've ignored them for now. I've been googling around, and seen suggestions telling me to untick the checkbox "Reuse types in referenced assemblies" when I add the service reference to the main Silverlight project, however this hasn't fixed my issue at all. I've tried restarting Visual Studio as well, but this hasn't fixed anything either. I've started to consider that it's some sort of setting in the IIS7 web server, that I'm missing, but I looked around for hours now, and decided to come here for help. I found a similar problem here, but the "solution" was to not solve the problem, but instead find another way. I'm hoping this time we can find a solution instead.
Turns out that when I created the solution, I forgot to tick "Enable WCF RIA Services". Along with this I also redid web.config from scratch. How this still works on the development server is a mystery to me, however doing both things solved the problem.