Migrate KM folders with properties

Hello
I´m migrating my KM folders from one environment to another. I´ve been able to move my folders, my documents, all the KM properties. Everything BUT the KM Folder properties.
Properties like tbp on, approvals workflows or permissions haven´t move.
Any idea on how to do it?
Regards
Fernando

Hi
That´s what I initially did, this has been great to move all the modifications done in Layout Set and some other stuff, but this does not migrates my KM folders properties.
I´ve set on the time based publishing and the approval process in Content Management-Explorer, here I open the folder properties and change configuration. This is the configuration that has not been migrated.
Is there anything special I have to perform in ICE for it?
Regards
Fernando

Similar Messages

Automator action with dropdown to make folders with predetermined names

Is there an action/workflow that will allow me to create Folders using a dropdown menu of predetermined names for those folders?

I haven't seen one, and since no one has posted about one yet, I'll throw this out.
I modified a couple of handlers I have laying around into a Run AppleScript action that will make folders from a list of names. The list can be set in a Get Specified Text action, with the "menu" being a Choose from List action:
Tested workflow:
1) Get Specified Text (your folder names, separated by returns) for example:
Testing
Another test
My Spiffy New Folder
2) Filter Paragraphs (Return paragraphs that are not empty)
3) Choose from List (Prompt: Please choose folder names:)
4) Run AppleScript:
<pre style="
font-family: Monaco, 'Courier New', Courier, monospace;
font-size: 10px;
margin: 0px;
padding: 5px;
border: 1px solid #000000;
width: 720px; height: 340px;
color: #000000;
background-color: #FFDDFF;
overflow: auto;"
title="this text can be pasted into an Automator 'Run AppleScript' action">
on run {input, parameters}
make folders with names from a list
input: a list of names (text items)
output: a list of Finder items (aliases) created
set output to {}
set DestinationFolder to missing value -- set the destination path here if desired
try -- verify that the path is valid
set DestinationFolder to DestinationFolder as alias
on error
set DestinationFolder to (choose folder with prompt "Choose the location to make the selected folders:")
end try
repeat with AnItem in the input
GetUniqueName for AnItem from DestinationFolder -- avoid duplicates
try
tell application "Finder" to make new folder at DestinationFolder with properties {name:the result}
set the end of the output to the result as alias
end try
end repeat
return output
end run
to GetUniqueName for SomeName from SomeFolder
check if SomeName exists in SomeFolder, creating a new unique name if needed
parameters - SomeName [text]: a name.extension to check for
SomeFolder [mixed]: a folder to check
returns [text]: a unique name
set {Counter, Divider} to {"00", "_"}
set Here to -(offset of "." in ((reverse of text items of SomeName) as text)) - 1
set TheName to text 1 thru Here of SomeName
if Here is -1 then -- no extension
set TheExtension to ""
else
set TheExtension to text (Here + 1) thru -1 of SomeName
end if
set NewName to TheName & TheExtension
tell application "System Events" to tell (get name of items of folder (SomeFolder as text))
repeat while it contains NewName
set Counter to text 2 thru -1 of ((100 + Counter + 1) as text) -- leading zero
set NewName to TheName & Divider & Counter & TheExtension
end repeat
end tell
return NewName
end GetUniqueName</pre>
- the output from the Run AppleScript action is a list of aliases to the folders created, if you want that information to do something with.

Cannot open your default e-mail folders. You must connect to Microsoft Exchange with the current profile before you can synchronize your folders with your Outlook data file (.ost)

Fresh installation of Exchange Server 2013 on Windows Server 2012.
Our first test account cannot access their email via Outlook but can access fine through OWA. The following message appears - "Cannot open your default e-mail folders. You must connect to Microsoft Exchange with the current profile before you can synchronize
your folders with your Outlook data file (.ost)" is displayed.
If I turn off cached Exchange mode, setting the email account to not
cache does not resolve the issue and i get a new error message - "Cannot open your default e-mail folders. The file (path\profile name).ost is not an Outlook data file (.ost). Very odd since it creates its own .ost file when you run it for the first
time.
I cleared the appdata local Outlook folder and I tested on a new laptop that has never connected to Outlook, same error message on any system.
Microsoft Exchange RPC Client Access service is running.
No warning, error or critical messages in the eventlog, it's like the healthiest server alive.
Any help would be greatly appreciated. I haven't encountered this issue with previous versions of Exchange.

