Issues in Upgradation of Directory Server 5.3 Patch 3 to Patch 6

I am currently using Directory Server 5.2 Patch 3. I am trying install Patch 6 but is getting the error message
*./install.sh: ./lib/nsPerl5.005_03/nsperl: not found*
"patchzip-directory-5.2_Patch_6-us.sparc-sun-solaris2.8.tar" is this the right tar file I am using?
Please respond. Thanks in advance.
Regards,
Joydeep
Edited by: joy2009 on Jul 15, 2009 5:43 AM

You should be using patchzip 117665-05 (if you're using zip install).
What you're seeing looks like this bug
6287502 - Error ./lib/nsPerl5.005_03/nsperl: not found from install.sh when called from another directory
Are you running the installer from outside the top level directory? If so, you should run the installer after "cd" to it's directory.

Similar Messages

Login issue after upgrading sun app server 8.1 to 9.0

Hi, I recently upgraded sun application server from 8.1 to 9.0. Now when I go to my web application in my browser and try to login, its giving me an error.
System Messages We're sorry but we are unable to log you in at this time...
Error: Error in allocating a connection. Cause: Connection could not be allocated because: Access denied for user ''@'localhost' (using password: YES)
Any ideas where to start?

try to uninstall all of it and install again..
take care of your files.. backup everything

We are in the process of upgrading to Directory Server 5.1, and are currently using Netscape C SDK 4.0. Is it recommended (or required) that we update to the latest version (5.08) of the SDK as well?

No it is not a requirement that your client application uses the latest version of the C-SDK. However some bugs have been fixed in the latest version of the C-SDK and also some new features are available... so I can only recommend you to use it.
Regards,
Ludovic.

Directory Server 6.2 upgrade to 6.3: import LDIF problem

Hi all,
I have tried upgrading my Directory Server 6.2 to version 6.3 because of the database integrity issues as stated in:
http://blogs.sun.com/dsee/entry/directory_server_6_2_database
I have followed the steps defined in this article:
1. Shut down each directory server instance, as described in Starting, Stopping, and Restarting a Directory Server Instance.
2. Perform an LDIF export of the database, as described in Backing Up to LDIF.
3. Install the hotfix for bug 6642430 on Directory Server 6.2, or upgrade your Directory Server 6.2 instance to Directory Server 6.3 once Directory Server 6.3 is available for download (early April). You will need to login to Sunsolve in order to see this bug description.
But when importing the LDIF export, I got the following error:
[17/Dec/2008:14:44:08 +0100] - import ec: WARNING: Skipping entry "sunPortalAdminPortalDomainPortalServerInstanceMonitoringID=Monitoring,sunPortalAdminPortalDomainPortalServerInstanceID=sol10portal-80,sunPortalAdminPortalDomainPortalID=portal1,sunPortalAdminPortalDomainID=defaultDomain,o=example" whichIt's the only information I get about why the entry was skipped (I did not forget to copy the part after 'which', there was no information there :-))
This resulted in a missing Portal instance configuration and thus I got a 'configuration error' when surfing through the gateway to the portal.
I have also tried: manually importing that entry, which resulted in a 'Object does not exist' error. I have tried copying the whole tree from another backup with identical setup, which wasn't working either.
Did anyone experience the same problems before? Did I do something wrong or is there a workaround for this?
Second question: What is the exact reason why a export and import is necessary? Or is it only necessary if the database is already corrupt? Is there a way to check that?
Thanks alot!
Sten

The entry was not imported most likely because it's parent isn't in the database yet. Are entries above this in another backend ? If so try importing that backend first. Also, that dn is so long, that it exhausted the buffer which is used to write messages in the access log. This is why, there's nothing after "which".
What is the exact reason why a export and import is necessary? Or is it only necessary if
the database is already corrupt? Is there a way to check that?The database corruption could be silent. So a binary backup/restore when going from 6.2 to 6.3 is not recommended and the LDIF route must be used.

Issue w/ Case Differences Using the IBM Directory Server MA

We have the following issue using the IBM Directory Server MA using FIM 2010 R2 (Version 4.1.3479.0).
We provision a new object, e.g., uid=jdoe,ou=users,o=contoso, into an instance of IBM Directory Server
The object is created in IBM Directory Server as uid=jdoe,ou=users,o=contoso
A Full Import on the IBM Directory Server MA runs and confirms the export
Subsequent imports, sync, and exports run successfully
<Time passes>
A Full Import on the IBM Directory Server MA runs, and this object shows up as a staging-error (uid=jdoe,ou=Users,o=contoso)
Subsequent imports and syncs report errors on this object (staging-error)
Note that we do not manipulate the anchor (DN) of this object once it is created in IBM Directory Server. Other attributes are synchronized, but the object is never renamed/moved. This case change does not happen with all of the objects brought
in during the Full Import, but the number of instances do increase periodically. At this point, it does look like the import is changing from a lowercase "u" to an uppercase "U" but not vice versa.
I found a related
TechNet article containing the following remark:
"IBM Directory Server does not guarantee that the case of a DN component will match in all instances. On a synchronization or import from IBM Directory Server, this can manifest itself as an unexpected update. For example, if you create
O=TEST, and then create the user cn=MikeDan,O=TEST, this might be imported from IBM Directory Server as
cn=MikeDan,O=test. Because of the case difference, FIM treats this as an update on subsequent full imports."
Unfortunately, the article does not propose a resolution.
Has anyone encountered this issue? More importantly has anyone resolved this or found an acceptable workaround?
Note that deleting the connector space is not an acceptable workaround. :)

