Filtered Index
Search
Shameless Plugs
Most Popular
Who's online
User login
Filtered by: Error messages
4388
Apache2 could not bind to address 0.0.0.0:631 after vSphere upgrade
After the upgrade from vSphere 4.0x to vSphere 4.1 or ESXi 4 to ESXi4.1 apache on a OES 2 server wouldn't start with the error: apache2 could not bind to address 0.0.0.0:631 after vSphere upgrade
As you all probably know TCP port 631 is for IPP print, or for us Novell guy's iPrint. iPrint is started with apache (the website that is). But if iPrint cannot start, apache wouldn’t start also. So what's blocking TCP port 631?
Submitted by: mwilmsen on Wed. 11.17.2010
Filed Under:
Collaboration Cool Solutions, Cool Solutions, Open Enterprise Server Cool Solutions, All Tech, All the Time
Topic: All-Tech OES, Error messages
Product: Open Enterprise Server, Open Workgroup Suite, openSUSE
4886
0
Novell Access Manager – “Detected URL Tampering”
There are several reasons that cause the NAM to detect URL Tampering. Most often it is a name resolution issue stemming from improper DNS or HOSTS file configuration in your environment. Still, even with proper configuration your users may, appropriately, get this message. The reason may stem from users having become accustomed to using web server host or “short names” to access the web server/app before it was protected by Access Manager. If that is the case, this article will show you when and how you can configure NAM to allow “short name” access using the Virtual Mult-homing feature.
Submitted by: pmckeith on Wed. 11.17.2010
Filed Under:
Identity & Security Management Cool Solutions, Cool Solutions
Topic: Access Control, Administration, Authentication, Browsers, Configuration, Deployment, Error messages, Gateways, Identity & Security Management, Links, Partners, Policies, Secure Access, Single Sign-on, Tips for Administrators, Troubleshooting, WebAccess
Product: Access Manager, Compliance Management Platform, iChain, Identity-Driven Computing, Secure Identity Management
3342
0
Error Codes of the SOAP Driver - Part 1
Recently I was working on a SOAP driver to talk to Salesforce.com, and had collected some errors I would like to talk about. Some of these errors are specific to Salesforce.com, and others are more generic and related to SOAP in general.
Submitted by: geoffc on Mon. 11.08.2010
Filed Under:
Identity & Security Management Cool Solutions, Cool Solutions, All Tech, All the Time
Topic: All-Tech IDM, Error messages
Product: DirXML, eDirectory, Identity Manager, Identity Manager 3.5
4057
0
Repairing Damaged Access Gateway Objects in Access Manager 3.1
Recently, I got hit with the sporadic Missing LAG/"Null Value" bug. For those that are unfamiliar with this little feature, I'll give you the scenario.
Submitted by: mfaris01 on Fri. 09.10.2010
Filed Under:
Identity & Security Management Cool Solutions, Cool Solutions
Topic: eDirectory, Error messages, iManager, Java, Objects, Technical Information Document (TID), Tips for Administrators, Troubleshooting
Product: Access Manager, eDirectory, iManager
4419
0
Diagnosing a 6038 Error in Identity Manager
Geoffrey Carman shares some helpful troubleshooting tips on how to fix a "6038 UNKNOWN ERROR" in Identity Manager.
Submitted by: geoffc on Fri. 01.08.2010
Filed Under:
Identity & Security Management Cool Solutions, Cool Solutions
Topic: Error messages, Troubleshooting
Product: DirXML, eDirectory, Identity Manager, Identity Manager 3.5
5744
2
Active Directory Driver Error Messages - Part 5
As I continued working through the process of deploying a new set of drivers, I found even more errors than I had covered in the first four articles, so here comes part five of a continuing series.
Submitted by: geoffc on Wed. 11.25.2009
Filed Under:
Identity & Security Management Cool Solutions, Cool Solutions
Topic: Drivers, Error messages, Identity Management, Troubleshooting
Product: DirXML, eDirectory, Identity Manager, Identity Manager 3.5
2