So it looks like a lot of people are having this issue and seeing how Exchange 2013 is still new (relatively to the world) there isn't much data around to answer this. I've spend ALOT of time trying to figure this out.
Here is the answer. :) - No I don't know all but I'm going to try to give you the most reasonable answer to this issue, in a most logical way.
First thing I did when I was troubleshooting this issue is that I ignored Martina Miskovic's suggestion for Step4 http://technet.microsoft.com/library/jj218640(EXCHG.150)because it didn't make sense to me because I was trying to connect
Outlook not outside the LAN but actually inside. However, Martina's suggestion does fix the issue if it's applied in the correct context.
This is where the plot thickens (it's stew). She failed to mention that things like SSL (which I configure practically useless - anyone who ever worked in a business environment where the owner pretty much trusts anyone in the company, otherwise they don't
work there - very good business practice in my eyes btw, can confirm that...) are some sort of fetish with Microsoft lately. Exchange 2013 was no exception.
In exchange 2003, exchange 2007 and exchange 2010 - you could install it and then go to outlook and set it up. And when outlook manual Microsoft Exchange profile would ask you for server name, you would give it and give the name of the person who you setting
up - as long as machine is on the domain, not much more is needed. IT JUST WORKS! :) What a concept, if the person already on premises of the business - GIVE HIM ACCESS. I guess that was too logical for Microsoft. Now if you're off premises you can use things
like OutlookAnywhere - which I might add had their place under that scenario.
In Exchange 2013, the world changed. Ofcourse Microsoft doesn't feel like telling it in a plain english to people - I'm sure there is an article somewhere but I didn't find it. Exchange 2013 does not support direct configuration of Outlook like all of it's
previous versions. Did you jaw drop? Mine did when I realized it. So now when you are asked for your server name in manual outlook set up and you give it Exchange2013.yourdomain.local - it says cannot connect to it. This happens because ALL - INTERNAL AND
EXTERNAL connection are now handled via OutlookAnywhere. You can't even disable that feature and have it function the reasonable way.
So now the question still remains - how do you configure outlook. Well under server properties there is this nice section called Outlook anywhere. You have a chance to configure it's External and Internal address. This is another thing that should be logical
but it didn't work that way for me. When I configured the external address different from the internal - it didn't work. So I strongly suggest you get it working with the same internal address first and then ponder how you want to make it work for the outside
users.
Now that you have this set up you have to go to virtual directories and configure the external and internal address there - this is actually what the Step 4 that Martina was refering to has you do.
Both external and internal address are now the same and you think you can configure your outlook manually - think again. One of the most lovely features of Outlook Anywhere, and the reason why I had never used it in the past is that it requires a TRUSTED
certificate.
See so it's not that exchange 2013 requires a trusted certificate - it's that exchange 2013 lacks the feature that was there since Windows 2000 and Exchange 5.5.
So it's time for you to install an Active Direction Certificate Authority. Refer to this wonderful article for exact steps - http://careexchange.in/how-to-install-certificate-authority-on-windows-server-2012/
Now even after you do that - it won't work because you have to add the base private key certificate, which you can download now from your internal certsrv site, to Default Domain Policy (AND yes some people claim NEVER mess with the Default Domain Policy,
always make an addition one... it's up to you - I don't see direct harm if you know what you want to accomplish) see this: http://technet.microsoft.com/en-us/library/cc738131%28v=ws.10%29.aspx if you want to know exact steps.
This is the moment of ZEN! :) Do you feel the excitement? After all it is your first time. Before we get too excited lets first request and then install the certificate to actual Exchange via the gui and assign it to all the services you can (IIS, SMTP and
there is a 3rd - I forgot, but you get the idea).
Now go to your client machine where you have the outlook open, browse to your exchange server via https://exchang2013/ in IE and if you don't get any certificate errors - it's good. If you do run on hte client and the server: gpupdate /force This will refresh
the policy. Don't try to manually install the certificate from Exchange's website on the client. If you wanna do something manually to it to the base certificate from the private key but if you added it to the domain policy you shouldn't have to do it.
Basically the idea is to make sure you have CA and that CA allows you to browse to exchange and you get no cert error and you can look at the cert and see that's from a domain CA.
NOW, you can configure your outlook. EASY grasshoppa - not the manual way. WHY? Cause the automatic way will now work. :) Let it discover that exachange and populate it all - and tell you I'm happy! :)
Open Outlook - BOOM! It works... Was it as good for you as it was for me?
You may ask, why can't I just configure it by manual - you CAN. It's just a nightmare. Go ahead and open the settings of the account that got auto configed... How do you like that server name? It should read something like [email protected]
and if you go to advanced and then connection tab - you'll see Outlook Anywhere is checked as well. Look at the settings - there is the name of the server, FQDN I might add. It's there in 2 places and one has that Mtdd-something:Exchange2013.yourdomain.local.
So what is that GUID in the server name and where does it come from. It's the identity of the user's mailbox so for every user that setting will be different but you can figure it out via the console on the Exchange server itself - if you wish.
Also a note, if your SSL certs have any trouble - it will just act like outlook can't connect to the exchange server even though it just declines the connection cause the cert/cert authority is not trusted.
So in short Outlook Anywhere is EVERYWHERE! And it has barely any gui or config and you just supposed to magically know that kind of generic error messages mean what... Server names are now GUIDs of the [email protected] - THAT MAKES PERFECT
SENSE MICROSOFT! ...and you have to manage certs... and the only place where you gonna find the name of the server is inside the d*** Outlook Anywhere settings in the config tab, un it's own config button - CAN WE PUT THE CONFIG ANY FURTHER!
Frustrating beyond reason - that should be Exchange's new slogan...
Hope this will help people in the future and won't get delete because it's bad PR for Microsoft.
PS
ALSO if you want to pick a fight with me about how SSL is more secure... I don't wanna hear it - go somewhere else...

