I have tried the different solutions offered in multiple threads but none of them are solving my issue.
Also I noticed i have no error in my logs so it does not facilitate to find the root cause of my error.
Ok first thing first:
I am an administrator on my laptop
I m running Windows 7 64 bit
I m using MQ 8.0.0.5
When I create a queue manager (btw i open WMQ as an administrator), the queue manager is created but I am getting the message AMQ8157: Security Error
See attached picture
The queue manager appears under the Queue Managers folder but it will not connect.
When I click on connect i am getting the error
An unexpected error (2063) has occurred. (AMQ4999) An unexpected
error (2063) has occurred. (AMQ4999) Severity: 10 (Warning)
Explanation: An unlisted error has occurred in the system while
retrieving PCF data. Response: Try the operation again. If the error
persists, examine the problem determination information to see if any
details have been recorded.
The .log does not display any error message so i am really stuck.
Below is the only log i m getting when creating the queue manager, nothing when i try to connect.
!ENTRY org.eclipse.osgi 2 1 2018-07-09 11:10:32.557 !MESSAGE NLS
missing message: UI_WIZARD_FILE_SIZE_UNCHANGED2_LABEL in:
com.ibm.wmqfte.explorer.elements !SESSION 2018-07-09 11:14:46.319
----------------------------------------------- eclipse.buildId=unknown java.fullversion=JRE 1.7.0 IBM J9 2.7 Windows
7 amd64-64 Compressed References 20160406_298393 (JIT enabled, AOT
enabled) J9VM - R27_Java727_SR3_20160406_0942_B298393 JIT -
tr.r13.java_20160328_114186 GC -
R27_Java727_SR3_20160406_0942_B298393_CMPRSS J9CL - 20160406_298393
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_GB
Command-line arguments: -os win32 -ws win32 -arch x86_64
!ENTRY org.eclipse.osgi 2 1 2018-07-09 11:14:51.921 !MESSAGE NLS
missing message: UI_WIZARD_FILE_SIZE_UNCHANGED2_LABEL in:
com.ibm.wmqfte.explorer.elements
This definitely seems like an issue related to permissions, you might want to double check on the users and groups for MQ that you have.
Also, could you check the MQ service if its using the same account which is supposed to be taken. (though its wierd that there aren't any logs for security error)
Usually the reason for a security error will be logged by the queue manager in its own error logs (for security reasons you don't want to give the reason the client as they could use this against you). You can find your error logs here:
C:\ProgramData\IBM\MQ\qmgrs\Mel2\errors
AMQERR01.LOG is the most recent log file.
The biggest mistake people make is trying to do MQ changes under the Administration account (Windows) or root (Unix/Linux). First, you will make a mess of things and secondly, it does not work as you think it does.
You should ONLY use the Administration or root account for the installation of MQ, after that use your own account.
If you are going to be the "MQAdmin" on your WIndows PC then:
Stop using the Administrator account for MQ
Use your OWN user account for MQ configuration/administration
Add your user account to the "mqm" group
Either restart the queue manager(s) or issue the refresh security command
Once your UserId is in the "mqm" group, you can configure your queue managers
Note: If you were configuring MQ with Administration account then I would delete EVERYTHING you did under the Administrator account and simply start over doing it the right way. Otherwise, you will be posting question after question on Stackoverflow asking why "this does not work" and "that does not work".
I was also facing same issue.
So,I have the MQMD service , right click on MQMD service, and change the log on to ‘Local System Account’ and and restarted the service and now working fine.
Related
We are trialing a test migration of a project on TFS 2010 (on prem) to #visual-studio-online using #OpsHub . During the migration phase at the user mapping window we are getting the below error message.
2015-07-08 15:10:49,916 [4] ERROR Error : The operation has timed out
at System.Net.HttpWebRequest.GetResponse() at
Microsoft.TeamFoundation.Client.Channels.TfsHttpWebRequest.SendRequestAndGetResponse(HttpWebRequest
webRequest, WebException& webException)
I am not able to find much information on-line about this error. I tried doing the migration as a TFS administrator and as a domain user who has project admin access to the project but still get these time out errors.
I saw online a user upgraded to #OpsHub 1.3 from 1.2 to overcome this issue which I tried but still doesn't help. Do we need to open any other ports for this to work apart from 80 and 443? Any suggestion as to how to over come this issue?
From the logs we find out that error is about time out from your local tfs server.
Server Error : TF400324: Team Foundation services are not available from server tfs.nextdigital.com\Next Digital.
Technical information (for administrator):
The operation has timed out
Here you need to work with your tfs admin to increase timeout parameter of your tfs.
Following thread might help you in this.
http://blogs.msdn.com/b/ablock/archive/2008/09/16/increasing-the-time-out-time.aspx
Thanks & Regards,OpsHub Support
I've successfully configured ZSS Server on my internal system (Win Server 2008R2 + IIS 7.5), and everything works fine.
Now I'm trying to install the same system on a customer machine; I've done this through the installer (latest version), he has applied the necessary security permissions, the home page of the site is visible, but syncing the db give the 1992 error.
Taking a look at IIS logs, I see that every call with GET /pull result in a 404 error code, subcode 0; there are several consecutive statements like this, all terminating wi9th 404.0 error code.
The web.config is the same as my system. What else can I check ?
You say you can reach the home page of the site - do you mean the "main" IIS home page, or the root of the ZSS site? That is, assuming Zumero is running on port 8080, what do you see when you point a browser at http://your.customer.site:8080?
I my case it was caused by the Application pool being configured for 32 bit (which it should not be). Version 1.4 has an improved installer, that should prevent this from happening
I'm trying to enable MSMQ on my development computer (running Windows 7).
I go to turn windows features on or off -> Microsoft Message Queue (MSMQ) Server Core -> Check MSMQ Active Directory Domain Services Integration AND MSMQ HTTP Support.
When I click OK, I get the error "An Error has occurred. Not all of the features were successfully changed." -> Click OK -> "You must restart your computer to apply these changes".
I've clicked Restart Now and Restart later and no matter what, same issue every time.
If I selected Restart later and go into Services...I see Message Queuing (stopped), and if I try to start the service, I get the error "Windows could not start the Message Queuing service on Local Computer. Error 0x80070005: Access denied."
I checked my privileges and I am an Admin on the machine. Just to be safe, I even logged into the machine as the actual Administrator. Same scenario.
Furthermore, when I go into the Event Viewer, I check the Application logs. I have an error with MSMQ as the Source. EventID: 2076, Error: The logger files cannot be initialized. The file QMLog in the Msmq\Storage folder is corrupted or absent. Error 0x80070005: Access denied.
If I check the System Logs, I see another error with the source being Service Control manager. Error eventId: 7023, Error: The Message Queuing service terminated with the following error: %%-2147024891
When I look up the error codes on Microsoft, there is NOTHING.
I had something like this - not sure how it came about as I always had AD integration turned ON for my MSMQ (as I needed it) but somewhere along the line, it got turned off and I couldn't turn it back on again via Control Panel - I would get the error behaviour (and restart!) that the OP describes. To fix it, I accessed my machine via the AD services manager app on one of our domain servers and deleted the "msmq" object that was under it.
I restarted my local MSMQ service on my machine AND rebooted (not sure which or both was required) and then when I checked my local registry entries, it indicated I was correctly running in AD mode once again. Everything started to work again after that.
This link was helpful in giving me the right direction to go in: Technet MSMQ delete stale objects article
when i try to run the setup.exe to start the installation, i get the following error in windows_xp:
Microsoft .NET Framework CAS Policy Manager has encountered a problem and needs to close.
this is what is in the error signature:
AppName: caspol.exe AppVer: 2.0.50727.3053 AppStamp:4889dd08
ModName: mscorwks.dll ModVer: 2.0.50727.3607 ModStamp:4add5446
fDebug: 0 Offset: 000d0494
i have tried completely removing and reinstalling all of my .net installations and it didn't resolve the issue. it's weird, because one time i tried to run setup i got two application events but subsequent tries did not produce more events.
the first event's id is 1023:
.NET Runtime version 2.0.50727.3607 - Fatal Execution Engine Error (7A09795E) (80131506)
It might be possible that the uninstallation did not remove all objects such as registry keys.
This may be of some use but I cannot verify its success rate having not used it myself.
http://www.justanswer.com/computer/5gtob-microsoft-net-framework-cas-policy-manager-encountered.html
We have an application server with the following spec’s:
• Windows 2008 R2 operating system.
• All prerequisites are configures successfully and correctly: Windows roles, MSDTC and connection to SQL DB server.
• MS Reporting Services 2008 R2 are installed and configured successfully, and all reports are deployed and render with no problems.
The application server connects to SQL Server 2008 R2 DB on different server - there are no firewalls between the 2 servers , and using UDL file, the connection is always successful using windows authentication or SQL authentication on SQL Server.
When we install “K2 blackpearl 4.5 (4.10060.1.0) with Update KB001040”, the setup completes successfully but the following exception appears when we open work list, when K2 setup manager is opened for reconfiguration and when rendering any report on the report manager: “A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.)” although all DB’s are created successfully during the installation for K2. Also all other features at K2 (any feature at Management Console) and Report Manager (deployment of reports, management of data sources, and folder/report settings) works perfectly.
When we remove K2 components from the server the reporting services works successfully again, without any reconfiguration.
We tried to move the server to new environment to check if there is a problem with the server itself, all installation and configuration are completed with no problems and the error message disappeared.
We did check all of below points:
• MSDTC configuration.
• All ports are open between the 2 servers.
• SQL connection is always successful between the 2 servers.
• We have a third server with MOSS 2007 installed and it works perfectly with problems in connection to DB.
• All users used for windows services and SQL windows connection are active and configured correctly.
o Have SQL login with dbcreator and SecurityAdmin roles.
o Are added as Administrators on Application server.
• We have tries Windows authentication and SQL authentication and they all gave the same problem.
• We have used a newer version of K2 installation files “K2 blackpearl 4.5 (4.10060.1.0) with KB001320” and it failed at the last steps of installation with the same problem.
Please help on this.
(full disclosure i work for K2) and looked through our system as well as the support forum and could not find a reference to this error. From the people i talked to it appears to be a general network issue, with quite a few possible causes, including something as simple as the network card. Although I am not 100% clear on a few points you made. When you said
"following exception appears when we open work list" Where are you opening the worklist from?
When you said
"When we remove K2 components from the server the reporting services works successfully again, without any reconfiguration."
Are you getting this error in SQL Reporting Services?
You can also post a question in http://k2underground.com someone else may have seen this.
Edit I asked around and there does not seem to be any good answers to this at the moment. Would you be willing to open a K2 support ticket and let us look at the K2 logs or see the config via livemeeting? Thanks!