I have seen this error in the group but not a satisfactory answer. Is this
possibly happening because customizations were developed on a US English box
and then rolled out on an International English box?

TIA

After doing the xml import:

Event Type: Error
Event Source: DMSNAPIN
Event Category: None
Event ID: 0
Date: 11/08/2004
Time: 10:34:17
User: N/A
Computer: XXXXXX
Description:
PopulateStringMap Error : Object reference not set to an instance of an
object. , StackTrace : at
Microsoft.Crm.Tools.ImportExportXml.XmlCustomizati on.PopulateStringMap(Objec
t Progress)

Hi:

Could you please detail the steps you follow that generatethis error?

John.


"Stephen Redmond" <noreply__stephen@crm.ie> wrote in message
news:uLzAfQ5fEHA.2468@TK2MSFTNGP12.phx.gbl...

Yes. The schemas for the two localizations are incompatible for transporting
customizations between the two. There is no work round. You have to manually
rebuild customizations for the correct localization.




"Stephen Redmond" <noreply__stephen@crm.ie> wrote in message
news:uLzAfQ5fEHA.2468@TK2MSFTNGP12.phx.gbl...

Hi,

This occurs in the Event log when you import an XML file in the deployment
manager. The XML file was extracted from a test/dev system on a US English
system. The "live" system is International English (Irish to be precise).



Stephen



"John" <John@nospam.com> wrote in message
news:OoolBS6fEHA.3476@tk2msftngp13.phx.gbl...

Stephen,

The exported ucstomizations are localized, so they can't be imported directly to
a system with a different locale. One way to try to work around it would be to
edit the resulting XML. You'd have to first get a "clean" version from your
destination system and then manually edit the file from the other system to
change any language code references. Not sure how many there are, but there
could be quite a few, so this may take awhile.

Matt Parks
MVP - Microsoft CRM

----------------------------------------
----------------------------------------
On Wed, 11 Aug 2004 14:51:24 +0100, "Stephen Redmond" <noreply__stephen@crm.ie>
wrote:

Hi,

This occurs in the Event log when you import an XML file in the deployment
manager. The XML file was extracted from a test/dev system on a US English
system. The "live" system is International English (Irish to be precise).



Stephen



"John" <John@nospam.com> wrote in message
news:OoolBS6fEHA.3476@tk2msftngp13.phx.gbl...

Hmmm. That is what I though as well.

When I got the XML file from the customer's site, it contained the
attributes that error messages said were not created!

I am going on-site today, so I may be able to resolve it.


Stephen

"Matt Parks" <mattp65@RemoveToX_XYahoo.com> wrote in message
news:nlknh0d9ammok9kehcdvleobiggo2i0ai6@4ax.com...

OK,

I was on site on Friday - with the goal of rebuilding the customizations
there. When I got there, I discovered that the errors that the
implementation guy had found weren't true! There where errors in the event
log that custom fields could not be created - all the fields where there.
All the customizations were there. Everything worked. Everything sync'ed
out to the SFO clients and worked as expected there. Very strange.

Only one thing was awry - some of the views have no headers, the header text
is blank. Any ideas on that?


Thanks,


Stephen


"Peter Lynch" <anon@anon.com> wrote in message
news:%23nRHNp6fEHA.904@TK2MSFTNGP09.phx.gbl...

Stephen

These are the specific symptoms of the non-portability I described:

1. No headings on most/any list views
2. When you try to customise any form, all tabs are empty and you cannot do
any more customisations in situ

Sorry, you will have to manually rebuild and you - should do it before the
users spend time entering data into an incompatible system!

Sorry to be the bearer of bad tidings; this same thing happened to me
earlier this year

Peter
"Stephen Redmond" <noreply__stephen@crm.ie> wrote in message
news:ODCTVl4gEHA.644@tk2msftngp13.phx.gbl...

Hi Peter, thanks for the info.

This really is incredible to me. The very fact that this is XML means that
it should be portable between sites - no matter what the language - but
especially between 2 English sites!!!

I have investigated the XML file that I exported from the dev system and it
would appear to look fine. For example, the layout for the "My Active
Leads" view looks like this:

<LayoutXml Name="My Active Leads">
<grid name="resultset" object="4" jump="fullname" select="1" icon="1"
preview="1">
<row name="result" id="leadid">
<cell name="fullname" desc="Name" />
<cell name="subject" desc="Topic" width="200" />
<cell name="statuscode" desc="Status Reason" width="100" />
<cell name="createdon" desc="Created On" width="125" />
</row>
</grid>
</LayoutXml>

However, when I look at it in the new database after the import, all the
descriptions have been pulled out.

<LayoutXml Name="My Active Leads">
<grid name="resultset" object="4" jump="fullname" select="1" icon="1"
preview="1">
<row name="result" id="leadid">
<cell name="fullname" desc="" />
<cell name="subject" desc="" width="200" />
<cell name="statuscode" desc="" width="100" />
<cell name="createdon" desc="" width="125" />
</row>
</grid>
</LayoutXml>

How the hell has this happened??? We are not talking Chinese to English
(where there might be an incompatibility with the double-byte character
set). This is English to English!

Of course, the customer will be perfectly happy to pay for my time and
effort to resolve this - NOT!!!


Stephen


"Peter Lynch" <anon@anon.com> wrote in message
news:%23ry3ny4gEHA.3864@TK2MSFTNGP10.phx.gbl...

It seems incredible - but it is true. I've been there, done it, with MBS
support !

The key point is that the two 'english' schemas are different!!

This will be fixed in Version 2, I believe

Peter
"Stephen Redmond" <noreply__stephen@crm.ie> wrote in message
news:Oiwa3A5gEHA.1292@TK2MSFTNGP10.phx.gbl...

Hi Peter,

I have resolved this (apparently - everything appears to work perfectly) by
a very simple step. I did a find and replace in the XML file and replaced
all instances of

languagecode="1033"

with

languagecode="2057"

(2057 = English, United Kingdom)

Then I reimported the file. And now all is right with the world. All the
views display correctly and can be edited and all the forms can be edited.

Worth looking at if you encounter the issue again.


Stephen


"Peter Lynch" <anon@anon.com> wrote in message
news:O2W3yF5gEHA.3236@TK2MSFTNGP10.phx.gbl...

Well done and thanks

Peter


"Stephen Redmond" <noreply__stephen@crm.ie> wrote in message
news:O0mkwxSiEHA.2664@TK2MSFTNGP11.phx.gbl...