Can I use watch folders with my network drive in Photoshop elements 10

Can I use watch folders with my network drive in Photoshop elements 10

photodrawken a écrit:
See the tips in this FAQ:
http://www.johnrellis.com/psedbtool/photoshop-elements-faq.htm#_Watchi ng_Network_Folders
Ken
Beware the FAQ you are referring to is no longer relevant. It does not apply to PSE10
Hereunder the warning issued by the author himself.
Photoshop Elements 6/7/8 (Windows) Frequently Asked Questions (FAQ)
John R. Ellis
Last updated January 21, 2011
Copyright 2008-10 by John R. Ellis
As of June 2010 I no longer maintain this FAQ. I’ve migrated to Lightroom 3, which I use for all my organizing and most of my editing (I still use the Photoshop Elements Editor for more involved editing). Adobe has clearly decided not to invest sufficient resources for properly maintaining the Photoshop Elements Organizer– see my Amazon review of PSE 8. Lightroom is marketed to professionals and prosumers with tens of thousands of photos who demand adequate organizational capabilities, whereas Photoshop Elements is marketed to consumers, most of whom do not want or use the Organizer.
This page captures my answers to frequent questions about Photoshop Elements 6, 7, and 8 (Windows). It’s mostly about the Organizer, since I know the Organizer much better than the Editor.
The versions to which each FAQ applies are indicated with the notation [PSE 6, 7, 8]. If I’m not sure whether something applies to a version, it will be indicated with a question mark, e.g. [PSE 7, 8?].
If you have corrections or suggestions, please email them to john at johnrellis.com.

Users unable to create or delete folders in migrated public folders using Outlook

We have an Exchange 2013 CU3 environment migrated from Exchange 2007.
The public folder migration was completed over the weekend.
The environment has several public folder mailboxes.
Post migration users are unable to create/delete new sub folders, or modify permissions using Outlook on any of the migrated public folders. Users can however create new top level folders using outlook. They can also create and delete new posts
in migrated public folders.
Admins are able to create folders and set permissions on migrated folders using the EAC.
Test User accounts used for testing are set to use the Primary Hierarchy mailbox as their default public folder mailbox.
Test Users have been given Owner permissions from the root down on the folders we are testing with.
We have tested with Outlook 2010 and 2013 getting the same "Cannot create the folder" error.

Further testing
We moved a top level folder from a secondary PF mailbox to the primary PF mailbox using the New-PublicFolderMoveRequest command in powershell.
After the move completed we could create new folders under the moved top level folder.
The top level folder that was moved had it's own sub-folders that we did not move to the primary mailbox. (We didn't move the whole branch.. Just the top level folder)
We still cannot create or modify the existing sub-folders after moving the top level folder.
We then moved the newly created sub-folder to a secondary PF mailbox.
At that point we could no longer create sub-folders in the folder form outlook.
From what I can tell you can only create new sub-folders in folders homed to the primary PF mailbox when using outlook.
Is this a bug or as designed?
According to this Tech ed presentation Clients connecting to a secondary PF mailbox should have folder changes proxy to the primary PF mailbox.. (See slide 10)
http://channel9.msdn.com/Events/TechEd/NorthAmerica/2013/OUC-B329#fbid=
Update : 2-5-2014
Not much new to report other than it appears that users need to be homed to the primary PF mailbox to delete calendar meetings.
Opened a ticket with Premier support.
Update 2-11-2014
Premier support continues to look into the issue. No ideas as to the cause yet.
2-24-13
Still no resolution from support or even a clue what is causing this.

I'm converting from a PC to iMac. On the PC I have many Inbox folders with PR info for distribution. How do I get these folders from the PC to the iMac?

I'm converting from a PC to iMac. On the PC I have many Inbox folders with PR info for distribution. How do I get these folders from the PC to the iMac? I've used the Windows e mail Inbox folders for an easy access filing cabinet for years, as this all goes out on e mail. Thanks for assisting me!

I think the easiest way would be to use Migration Assistant to get all that over...
http://support.apple.com/kb/HT2518
http://support.apple.com/kb/DL1415

Migrating Public folders Fatal error MapiExceptionNoReplicaAvailable

