The following is a list of problems reported for iResetMe along with the solutions that we have developed for them. If you have a problem that is not covered here, ask us via E-mail and we'll address your problem.
Register your E-mail address to receive a notification when this product is updated.
Index:
iResetMe Release Independent Problem Reports:
iResetMe Release 4 Problem Reports:
iResetMe Release 3 Problem Reports:
iResetMe Release Independent Problems:
We changed to use long passwords on our system, but iResetMe is still only allowing 10 character passwords.
When you change the system value QPWDMAXLEN to a value greater than 10, you also have to make an adjustment in the Password Rules in iResetMe. This can be done using option #11 on the INSTALL menu. Look for the record for QPWDMAXLEN and edit it using option 2. Change the "Current Setting" setting to match your QPWDMAXLEN setting. You will have to repeat this process for each language that you are supporting in iResetMe on your system.
While following the instructions to create the IRESETME digital certificate, I don't see a "Local Certificate Authority" to specify.
The IRESETME certificate must be associated with the Local Certificate Authority in DCM. If you don't see the Local Certificate Authority, it probably just needs to be enabled. Select the "Fast Path" in the list of options in the left hand panel in DCM, then select the "Work With CA Certificates". Check the list displayed for LOCAL_CERTIFICATE_AUTHORITY and make sure that it is enabled. Once this has been done, then you will be able to use it at step 4.3 on the user's guide when creating your IRESETME digital certificate.
If the above process does not resolve your issue, then you may need to create a Local Certificate Authority (CA) store using DCM. Here is a link to an IBM support page that will describe the process needed. When you open this page, click on all of the plus signs (+) to see the details for the procedure.
My test email is not going through - when I look in the joblog, I see "Command failed. reason -301 negative response from SMTP server .... Relaying blocked at this site.
This message indicates that the SMTP server on your system is set to disallow email relays. For iResetMe's email feature to work, this will have to be changed. The setting is conrolled by the ALWRLY parameter (Allow relayed mail) on the Change SMTP Attributes (CHGSMTPA) command. Prompt this command using the F4 key and roll up until you see this parameter.
(Note: Your user profile must have special authority *IOSYSCFG to use the CHGSMTPA command. We recommend that you make changes to this command from a profile that is a security officer.)
When you first check this setting, you will probably find the ALWRLY set to *NONE. This will stop all email from iResetMe from being sent. Changing this value to *ALL will allow mail to be sent, but it is not the best solution to enabling email. The preferred solution is to change this value to *LIST. This will restrict email relays to only those IP addresses that you specifically authorize.
Once you have relaying configured and have specified the *LIST setting, you will then have to update the SMTP list to indicate who can relay mail. This is done using the ADDSMTPLE (Add SMTP List Entry) command. There are a lot of options for this, but as a simple example let’s set up an entry that will permit mail to be relayed from your IBM i (iSeries, AS/400). If your system has an IP address of 10.100.2.1, then you would add a relay accept transaction that looks like the following:
ADDSMTPLE TYPE(*ACCEPT) INTNETADR('10.100.2.1')
SUBNETMASK('255.255.255.255')
This entry will accept all SMTP mail that is sourced from the specific IP address indicated in the INTNETADR parameter. The subnet mask used here is coded so that only the specific IP address will be processed. You can also use this command to post a *REJECT entry to the SMTP list to indicate specific IP addresses to be rejected. Varying the subnet mask can let you define ranges of IP addresses and if you need help on how to code these entries, feel free to contact us (support@kisco.com). Once entries have been added to the SMTP list, you can delete them using the RMVSMTPLE (Remove SMTP List Entry) command. It would be nice if IBM provided a WRKSMTPLE command too, but the test system I work on has no sign of this feature.
After you get these changes made, you should end and then restart your SMTP server before testing for the results. Ending the SMTP server is done with the following command:
ENDTCPSVR SERVER(*SMTP)
and restarting it is done with the following:
STRTCPSVR SERVER(*SMTP)
We are getting a warning message about the digital certificate from our browser session when connecting the iResetMe.
We have developed instructions for this issue. Please reference the following page. It will contains instructions for the FireFox browser (which is easy to use), Chrome and for Microsoft's Internet Explorer (IE).
As we develop solutions for additional browsers, this page will be updated.
iResetMe Release 4 Problems:
The email text for a confirmation email is garbled for a user registered for Spanish Language.
We discovered a problem with the text being used that was causing the email text to get garbled. It has now bee fixed.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 4.06 version of iResetMe. The correction is available in PTF package IRPTF406. E-mail us and request the PTF package.
An update confirmation shows that a password was changed, but the profile was just reset, not changed.
When a user profile was just reset, the confirmation panel in the browser session and the optional email confirmation text both were indicating that a password reset took place. We have now fixed this so that it confirms indicating that the profile was reset only.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 4.02 version of iResetMe. The correction is available in PTF package IRPTF403. E-mail us and request the PTF package.
The remote password sync validation process is failing.
When this was reported to us, we discovered two potential issues that could cause this. First, the initial iResetMe documentation for Release 4 does not explain that the HTTPS parameter in the IRMSET command (option #9 on the INSTALL menu) must be set for the sync process to work. Check to make sure that this is set correctly according to existing documentation for that parameter.
The second potential problem that we discovered was a problem in our code that caused the sync validation to fail if the HTTPS parameter specified a numeric IP address. We have now fixed the problem and a numeric IP address can be used.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 4.01 version of iResetMe. The correction is available in PTF package IRPTF402. E-mail us and request the PTF package.
iResetMe Release 3 Problems:
Profile Monitor re-engineered.
To simplify the Profile Monitor feature, it has been completely re-engineered. This redesign clears up a number of nagging issues with this feature.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 3.13 version of iResetMe. The correction is available in PTF package IRPTF314. E-mail us and request the PTF package.
After starting the server instance with the Profile Monitor active, there is a job in the IRESETME subsystem that is using a lot of CPU%.
The job using too much CPU% is the Profile Monitor task. Under certain circumstances, it was going into a program loop. This has now been corrected.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 3.12 version of iResetMe. The correction is available in PTF package IRPTF313. E-mail us and request the PTF package.
The Profile Monitor seems to have stopped working.
Based on a report from a customer, we found that under certain circumstances, the Profile Monitor was not working correctly. This has now been identified and corrected. Along with this fix, a problem with a cleanup routine for old data areas in the application library named IRMLIB has also been fixed.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 3.09 version of iResetMe. The correction is available in PTF package IRPTF310. E-mail us and request the PTF package.
When using the Profile Monitor feature, the QSYSMSG message queue is locked.
The Profile Monitor feature has now been re-engineered to work without locking the QSYSMSG message queue. Concurrent with this change, we have also implemented new options on the server instance start and stop commands to make it easier to enforce the desired options by adding a global default setting.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 3.07 version of iResetMe. The correction is available in PTF package IRPTF308. E-mail us and request the PTF package.
When purging the Activity Log, the last purge date is not logged.
We discovered that a recent change made to the software caused this feature to stop working correctly. It has now been restored and work correctly.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 3.06 version of iResetMe. The correction is available in PTF package IRPTF307. E-mail us and request the PTF package.
We see a lot of data areas building up in the iResetMe application library.
While the buildup of data areas in the IRMLIB application library is not a problem of itself, it can lead to system degradation if the number of data areas becomes large. iResetMe has now been updated to automatically clean out old data areas that are no longer needed. This cleanup will happen once per day while the software is active and in use.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 3.02 version of iResetMe. The correction is available in PTF package IRPTF303. E-mail us and request the PTF package.
