I have installed HP ALM 11.52 on windows server 2008 r2 for learning purpose. I have used sql sever 2008 and iis 7. I have installed and configured the ALM successfully to use on local machine. Now i can login into the site administration using valid credentials but I can't login into the site as user. while login it's show me this error
Following client components were not downloaded successfully.
1. QAIAD.dll
This file has no digital signature or the publilsher is untrusted.
Close all connections to server and try again.
I have searched the internet and found some solutions like,
put localhost:8080/qcbin into trusted site and lower the security level in IE
Disable the check for valid digital sign, valid publisher certi, valid server certi under advanced tab in IE version 10,
cleared the local temp data. And Run the IE as Administrator
Registed Hp client from tool but same error.
But all these didn't work for me. I have wasted almost a day to solve this but found no solution.
So, please help me solve this issue.
Please check the attached snapshot of issue.
problem image
Append to the end of the URL the following:
?cancelcrlcheck=true
Related
I can't do anything in server manager. I have tried enabling "Allow Remote Shell Access" in GPO. This is ridiculous how this just doesn't work for software costing OVER A THOUSAND DOLLARS!
UPDATE: Microsoft just doesn't know what the hell they're doing, they make an operating system for "datacenters" and yet their bulls****y OSes come broken. Now, if their OS was working, when the value found at "WSMAN:\localhost\Shell\AllowRemoteShellAccess" says "True", you'd think that it really is true, but it just isn't. Microsoft is a billion dollar company built on broken software and utterly horrible customer support.
Have you tried installing the required features from a different server's Server Manager by adding this server as a remote server ?
This is how I worked around the issue. It seemed the local server manager on the specific server had issues.
I tried all the recommended stuff - Allow Remote Shell Access; gpupdate /force in an admin window; WM service restart. All to no avail. BUT simple Windows restart fixed it. OMG!
Can anyone tell me why I'm getting the following error when installing BizTalk 2013 R2 CU2:
BtsDeploySystemAssemblyTask has stopped working
I might have had this same problem recently and the solution was to run the update as a different user that had more permissions and it worked.
Since the error is coming up through the SqlClient, you need to make sure the running user has high level permissions to all the databases or even the entire SQL Server Instance.
Sorry :( but since it was a single event, we had no opportunity to repro or investigate though the successful user was a fully sysadmin on SQL Server and Domain Administrator.
I've been trying to host Jabbr on AppHarbor.
The guide here is not up to date as Jabbr doesn't have a dependency on Janrain anymore.
Steps I have done:
Installed the SQL Express addon.
I've pushed the latest Jabbr code from GitHub to the AppHarbor.
Changed the connection string with the full connections string from
configuration.
Updated jabbr:encryptionKey and jabbr:verificationKey (as David Flower suggested).
The application manage to loads up, I can usethe default login screen, I can create a new user, but when the application crashes after login was successful (I think).
It is showing Server Error
500 - Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed.
When using the AppHarbor owns Errors pane, it shows nothing related.
What is the best way to debug this?
Thanks!
Ariel
I've promised to take a look at an old DotNetNuke installation for a client with the intention of making a few, hopefully minor, changes. The installation is rather old - I believe version 3.0.013 - and the production copy is running against SQL Server 2000, Windows 2003 and .Net 1.1.
As the production server is live and significantly used we need a development installation first. I have attempted to install a copy on my local server - Windows 2003, SQL Server 2005, .Net 2.0, and although with a few tweaks I can successfully get it to display the site, I cannot login, or even access the login module (ie just putting in blank username and password attempting to generate a 'must enter username' type error) without getting the error 'Object reference not set to an instance of an object'
I've spent some time trying to get around this error, without success, although I am hampered by not having used this package before.
So my questions are
Has anyone managed to run DotNetNuke 3.0.x with this configuration (or do I need to setup a box with SQL 2000 and .Net 1.0 to get it to run)?
Any suggestions where I should start looking for this error, or has anyone come across anything similar before?
EDIT: Eventually chickened out and installed in on an old webserver with Win2003/SQL 2000/Net 1.1 and it went in fine on an identical install. So I guess the answer is no, it doesn't work straight out of the box.
My feeling is that you shouldn't have any trouble running in the above mentioned environment. But taking a closer look at the error itself will help us to prove that.
If the error is occurring only when you navigate to the Login module, it may be an issue loading the authentication provider. The best way to find out is to look in the DNN Event Log and take a look at the full error message.
Because you can't login to access the Event Log, you should probably just take a look at the row created in the database when you receive the error. The table is called EventLog and there may be a little bit of friction in parsing the error message out, as all of the details are stored in the database in an XML format.
In general, when moving a site from one environment to another there are only a couple of things that you'd need to do:
make sure you can connect to the database
set the file system permissions
It sounds like you already have database connectivity because you can load the site.
However, you may want to double check (just re-apply) the file system permissions for the root of the website on the machine in question. Make sure the identity of the website (typically ASP.NET Machine Account or Network Service) has 'Modify' permissions on the root website directory. Perhaps the web site can't load a particular assembly due to lack of permissions.
I run Vista (business x32) on my work machine, in which I do ASP.NET development. Because I use IIS to server the sites I build (I do a lot of CMS integrations so I need to use IIS not the inbuilt web development server) I always need to attach to w3wp for debugging.
The problem is that w3wp requires elevated permissions for me to connect to the processes from VS 2008. But when I try and restart VS to "run as administrator" I get the error:
"This program has been blocked"
"Your administrator has set a policy to block this program"
I only get this problem when I'm logged into my machine with my domain account (which is in the local admin group), if I use the local admin I have no problems.
I'm the only person on the domain who has this problem, everyone else using Vista can open VS as an administrator no dramas.
To get around this I have to turn off UAC, but it always turns itself back on (after each restart), so this is highly frustrating.
I've not been able to find out how to add a program to the "safe" list either.
Have you asked the Domain Admins if they have a Group Policy which is re-enabling UAC?
It may be that Vista by default has only a few places that can run unrestricted and if you have Visual Studio installed outside those areas, it may be preventing it from running with elevated permissions.
Check where it is installed, and add its location as an "unrestricted" area within the Softwware Restrictions / Additional Rules area.
To do this follow these steps:
Open the secpol.msc editor.
Browse to Local Policies / Software Restriction Policies / Additional Rules.
Then right click the right window and choose New Path Rule...
Browse to the path where VS is installed and set the Security Level to Unrestricted.
See if that doesn't do the trick.
Good Luck!
You could write a script that disables UAC and then run that script every time you restart your computer, or maybe just before you launch VS.
Modify registry:
How to Disable or Enable Vista User Access Control in Command Prompt
More options for disable/enable UAC:
How to Disable and Turn Off UAC in Windows 7
I can open VS with "Run as administrator" under my domain account (which is in the local admin group) on my work computer, so I suspect something is wrong on your computer. And by now, you may have had you PC re-imaged, so perhaps the problem went away for you.