I am trying to migrate our public folders from our old 2010 server to the new 2013 one. I have created the folders (one) as per instructions and can see the structure under the name "Public" with "Mailbox1" in ecp but when I run the command
to migrate and run the check I see the error referred to above.
The full output from the get-statistics command is
RunspaceId                       : b6e18ee6-c158-40d7-a6a6-18b04c3d43d9
Name                             : PublicFolderMigration
Status                           : Failed
StatusDetail                     : FailedMAPI
SyncStage                        : CreatingFolderHierarchy
Flags                            : IntraOrg, Pull, Suspend, SuspendWhenReadyToComplete
RequestStyle                     : IntraOrg
Direction                        : Pull
Protect                          : False
Priority                         : Normal
Suspend                          : True
SourceVersion                    : Version 14.3 (Build 123.0)
SourceDatabase                   : Public_Folders
SourceServer                     : EXCSRV03.Walton.local
BatchName                        :
OutlookAnywhereHostName          :
RemoteCredentialUsername         :
AuthenticationMethod             : Basic
RemoteMailboxLegacyDN            :
RemoteMailboxServerLegacyDN      :
BadItemLimit                     : 0
BadItemsEncountered              : 0
LargeItemLimit                   : 0
LargeItemsEncountered            : 0
FolderToMailboxMap               : {\}
QueuedTimestamp                  : 2/22/2014 10:18:37 AM
StartTimestamp                   : 2/22/2014 10:18:43 AM
LastUpdateTimestamp              : 2/22/2014 10:18:46 AM
InitialSeedingCompletedTimestamp :
FinalSyncTimestamp               :
CompletionTimestamp              :
SuspendedTimestamp               :
OverallDuration                  : 01:10:03
TotalFinalizationDuration        :
TotalDataReplicationWaitDuration :
TotalSuspendedDuration           :
TotalFailedDuration              : 01:09:54
TotalQueuedDuration              : 00:00:03
TotalInProgressDuration          : 00:00:06
TotalStalledDueToCIDuration      :
TotalStalledDueToHADuration      :
TotalStalledDueToReadThrottle    :
TotalStalledDueToWriteThrottle   :
TotalStalledDueToReadCpu         :
TotalStalledDueToWriteCpu        :
TotalStalledDueToReadUnknown     :
TotalStalledDueToWriteUnknown    :
TotalTransientFailureDuration    :
TotalIdleDuration                : 00:00:02
MRSServerName                    :
EstimatedTransferSize            : 0 B (0 bytes)
EstimatedTransferItemCount       : 0
BytesTransferred                 : 0 B (0 bytes)
BytesTransferredPerMinute        :
ItemsTransferred                 : 0
PercentComplete                  : 10
PositionInQueue                  :
PreventCompletion                : True
FailureCode                      : -2147467259
FailureType                      : MapiExceptionNoReplicaAvailable
FailureSide                      : Source
Message                          : Error: MapiExceptionNoReplicaAvailable: Unable to get replica list for the folder.
                                   (hr=0x80004005, ec=1129)
                                   Diagnostic context:
                                       Lid: 40487   EMSMDBMT.EcDoRpcExt2
called [length=53]
                                       Lid: 56871   EMSMDBMT.EcDoRpcExt2
returned [ec=0x0][length=192][latency=15]
                                       Lid: 52176   ClientVersion:
15.0.516.30
                                       Lid: 50032   ServerVersion:
14.3.123.2
                                       Lid: 23226   --- ROP
Parse Start ---
                                       Lid: 27962   ROP:
ropGetOwningMDBs [66]
                                       Lid: 17082   ROP Error:
0x469
                                       Lid: 18017
                                       Lid: 21921   StoreEc:
0x469
                                       Lid: 27962   ROP:
ropExtendedError [250]
                                       Lid: 1494
---- Remote Context Beg ----
                                       Lid: 26426   ROP:
ropGetOwningMDBs [66]
                                       Lid: 3010
StoreEc: 0x8004010F
                                       Lid: 3010
StoreEc: 0x8004010F
                                       Lid: 3650
StoreEc: 0x8004010F
                                       Lid: 53151
                                       Lid: 1750
---- Remote Context End ----
                                       Lid: 26849
                                       Lid: 21817   ROP Failure:
0x469
                                       Lid: 16814
                                       Lid: 20910   StoreEc:
0x469
                                       Lid: 61040
                                       Lid: 61104   StoreEc:
0x469
FailureTimestamp                 : 2/22/2014 10:18:46 AM
IsValid                          : True
ValidationMessage                :
OrganizationId                   :
RequestGuid                      : 9929f03f-d4a3-4a1d-945c-22d8bf04d3ca
RequestQueue                     : Staff_2014
ExchangeGuid                     : 4db20d25-f308-42d9-83f2-4c104e4aed62
Identity                         : RequestGuid (9929f03f-d4a3-4a1d-945c-22d8bf04d3ca), RequestQueue:
                                   (6a17b86c-969d-4c16-8210-1d52a28eaa76)