I remember experiencing this issue when we were on 5.0, and I believe it persists through 5.1 as well.
There is a comment in the 5.2 release notes that something similar was fixed:
Changing case sensitive attribute values failed in MMR. (4624693)
If I had to take a wild guess, I would say that the server does some internal checking to see if the value has changed, possibly based on the attribute syntax, to avoid replicating "changes" that really don't change anything except case. I doubt that all your custom attributes are case-sensitive, though. Enabling replication probably "turns on" this behavior, which doesn't go away even if replication is disabled.
In any case, you're probably out of luck unless/until you upgrade to 5.2.

Directory Server 6.2 - Possible Database Corruption

We have become aware of a bug in Directory Server 6.2 only that could cause database corruption. We have a hotfix for this issue, and if you are running Directory Server 6.2 and run into this problem then you should contact Sun Support and ask for the fix for the following bug
6642430: DB corruption (zero’d pages) when performing db2ldif against large 20GB ldif file.
The sunsolve record for this bug can be found at [http://sunsolve.sun.com/search/document.do?assetkey=1-1-6642430-1].
NOTE: This issue does not affect Directory Server 6.0 or 6.1 release so you only need this fix if you are running Directory Server 6.2.
After you have the hotfix for this issue on Directory Server 6.2 and have applied the hotfix, then you will have to re-initialize the database from an LDIF backup to fully correct the corruption issue. Simply applying the hotfix will not fix the database if the database is already corrupted. Database corruption can be present though not detected with data in binary formats. You must therefore rebuild the database by importing an LDIF backup.
Directory Server Enterprise Edition 6.2 is no longer available for download and Directory Server Enterprise Edition 6.3, which includes a fix for this issue, will be available for download early April. When upgrading to Directory Server 6.3 from 6.2 (not needed if you are on 6.0 or 6.1), make sure you export the database (db2ldif) prior to the upgrade and then re-import the database after the upgrade to fully re-initialize the database and to ensure that no corruption issues remain.
Recommended patch or upgrade procedures:
<ol><li>     Shut down each directory server instance, as described in [Starting, Stopping, and Restarting a Directory Server Instance|http://docs.sun.com/app/docs/doc/820-2491/6ne3dhd8u?a=view#bcaan].
</li>
<li>     Perform an LDIF export of the database, as described in [Backing Up to LDIF|http://docs.sun.com/app/docs/doc/820-2491/6ne3dhdio?a=view#ganwh].
</li>
<li>     Install the [hotfix for bug 6642430|http://sunsolve.sun.com/search/document.do?assetkey=1-1-6642430-1] on Directory Server 6.2, or upgrade your Directory Server 6.2 instance to Directory Server 6.3 once Directory Server 6.3 is available for download (early April). You will need to login to Sunsolve in order to
     see this bug description.
</li>
<li>     Re-initialize the database from the LDIF exported in step 2, as described in [Importing Data From an LDIF File|http://docs.sun.com/app/docs/doc/820-2491/6ne3dhdj4?a=view#ganwc].
     If you are running replicated instances of Directory Server, make sure you read [Restoring Replicated Suffixes|http://docs.sun.com/app/docs/doc/820-2491/6ne3dhdjc?a=view#bcajf] as well.
</li>
</ol>
Edited by: KevinLeMay on Mar 28, 2008 4:48 AM

The entry was not imported most likely because it's parent isn't in the database yet. Are entries above this in another backend ? If so try importing that backend first. Also, that dn is so long, that it exhausted the buffer which is used to write messages in the access log. This is why, there's nothing after "which".
What is the exact reason why a export and import is necessary? Or is it only necessary if
the database is already corrupt? Is there a way to check that?The database corruption could be silent. So a binary backup/restore when going from 6.2 to 6.3 is not recommended and the LDIF route must be used.

How to disable nonsecure port in Directory Server 5.2

We have recently upgraded from Directory Server 5.1 to 5.2. With version 5.1, you could set the non-secure LDAP port to be 0, and that would disable connections to the non-secure port. Version 5.2 doesn't allow you to do this. I tried from the console, and even changed it manually in the dse.ldif file, and neither method worked. Is there any way to disable the non-secure port for Directory Server 5.2?
Thanks!

I have found the simplest way is to lock the nonsecure port down to the localhost using
listenhost: 127.0.0.1
This means that it won't answer outside queries on that unsecured port, but it still has the advantage of allowing you to use it locally (which can save on the typing a bit).
Note you can of course set this to any ip or range for example 24.24.*
This also works for the secure port using securelistenhost: (I think that's the spelling but didn't check.)
Ward

Migrate from Sun One Directory Server 5.1 to 5.2

Greetings
I am trying to run the script provided with the 5.2 release MigrateInstance5; I have installed the server and have followed the instructions to a tee. I keep getting the error, Unable to start the Sun One Directory Server, when I run the script, I am at my wits end as this is supposed to be the easy step, I have to go from 4.2 to 5.2 next.
Please help.

Hello,
We upgraded our directory server version for several times.
If you want a secure method.
export your data.
Copy your schema file to the new install path, modify the information related to the old version and server (also the last line containing db number : keep only lines about the schema entry, it's ACI, objectclasse and attributes) and restart your directory.
Import your data. (you might use a script to clean your ldif file : empty attributes ...)
For the upgrade from 4.2 to 5.2 you will have to work a little bit more on the schema file as you have two of them instead of one. but the idea is the same.
edit your New schema file, keep only the following lines "
dn: cn=schema
objectClass: top
objectClass: ldapSubentry
objectClass: subschema
cn: schema
aci: ....
aci: ....
copy and paste your custom attributes and then objectclasses form the corresponding files.
On the import phase, check that you are not using objectclasses whiche were modified or suppressed.
I hope it was helpfull.

WorkGroup Manager issues since upgrading to OS X Server 10.4.1.10

Hi all.
Since upgrading our XServe [Dual 2.3GHz PowerPC G5, 6GB RAM] to OS X Server v10.4.1.10 I have had an issue where I have to quit the program and relaunch to be able to "see" a newly created network home folder. I need to view it under the Sharing tab so to assign the correct permissions since that has no longer worked since upgrading to server version 10.4.7.
Long story short is... we have our students home folder on the XServe and their preferences are managed via WGM but they use the Active Directory server for authentication. Basically our school district wanted to create a student account once and be able to use it for Windows or Mac's. Therefore, I export a user from the AD server and import the user into the Mac server ( LDAP domain) and things worked fine 2 years ago when the server was set up but now we have this... any thoughts would be appreciated.

What was the upgrade from?
What optical drive model? (There may be a firmware update on the Apple downloads to deal with Tiger.)
You might also try an NVRAM reset, as NVRAM is read early, by the machine’s boot firmware, and going back to ground zero can help. To reset NVRAM, you need to boot into Open Firmware by holding down the cmd-option-O-F key combination until you get the white Open Firmware terminal screen. Once you are there, enter the following three commands:
reset-nvram <enter>
set-defaults <enter>
reset-all <enter>
The last command will cause the machine to reboot. When you next boot, the firmware will generate a new device table and maybe cure the problem.

Directory Server setup issues.

I recently installed the new OS X Server on my new iMac. I have two iPhones, two iPod touches, the iMac and an Air that I want to serve. I registered macserved.com and have a static IP. As far as I can tell, the domain and DNS is set up correctly (to serve internal DNS). I had a wordpress blog running for a while and can access it both internally and externally. MySQL was a pain in the butt to configure, but I figured it out. When I started the config for Profile and OD however, I get this error:
An error occurred while configuring iMac as a directory server. Please check your network configuration and try again.
So I first checked my hostname:
Primary address     = 192.168.0.6
Current HostName    = macserved.com
DNS HostName        = macserved.com
The names match. There is nothing to change.
dirserv:success = "success"
A little dig output:
; <<>> DiG 9.8.3-P1 <<>> macserved.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27076
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;macserved.com.                              IN          A
;; ANSWER SECTION:
macserved.com.                    10800          IN          A          192.168.0.6
;; AUTHORITY SECTION:
macserved.com.                    10800          IN          NS          macserved.com.
;; Query time: 2 msec
;; SERVER: 192.168.0.6#53(192.168.0.6)
;; WHEN: Fri Dec 7 19:24:36 2012
;; MSG SIZE rcvd: 61
I'm not certain it is a DNS issue, but I'm fairly new to DNS setup so I cannot rule it out.
Where should I start looking? What should I be looking for in the logs? I'm cool with scraping everything and starting over as well. Right now I have zero invested in it (no files that need saved, etc) but I would PREFER not to reformat/reinstall OS X though.

I figured it out! My certificates were hosed. I rm -rf the Authority in Library/ and recreated the certs after DNS was setup properly. Works great now aside from a few other website issues, but that is another thread :-)

Can JRE for Sun One Java Directory Server 5.2 be upgraded to JRE 6.0 Update

I am trying to upgrade jre installed with Sun One Java DS 5.2 from 1.5.0 to JRE 6.0 Updat 16. Is this possible?

I never received any feedback on my question.
I am attempting to upgrade our JRE version (installed with Sun One Directory Sever 5.2) from 1.4 to 1.6. I've installed JRE 1.6 Update 16 and set the JAVA_HOME environment variable to d:\programs\java\jre6 and don't know how to configure the directory server to run the 1.6 java version. Any help would be greatly appreciated.
Edited by: CDRA on Feb 2, 2010 6:17 PM

Upgrade from Windows Server 2012 Active Directory to Windows Server 2012 R2 Active Directory

We are currently running Windows Server 2012 Active Directory and would like to upgrade to Windows Server 2012 R2 AD. Is it OK to just do an in-place upgrade, or is it advisable to build new domain controllers on R2? Are there any guides or articles anyone
can recommend?

Hi Ginandtonic,
To upgrade DC(Domain Controller) from windows server 2012 to windows server 2012 r2, please refer to these articles:
Upgrade from windows Server 2012 to 2012 R2
Upgrade Active Directory from 2012 to 2012 R2
I hope this helps.
Best Regards,
Anna

Unexpected Termination SSIS package - Issue with SSIS packages after upgrading to SQL Server 2014

Hello everyone.
We performed an upgrade of SQL Server 2012 installation to SQL Server 2014 (with last CU5 update). We found that all SSIS packages (even the simplest with just Execute SQL tasks) fail with Unexpected termination message. The issue reproduces with both new
packages (that are created from scratch with SSDT 2014) and old packages (migrated from SQL 2012).
Any ideas, please? We googled and found that it is a known issue that should have fixed with CU4. But we use CU5 and the issue is still here.
MCP

Hi. Yes...
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="SQLISServer" />
<EventID Qualifiers="0">1</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-02-12T07:41:56.000000000Z" />
<EventRecordID>469950</EventRecordID>
<Channel>Application</Channel>
<Computer>abtru1a11.oneabbott.com</Computer>
<Security />
</System>
- <EventData>
<Data>The SSIS Execution Process could not write to the IS catalog: ABTRU1A11\DEV:SSISDB Error details: Cannot find the symmetric key 'MS_Enckey_Proj_Param_5', because it does not exist or you do not have permission.; at System.Data.SqlClient.SqlConnection.OnError(SqlException
exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior
runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream,
Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion,
Int32 timeout, Task& task, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader() at Microsoft.SqlServer.IntegrationServices.Server.Shared.ExecutionParameterLoader.GetExecutionParameter() at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.ProjectOperator.StartPackage()
at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.ProjectOperator.PerformOperation()</Data>
</EventData>
</Event>
MCP

Upgrading iplanet 4.1 directory server to 5.0

Dear all
Problem goes like this:
We have netscape messaging server 4.1 ,directory server 4.1 running on NT box
we want to upgrade our mail server to 5.1 and directory server to 5.0 .
how can i get a pack of mail server 5.1 with directory server 5.0.
we are thinking to shift the system to Solaris also.
i tried first loading directory server 5.1 on solaris and then loading messaging server on the same system but using the existing directory server option . then migrating the users from old directory server to 5.1 .
when we are loading the 5.1 on solaris it's straight forward and it's getting loaded but when installing messaging server on the same system we got a problem saying that serious problem occured while installing admin server ....
and coming out.

Hi Phil,
To ensure its not permissions I'd grant the EUL Owner
the "Select Any Table" database priv and then try
again.
If it still fails I would then perform a database
trace of the session to get more details.
Finally, if that fails I would create a new 3.1 EUL
and export/import all of your business areas into
that EUL and perform the upgrade to 4.
Thanks,
JeffHi Jeff,
I'll try your suggestions.
I also did a Business Area refresh which fixed a few definitions that no longer existed but when I ran the upgrade again I got the same error.
Thanks.
Phil.

Connection issue 10.9 to a 10.6 Directory server

Hi,
I am currently facing an issue between an 10.9 client and my 10.6 open directory server. I always receive the message that my server is not responding.
All clients in my network, 10.6 and 10.7, are running well. Authentication is possible without any issue.
Many thanks in advance for your support
Richard

In the case of Personal File Sharing, yes. That did the trick for us. Our problem seemed to be specifically speaking from 10.9 client to 10.9 client running PFS which had SMB turned on.
For your group shares, what are they hosted on?
Is SMB turned on for it, and if so, can you turn it off?
We don't use group shares here, so I'm making some guesses about the interaction. So far here, we've been able to confirm that 10.9 -> 10.9 using PFS and 10.6.8 ODS doesn't work.

Issues in Upgradation of Directory Server 5.3 Patch 3 to Patch 6

Similar Messages

Maybe you are looking for