|
Home > Archive > Commerce Server General > September 2004 > Commerce 2002sp3 on Windows 2003, can't change profiles data source.
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Commerce 2002sp3 on Windows 2003, can't change profiles data source.
|
|
| Shane M Ryan 2004-09-22, 9:47 pm |
| Commerce 2002sp3 on Windows 2003, can't change profiles data source. Steps
to reproduce:
1) Backup commerce database on old platform.
2) Restore database to new platform using Windows 2003.
3) Go to "Global Resources", "Profiles", "Profile Catalog", "DataSources",
"ProfileService_SQLsource"
4) Right click "ProfileService_SQLsource" choose properties.
5) Partitions.
6) Click under Name column "SQLSource"
7) Click "Edit", "Edit" put in new SQL Server name or IP address.
8) Click Ok, Ok, Ok, Ok, Entire MMC will disappear.
Anybody seen this before? How do I fix this? This only happens on Windows
2003. I have never had this problem with Windows 2000.
| |
| Shane M Ryan 2004-09-22, 9:47 pm |
| I found that the utitlity doesn't update the SourceDef table in the commerce
database properly under Windows 2003. I am going to change it in the
database manually.
"Shane M Ryan" <shanemryanNOSPAM@hotmail.com> wrote in message
news:e4xjU5AnEHA.1304@TK2MSFTNGP09.phx.gbl...
> Commerce 2002sp3 on Windows 2003, can't change profiles data source.
> Steps to reproduce:
>
> 1) Backup commerce database on old platform.
>
> 2) Restore database to new platform using Windows 2003.
>
> 3) Go to "Global Resources", "Profiles", "Profile Catalog",
> "DataSources", "ProfileService_SQLsource"
>
> 4) Right click "ProfileService_SQLsource" choose properties.
>
> 5) Partitions.
>
> 6) Click under Name column "SQLSource"
>
> 7) Click "Edit", "Edit" put in new SQL Server name or IP address.
>
> 8) Click Ok, Ok, Ok, Ok, Entire MMC will disappear.
>
>
>
> Anybody seen this before? How do I fix this? This only happens on
> Windows 2003. I have never had this problem with Windows 2000.
>
>
>
>
>
>
|
|
|
|
|