Report                           : 2/22/2014 10:18:36 AM [EXCSRV05] 'Walton.local/Technicians/Jonathan RUBINSTEIN'
                                   created request.
                                   2/22/2014 10:18:42 AM [EXCSRV05] The Microsoft Exchange
Mailbox Replication service
                                   'EXCSRV05.Walton.local' (15.0.516.29 caps:3F) is examining
the request.
                                   2/22/2014 10:18:42 AM [EXCSRV05] Connected to target
mailbox 'Public Folders
                                   (4db20d25-f308-42d9-83f2-4c104e4aed62)', database 'Staff_2014',
Mailbox server
                                   'EXCSRV05.Walton.local' Version 15.0 (Build 516.0),
proxy server
                                   'EXCSRV05.Walton.local' 15.0.516.29 caps:03DF07FFFF.
                                   2/22/2014 10:18:42 AM [EXCSRV05] Connected to target
mailbox 'Public Folders
                                   (309db159-1c82-407f-a8f2-5e3be77323da)', database 'Staff_2014',
Mailbox server
                                   'EXCSRV05.Walton.local' Version 15.0 (Build 516.0),
proxy server
                                   'EXCSRV05.Walton.local' 15.0.516.29 caps:03DF07FFFF.
                                   2/22/2014 10:18:42 AM [EXCSRV05] Connected to source
mailbox 'Public Folders ()',
                                   database 'Public_Folders', Mailbox server 'EXCSRV03.Walton.local'
Version 14.3
                                   (Build 123.0).
                                   2/22/2014 10:18:42 AM [EXCSRV05] Connected to source
mailbox 'Public Folders ()',
                                   database 'Public_Folders', Mailbox server 'EXCSRV03.Walton.local'
Version 14.3
                                   (Build 123.0).
                                   2/22/2014 10:18:43 AM [EXCSRV05] Request processing
started.
                                   2/22/2014 10:18:43 AM [EXCSRV05] Mailbox signature will
not be preserved for
                                   mailbox 'Public Folders ()'. Outlook clients will need
to restart to access the
                                   moved mailbox.
                                   2/22/2014 10:18:43 AM [EXCSRV05] Mailbox signature will
not be preserved for
                                   mailbox 'Public Folders ()'. Outlook clients will need
to restart to access the
                                   moved mailbox.
                                   2/22/2014 10:18:45 AM [EXCSRV05] Stage: CreatingFolderHierarchy.
Percent complete:
                                   10.
                                   2/22/2014 10:18:46 AM [EXCSRV05] Fatal error MapiExceptionNoReplicaAvailable
has
                                   occurred.
ObjectState                      : New
We only use one or our existing public folders and I'm wondering about simply unlocking the structure and restoring the emails from Veeam backup. I need to get rid of the old exchange server for disk space. However I'd really like to get the
migration done properly in case we turn out to need some further stuff.
Is there any way to debug this issue and get the migration done?
Many thanks

Hi Jay,
This issue occurs because there are some legacy system folders in the public folder database.
To resolve this issue, follow these steps:
Open the Public Folder Management Console.
Expand and then click System Public Folders so that it is highlighted and populates the Result pane.
Right-click schema-root and then select Remove.
Right-click all "OWAscratchpad" entries and then select Remove.
Migrate public folders to Exchange Server 2013. For more information about how to do this, refer to the following Microsoft TechNet article:
Migrate public folders to Exchange 2013 from previous versions
More details in the following KB:
Cannot replicate public folder to Exchange Server 2013
http://support.microsoft.com/kb/2866631
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support

Public Folders with Contacts vs Address Book

Which is the better approach: public folders with contacts or setting up an address book?
I want to set up some sort of address book to hold details of some of our major clients. Rather than each person maintaining his/her own address list the plan is for everyone to maintain a single list. As soon as we deal with a "new" contact at
one of our clients that person's details go into the central list and we all benefit.
In the past we've used public folders. However, it seems to me that they are quite a hassle with OWA so i was wondering why we don't simply create a new address book with:
New-AddressList -Name "MyCo – Customers" -RecipientFilter "(CustomAttribute1 -eq 'MyCo') -and (ObjectClass -eq 'Group')" -RecipientContainer "ad.ilbs.co/Habitats/myco"
or should I use New-OfflineAddressBook -Name ...
Our team run a variety of systems (Windows and Mac) and a variety of phones (mostly IOS and Android)
Roger

Hi Roger,
According to your description, you want to share the contact which is created by each client users in OWA and Outlook to all other domain users for contact sharing. Is it right?
If that is the case, the Public Folder is an option to achieve this as you mentioned. For address list in server side, only the administrators who have related permission to Exchange server can create an address list in Exchange server generally.
For client users, they can’t create the address list for all other users using, though the contact folder permission is set to reviewer for all other users.
If you are using Public Folder contact (default folder permission set to Author), each user can create contacts in this folder and the contact can be visible for all users. Then the client user can do the following settings in Outlook to
manually add the Public Contact to address book:
1. In Outlook, open Public Folder.
2. Right-click Public Contact folder, select Properties.
3. In Outlook Address Book tab, check Show this folder as an e-mail Address Book.
4. Click OK to save the setting.
Then the Public Contact folder should be added in the Address Book.
Regards,
Winnie Liang
TechNet Community Support

2010 to 2013 PF migration - mailenabled folders not working

After migrating public folders from 2010 to 2013 it is not possible to send mail to mailenabled folders. Mails are stuck in the queue until timing out.
Problem seems to be that LegacyExchangeDN is not updated during migration, it still points at the old location. Only cure I have found so far is mail disable and enable each folder to update LegacyExchangeDN, but I am looking for an easier solution.
LegacyExchangeDN before mail disable/enable:
/O=CMPANY NAME/OU=FIRST ADMINISTRATIVE
GROUP/CN=RECIPIENTS/CN=FOLDER NAME....
LegacyExchangeDN after mail disable/enable:
/CN=Mail Public Folder/CN=Version_1_0/CN=341472c0-a48b-4f42-aca0-372ab8c3c6e7/CN=000000007D2DD1F167......
Any input is appreciated

Its a known issue.
I don't think there is anyother solution.
Hope you are aware that you can disable bulk and enable them back.
Satheshwaran Manoharan | Exchange 2003/2007/2010/2013 | Blog:http://www.careexchange.in | Please mark it as an answer if it really helps you ------------- I do not represent the organisation I work for, all the opinions expressed here are my own. This
posting is provided "AS IS" with no warranties or guarantees and confers no rights.

Public folder migration: Whats wrong with this Folder to mailbox file?

Hi,
This is my Folder to Mailbox file, migrating public folders from 2010 to 2013:
"FolderPath","TargetMailbox"
"\","Hierarchy-PF"
"\IPM_SUBTREE\Office1","Office1-PF"
"\IPM_SUBTREE\Office2","Office2-PF"
"\IPM_SUBTREE\Office3","Office3-PF"
"\IPM_SUBTREE\Office4","Office4-PF"
All these PF mailboxes live in a dedicated database. But only the mailbox DB containing Hierarchy-PF is growing and my initial migration (New-PublicFolderMigrationRequest / Step 5 in the technet article) is over 50% percent complete. This mailbox is going
to be over 300GB big and I gather the limit is 100GB, I'm sure that can be exceeded without problems, but I had several different reasons splitting the mailboxes and data the way I wanted above.
Questions:
1. How do I achieve the end result I want? Do I need to add a \ to the end of the office1-5 ipm_subtree perhaps?
2. Is there any problem with me stopping the existing migration, deleting that request/mailbox/DB and starting over?
Thanks.

Hi,
From your description, it seems that all public folders are migrated to the public folder mailbox "Hierarchy-PF".
Please run the following command to check if these migrated public folders are under the public folder mailbox "Hierarchy-PF".
Get-PublicFolderStatistics | ft Name, MailboxOwnerId
And please use the following command to check migration report.
Get-PublicFolderMigrationRequest | Get-PublicFolderMigrationRequestStatistics -IncludeReport | fl
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Migrating Public folders, can't log in

We are using a Linux Sles 10 Server with GW 7.02 beta. User migrations work
fine. We pre-create them and then update the Data Migration CSV file with
their User ID and Password assigned when they were created. Security is set
to low. However, we can figure out how to migrate the public folders. All
we get is "can't log in".
Ideas would greatly be appreciated as this is our last piece in moving from
Exchange to Groupwise.

I can't remember exactly how this works, but public folders get migrated to GroupWise as folders that are owned by a 'resource' object, and everyone is given rights to proxy into the resource's account. Resource objects in GroupWise need to have an 'owner' that is a valid GroupWise user. So, if you're having login issues, it may be something to do with the owner of the resource. The utility needs to log in as the user in order to make changes, so it needs to have the owning user's password available.
Is the owner of the resource(s) that will house the folders included in the CSV file? Is the password specified there?
It seems like if you let the utility create the users and generate random passwords it goes pretty smoothly. You don't have to manually edit the CSV file in that case.
>>> Pat H.<[email protected]> 4/12/07 7:17 PM >>>
We are using a Linux Sles 10 Server with GW 7.02 beta. User migrations work
fine. We pre-create them and then update the Data Migration CSV file with
their User ID and Password assigned when they were created. Security is set
to low. However, we can figure out how to migrate the public folders. All
we get is "can't log in".
Ideas would greatly be appreciated as this is our last piece in moving from
Exchange to Groupwise.

How to fix AppleEvent handler failed error with command "make new mailbox with properties"

Below is the script I am running to create a hiearchy of new mailboxes inside "ON MY MAC" folder area.
tell application "Mail"
make new mailbox with properties {name:"ABar"}
make new mailbox with properties {name:"ABar/Foo"}
make new mailbox with properties {name:"ABar/Foo/Me"}
end tell
When I execute this the first mailbox is excuted fine but right afterwards I get the following error:
error "Mail got an error: AppleEvent handler failed." number -10000
I have tried adding delays but this does not work either. Code:
tell application "Mail"
make new mailbox with properties {name:"ABar"}
delay 0.2
make new mailbox with properties {name:"ABar/Foo"}
          delay 0.2
make new mailbox with properties {name:"ABar/Foo/Me"}
end tell
However rerunning the script and skipping over the make command if the folder already exit, causes the next exuction time to create one more folder.
Code:
tell application "Mail"
          if (mailbox "ABar" exists) = false then
make new mailbox with properties {name:"ABar"}
                    delay 0.2
          end if
          if (mailbox "ABar/Foo" exists) = false then
make new mailbox with properties {name:"ABar/Foo"}
                    delay 0.2
          end if
          if (mailbox "ABar/Foo/Me" exists) = false then
make new mailbox with properties {name:"ABar/Foo/Me"}
                    delay 0.2
          end if
end tell
** Anyone know how to solve this or why this is happening? **
It almost feels as if the hiearcgy is read into memory and this is not updated after the creation of the new mailbox.
Thanks!

Hi,
The processors are different archiectures and you can not use binaries from one architecture to work on the other.
Library name suffix differences is an example of the importance of this. Tuxedo 6.5 was separately built for each of those architectures and
is available on the PeopleSoft distribution as distinct binaries. If your migration was purely from HPUX11.11 to HPUX11.23 you might have
succeeded but the processor difference will not work for you and a core dump would not be unexpected.
Bob Finan
FYI:
Tuxedo 6.5 is end-of-lifed and, since it's EOL has passed the stage for extended support possibility, no new patches will
be created for it by engineering. You should look to migrate to a newer version of Tuxedo/Peoplesoft at the earliest
possiblity.

SAP on V6R1 - ABAP Import:Program 'Migration Monitor' exits with error code

Hello,
We are doing an installation of SAP NW 7.01 SR1 on V6R1.
 
We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
 
We are again getting error in following steps:
 
sapinst.log
 
 WARNING 2009-09-30 23:25:28.477
Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
J9VM - 20090309_31291_BHdSMr
JIT - 20090210_1447ifx1_r8
GC - 200902_24)
I mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
 Loading of 'SAPNTAB' import package: OK
 Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28. 
Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28. 
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28. 
Loading of 'SAPAPPL1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28. 
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28. 
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28. 
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28. 
Loading of 'SAPSDIC' import package: OK
Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28. 
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28. 
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28. 
Loading of 'FUPARAREF' import package: OK
Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28. 
Loading of 'TODIR' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28. 
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28. 
Loading of 'E071K' import package: OK
Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28. 
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28. 
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28. 
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28. 
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28. 
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28. 
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28. 
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28. 
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28. 
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28. 
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28. 
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28. 
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28. 
Loading of 'SAPAPPL0' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28. 
Loading of 'SAPSSEXC' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28. 
 
WARNING[E] 2009-09-30 23:25:28.524
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
 
ERROR 2009-09-30 23:25:28.914
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
 
 import_monitor.log.
 ****************************************************************************************************************************************************
 INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
 
INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
 
INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is successfully completed.
 
WARNING: 2009-09-30 23:31:31
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-09-30 23:31:31
1 error(s) during processing of packages.
INFO: 2009-09-30 23:31:31
Import Monitor is stopped.
 *************************************************************************************************************************************************
 SAPAPPL02.LOG
 **************************************************************************************************************************************************
 TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: TVV1 created #20091001110304
 
(DB) INFO: TVV1 deleted/truncated #20091001110304
 
(IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
 
(DB) ERROR: DDL statement failed 
(ALTER TABLE "TVV1" DROP PRIMARY KEY ) 
DbSlExecute: rc = 99 
(SQL error -539) 
error message returned by DbSl:
Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
Your inputs will help a lot.
Regards,
Prasad

Hello,
We are doing an installation of SAP NW 7.01 SR1 on V6R1.
 
We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
 
We are again getting error in following steps:
 
sapinst.log
 
 WARNING 2009-09-30 23:25:28.477
Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
J9VM - 20090309_31291_BHdSMr
JIT - 20090210_1447ifx1_r8
GC - 200902_24)
I mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
 Loading of 'SAPNTAB' import package: OK
 Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28. 
Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28. 
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28. 
Loading of 'SAPAPPL1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28. 
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28. 
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28. 
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28. 
Loading of 'SAPSDIC' import package: OK
Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28. 
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28. 
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28. 
Loading of 'FUPARAREF' import package: OK
Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28. 
Loading of 'TODIR' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28. 
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28. 
Loading of 'E071K' import package: OK
Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28. 
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28. 
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28. 
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28. 
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28. 
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28. 
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28. 
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28. 
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28. 
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28. 
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28. 
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28. 
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28. 
Loading of 'SAPAPPL0' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28. 
Loading of 'SAPSSEXC' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28. 
 
WARNING[E] 2009-09-30 23:25:28.524
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
 
ERROR 2009-09-30 23:25:28.914
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
 
 import_monitor.log.
 ****************************************************************************************************************************************************
 INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
 
INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
 
INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is successfully completed.
 
WARNING: 2009-09-30 23:31:31
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-09-30 23:31:31
1 error(s) during processing of packages.
INFO: 2009-09-30 23:31:31
Import Monitor is stopped.
 *************************************************************************************************************************************************
 SAPAPPL02.LOG
 **************************************************************************************************************************************************
 TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: TVV1 created #20091001110304
 
(DB) INFO: TVV1 deleted/truncated #20091001110304
 
(IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
 
(DB) ERROR: DDL statement failed 
(ALTER TABLE "TVV1" DROP PRIMARY KEY ) 
DbSlExecute: rc = 99 
(SQL error -539) 
error message returned by DbSl:
Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
Your inputs will help a lot.
Regards,
Prasad

SAP ECC error:'Migration Monitor' exits with error code 103.

Hi All,
I am doing SAP ECC installation for windows 32 bit with MAXDB as backend.
I am stuck at the import ABAP.Getting error
ERROR 2008-08-08 16:10:53
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
1) imort_monitor.java.log-->contains
java version "1.4.2_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
Import Monitor jobs: running 1, waiting 0, completed 18, failed 0, total 19.
Loading of 'SAPVIEW' import package: ERROR
Import Monitor jobs: running 0, waiting 0, completed 18, failed 1, total 19.
2)import_monitor.log
ERROR: 2008-08-08 16:10:36 com.sap.inst.migmon.LoadTask run
Loading of 'SAPVIEW' import package is interrupted with R3load error.
Process 'D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe -i SAPVIEW.cmd -dbcodepage 4103 -l SAPVIEW.log -nolog -c 0' exited with return code 2.
For mode details see 'SAPVIEW.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
INFO: 2008-08-08 16:10:52
All import packages are processed.
WARNING: 2008-08-08 16:10:52
1 error(s) during processing of packages.
INFO: 2008-08-08 16:10:52
Import Monitor is stopped.
3)SAPVIEW.log
error message returned by DbSl:
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE VIEW "Z_T_CO_BW" ( "KOKRS" , "KOSTL" , "VERSN" , "KSTAR" , "WOG001" , "MEG001" ) AS SELECT T0002."KOKRS", T0002."KOSTL", T0001."VERSN", T0001."KSTAR", T0001."WOG001", T0001."MEG001" FROM "COSS" T0001, "CSKS" T0002 WHERE T0002."MANDT" = T0001."MANDT")
DbSlExecute: rc = 103
(SQL error -942)
error message returned by DbSl:
(DB) INFO: disconnected from DB
D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe: job finished with 3108 error(s)
D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20080808174211
Only SAPDB: SAPSID srvice of SAP DB is only up.
No other services of database are up.And i am not able to up the other services also.
Is it required to up the other services?
If not?
Why this error is occuring?
Any help will be appreciated.
Thanks&Regards
Manisha das

Hello Manisha,
The one of the possible reasons for this is due to lack of H/W.
Increase your RAM size to atleast 2GB and utilise the same while you are installing ECC in database parameters step..
If the issue is with H/W, then this should fix the issue.
Hope it helps,
Regards,
Satish.

Sharing two folders with the same name

Hi all.
I have two folders with the same name and I would like to be able to share these under different share names. Problem is, this doesn't seem to be possible.
For instance, try doing this in File Sharing under Server Preferences:
* Click +, add /Data/Media
* Edit permissions on "Media" to permit guest access
* Click +, add /Volumes/Drobo/Media
* Edit permissions on "Media" (make sure you click the right one!) to permit guess access.
This appears on the surface to work, but what it has actually done is to delete the share for /Data/Media. If you exit the File Sharing pane and go back into it again, it will be gone.
Server Admin has the ability to rename a share's name from AFP,SMB,FTP,etc. but this doesn't appear to help either -- I tried adding the second media first, renaming its shared name to Media2 over in Server Admin, and then adding the first. Server Preferences just deletes the second one.
Such a basic thing as being able to rename the share from Server Preferences would appear to be enough to get around this, but since Apple didn't make it possible, I have no idea how to proceed.
Does anyone else have this working, and how did you do it?

The best way to solve this, would be make sure you use database paraneter GLOBAL_NAME, to change your database from lets say orcl1 to orcl1.mycorpdomain.com, by this you can make sure each database actualy has a different name. Your other database then could be named orcl1.example.com.
When chaning the display name in EM you might face other issues later on when for instance trying to run a restore using EM for one of these databases.
Regards
Rob
http://oemgc.wordpress.com

Migrate KM folders with properties

Similar Messages

Maybe you are looking for