The trials of relocating both the SQL and the CRM frontend server (1.2)

Just thought I'd share a few of my recent experiences with the group.

Past situation:
CRM 1.2 installed on a server with SQL on the same system. Running on W2k
server, in a native mode AD.

this was running reasonably, but the server was at the end of its service
contract and performance lagging, with the upcoming rollout of CRM for
support as well as sales the active user base was about to double so we
needed better performance.

The plan was to move the db's to a dedicated SQL server and shift the front
end to a new dual 2.8 xeon system (overkill but it does other roles too).

so the plan was to follow ms document ID 32398 (search on google against
this group - MS seem to have 'forgotten' this one). but install CRM frontend
onto the new system instead of the original.

the procedure was going well until step 6 - enabling replication on the
database. The ms doc doesn't state that you need single quotation marks
around the SQL server name, and even when those are in place the query
analyzer throws out a number of worrying messages (full text pasted at the
bottom under QARpt) the error message that worries me the most was this:

Server: Msg 20074, Level 16, State 1, Procedure sp_addmergearticle, Line 539
Only a table object can be published as a "table" article for merge
replication.

I know nothing of SQL, but to me that looks very wrong.

anyway we continued, no persevered. and tried the reinstallation of CRM (on
the new hardware) just after selecting the databases the following error
message appears:

Setup was unable to install Microsoft CRM Server.
Setup was unable to grant access to the Microsoft CRM databases.
 Unknown error. (80040E14)

Which is pretty unhelpful I think you'll agree. There is nothing out of the
ordinary with the event logs, and both systems were (at least at logon)
authenticating against the same DC so there shouldn't be any of the synch
issues I've seen mentioned in this group. We tried many different
combinations of the setup options with no joy and resorted to a call to ms
support. after taking an inordinately long time to open a call (one wonders
if they are using CRM ;) we discovered two things:

1) according to ms our crm license key is invalid. this is very odd as it
worked fine.
2) to reinstall crm a new license key is required, presumably the old one is
stored in the db and cannot be re-entered. it takes ms 48 hours to issue a
new key!

So I'm presently waiting for MS to issue the key. If anyone has any thoughts
on this, or just learns from my misfortune it'd be good to hear.

-Ben Fountain
Imscan Systems Limited


QARpt
New login created.
'distributor_admin' added to role 'sysadmin'.
The dependent aliases were mapped to the new database owner.
Database owner changed.
Creating table sysmergepublications
Creating table MSmerge_errorlineage
Creating table MSrepl_identity_range
Creating table sysmergearticles
Creating table sysmergeschemaarticles
Creating table sysmergesubscriptions
Creating table MSmerge_replinfo
Creating table MSmerge_tombstone
Creating table MSmerge_contents
Creating table MSmerge_genhistory
Creating table MSmerge_delete_conflicts
Creating table sysmergeschemachange
Creating table sysmergesubsetfilters
Creating table MSdynamicsnapshotviews
Creating table MSdynamicsnapshotjobs
Creating table MSmerge_altsyncpartners
Creating table sysmergepublications
Creating table MSmerge_errorlineage
Creating table MSrepl_identity_range
Creating table sysmergearticles
Creating table sysmergeschemaarticles
Creating table sysmergesubscriptions
Creating table MSmerge_replinfo
Creating table MSmerge_tombstone
Creating table MSmerge_contents
Creating table MSmerge_genhistory
Creating table MSmerge_delete_conflicts
Creating table sysmergeschemachange
Creating table sysmergesubsetfilters
Creating table MSdynamicsnapshotviews
Creating table MSdynamicsnapshotjobs
Creating table MSmerge_altsyncpartners
Warning: only Subscribers running SQL Server 7.0 Service Pack 2 or later can
synchronize with publication 'CRMPub-Imscan_MSCRM' because decentralized
conflict logging is designated.

Server: Msg 15024, Level 16, State 1, Procedure sp_grantdbaccess, Line 125
The group 'IMSCAN-DDC\SQLRepl {C9AFBE1E-67B2-4D9C-99C3-710AB8607B10}'
already exists in the current database.
Server: Msg 15024, Level 16, State 1, Procedure sp_grantdbaccess, Line 125
The group 'IMSCAN-DDC\SQLRepl {C9AFBE1E-67B2-4D9C-99C3-710AB8607B10}'
already exists in the current database.
New role added.
'Domain Admins' added to role 'MSmerge_C15D4F59965F4505B09147FA0BAD2AAA'.
'SQLRepl {C9AFBE1E-67B2-4D9C-99C3-710AB8607B10}' added to role
'MSmerge_C15D4F59965F4505B09147FA0BAD2AAA'.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Server: Msg 20074, Level 16, State 1, Procedure sp_addmergearticle, Line 539
Only a table object can be published as a "table" article for merge
replication.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMPub-Imscan_MSCRM' because it contains schema-only articles.
Warning: only Subscribers running SQL Server 7.0 Service Pack 2 or later can
synchronize with publication 'CRMMetaPub-Imscan_METABASE' because
decentralized conflict logging is designated.
New role added.
'Domain Admins' added to role 'MSmerge_76B5E99ADD6C4C8C9A9FB2DA9B5C37A8'.
'SQLRepl {C9AFBE1E-67B2-4D9C-99C3-710AB8607B10}' added to role
'MSmerge_76B5E99ADD6C4C8C9A9FB2DA9B5C37A8'.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because at least one timestamp
column exists in one of its articles..
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
articles.




0
BF
4/28/2004 12:04:44 PM
crm 35858 articles. 1 followers. Follow

3 Replies
558 Views

Similar Articles

[PageSpeed] 35

Hello

I did the same thing as you ie moved the CRM sql to a new box and reloaded
the web box.

It sounds as if your License name has some funny characters.

I too followed the article you specified however you should speak to your
CRM support person as it is possible to setup replication using the CRM
tools rather than running a script


"BF" <bf> wrote in message news:OxvI%23jRLEHA.3216@tk2msftngp13.phx.gbl...
> Just thought I'd share a few of my recent experiences with the group.
>
> Past situation:
> CRM 1.2 installed on a server with SQL on the same system. Running on W2k
> server, in a native mode AD.
>
> this was running reasonably, but the server was at the end of its service
> contract and performance lagging, with the upcoming rollout of CRM for
> support as well as sales the active user base was about to double so we
> needed better performance.
>
> The plan was to move the db's to a dedicated SQL server and shift the
front
> end to a new dual 2.8 xeon system (overkill but it does other roles too).
>
> so the plan was to follow ms document ID 32398 (search on google against
> this group - MS seem to have 'forgotten' this one). but install CRM
frontend
> onto the new system instead of the original.
>
> the procedure was going well until step 6 - enabling replication on the
> database. The ms doc doesn't state that you need single quotation marks
> around the SQL server name, and even when those are in place the query
> analyzer throws out a number of worrying messages (full text pasted at the
> bottom under QARpt) the error message that worries me the most was this:
>
> Server: Msg 20074, Level 16, State 1, Procedure sp_addmergearticle, Line
539
> Only a table object can be published as a "table" article for merge
> replication.
>
> I know nothing of SQL, but to me that looks very wrong.
>
> anyway we continued, no persevered. and tried the reinstallation of CRM
(on
> the new hardware) just after selecting the databases the following error
> message appears:
>
> Setup was unable to install Microsoft CRM Server.
> Setup was unable to grant access to the Microsoft CRM databases.
>  Unknown error. (80040E14)
>
> Which is pretty unhelpful I think you'll agree. There is nothing out of
the
> ordinary with the event logs, and both systems were (at least at logon)
> authenticating against the same DC so there shouldn't be any of the synch
> issues I've seen mentioned in this group. We tried many different
> combinations of the setup options with no joy and resorted to a call to ms
> support. after taking an inordinately long time to open a call (one
wonders
> if they are using CRM ;) we discovered two things:
>
> 1) according to ms our crm license key is invalid. this is very odd as it
> worked fine.
> 2) to reinstall crm a new license key is required, presumably the old one
is
> stored in the db and cannot be re-entered. it takes ms 48 hours to issue a
> new key!
>
> So I'm presently waiting for MS to issue the key. If anyone has any
thoughts
> on this, or just learns from my misfortune it'd be good to hear.
>
> -Ben Fountain
> Imscan Systems Limited
>
>
> QARpt
> New login created.
> 'distributor_admin' added to role 'sysadmin'.
> The dependent aliases were mapped to the new database owner.
> Database owner changed.
> Creating table sysmergepublications
> Creating table MSmerge_errorlineage
> Creating table MSrepl_identity_range
> Creating table sysmergearticles
> Creating table sysmergeschemaarticles
> Creating table sysmergesubscriptions
> Creating table MSmerge_replinfo
> Creating table MSmerge_tombstone
> Creating table MSmerge_contents
> Creating table MSmerge_genhistory
> Creating table MSmerge_delete_conflicts
> Creating table sysmergeschemachange
> Creating table sysmergesubsetfilters
> Creating table MSdynamicsnapshotviews
> Creating table MSdynamicsnapshotjobs
> Creating table MSmerge_altsyncpartners
> Creating table sysmergepublications
> Creating table MSmerge_errorlineage
> Creating table MSrepl_identity_range
> Creating table sysmergearticles
> Creating table sysmergeschemaarticles
> Creating table sysmergesubscriptions
> Creating table MSmerge_replinfo
> Creating table MSmerge_tombstone
> Creating table MSmerge_contents
> Creating table MSmerge_genhistory
> Creating table MSmerge_delete_conflicts
> Creating table sysmergeschemachange
> Creating table sysmergesubsetfilters
> Creating table MSdynamicsnapshotviews
> Creating table MSdynamicsnapshotjobs
> Creating table MSmerge_altsyncpartners
> Warning: only Subscribers running SQL Server 7.0 Service Pack 2 or later
can
> synchronize with publication 'CRMPub-Imscan_MSCRM' because decentralized
> conflict logging is designated.
>
> Server: Msg 15024, Level 16, State 1, Procedure sp_grantdbaccess, Line 125
> The group 'IMSCAN-DDC\SQLRepl {C9AFBE1E-67B2-4D9C-99C3-710AB8607B10}'
> already exists in the current database.
> Server: Msg 15024, Level 16, State 1, Procedure sp_grantdbaccess, Line 125
> The group 'IMSCAN-DDC\SQLRepl {C9AFBE1E-67B2-4D9C-99C3-710AB8607B10}'
> already exists in the current database.
> New role added.
> 'Domain Admins' added to role 'MSmerge_C15D4F59965F4505B09147FA0BAD2AAA'.
> 'SQLRepl {C9AFBE1E-67B2-4D9C-99C3-710AB8607B10}' added to role
> 'MSmerge_C15D4F59965F4505B09147FA0BAD2AAA'.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Server: Msg 20074, Level 16, State 1, Procedure sp_addmergearticle, Line
539
> Only a table object can be published as a "table" article for merge
> replication.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMPub-Imscan_MSCRM' because it contains schema-only
articles.
> Warning: only Subscribers running SQL Server 7.0 Service Pack 2 or later
can
> synchronize with publication 'CRMMetaPub-Imscan_METABASE' because
> decentralized conflict logging is designated.
> New role added.
> 'Domain Admins' added to role 'MSmerge_76B5E99ADD6C4C8C9A9FB2DA9B5C37A8'.
> 'SQLRepl {C9AFBE1E-67B2-4D9C-99C3-710AB8607B10}' added to role
> 'MSmerge_76B5E99ADD6C4C8C9A9FB2DA9B5C37A8'.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because at least one timestamp
> column exists in one of its articles..
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
> Warning: only Subscribers running SQL Server 2000 can synchronize with
> publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> articles.
>
>
>
>


0
John
4/28/2004 8:39:15 PM
The licensed name is simply 'Imscan' (without the quotes), can't really see
how that could be a problem. I'll see what MS support offers and post back
my results.

-Ben

"John O'Donnell" <csharpconsulting@nospam-hotmail.com-nospam> wrote in
message news:uG1fgDWLEHA.1156@TK2MSFTNGP09.phx.gbl...
> Hello
>
> I did the same thing as you ie moved the CRM sql to a new box and reloaded
> the web box.
>
> It sounds as if your License name has some funny characters.
>
> I too followed the article you specified however you should speak to your
> CRM support person as it is possible to setup replication using the CRM
> tools rather than running a script
>
>
> "BF" <bf> wrote in message news:OxvI%23jRLEHA.3216@tk2msftngp13.phx.gbl...
> > Just thought I'd share a few of my recent experiences with the group.
> >
> > Past situation:
> > CRM 1.2 installed on a server with SQL on the same system. Running on
W2k
> > server, in a native mode AD.
> >
> > this was running reasonably, but the server was at the end of its
service
> > contract and performance lagging, with the upcoming rollout of CRM for
> > support as well as sales the active user base was about to double so we
> > needed better performance.
> >
> > The plan was to move the db's to a dedicated SQL server and shift the
> front
> > end to a new dual 2.8 xeon system (overkill but it does other roles
too).
> >
> > so the plan was to follow ms document ID 32398 (search on google against
> > this group - MS seem to have 'forgotten' this one). but install CRM
> frontend
> > onto the new system instead of the original.
> >
> > the procedure was going well until step 6 - enabling replication on the
> > database. The ms doc doesn't state that you need single quotation marks
> > around the SQL server name, and even when those are in place the query
> > analyzer throws out a number of worrying messages (full text pasted at
the
> > bottom under QARpt) the error message that worries me the most was this:
> >
> > Server: Msg 20074, Level 16, State 1, Procedure sp_addmergearticle, Line
> 539
> > Only a table object can be published as a "table" article for merge
> > replication.
> >
> > I know nothing of SQL, but to me that looks very wrong.
> >
> > anyway we continued, no persevered. and tried the reinstallation of CRM
> (on
> > the new hardware) just after selecting the databases the following error
> > message appears:
> >
> > Setup was unable to install Microsoft CRM Server.
> > Setup was unable to grant access to the Microsoft CRM databases.
> >  Unknown error. (80040E14)
> >
> > Which is pretty unhelpful I think you'll agree. There is nothing out of
> the
> > ordinary with the event logs, and both systems were (at least at logon)
> > authenticating against the same DC so there shouldn't be any of the
synch
> > issues I've seen mentioned in this group. We tried many different
> > combinations of the setup options with no joy and resorted to a call to
ms
> > support. after taking an inordinately long time to open a call (one
> wonders
> > if they are using CRM ;) we discovered two things:
> >
> > 1) according to ms our crm license key is invalid. this is very odd as
it
> > worked fine.
> > 2) to reinstall crm a new license key is required, presumably the old
one
> is
> > stored in the db and cannot be re-entered. it takes ms 48 hours to issue
a
> > new key!
> >
> > So I'm presently waiting for MS to issue the key. If anyone has any
> thoughts
> > on this, or just learns from my misfortune it'd be good to hear.
> >
> > -Ben Fountain
> > Imscan Systems Limited
> >
> >
> > QARpt
> > New login created.
> > 'distributor_admin' added to role 'sysadmin'.
> > The dependent aliases were mapped to the new database owner.
> > Database owner changed.
> > Creating table sysmergepublications
> > Creating table MSmerge_errorlineage
> > Creating table MSrepl_identity_range
> > Creating table sysmergearticles
> > Creating table sysmergeschemaarticles
> > Creating table sysmergesubscriptions
> > Creating table MSmerge_replinfo
> > Creating table MSmerge_tombstone
> > Creating table MSmerge_contents
> > Creating table MSmerge_genhistory
> > Creating table MSmerge_delete_conflicts
> > Creating table sysmergeschemachange
> > Creating table sysmergesubsetfilters
> > Creating table MSdynamicsnapshotviews
> > Creating table MSdynamicsnapshotjobs
> > Creating table MSmerge_altsyncpartners
> > Creating table sysmergepublications
> > Creating table MSmerge_errorlineage
> > Creating table MSrepl_identity_range
> > Creating table sysmergearticles
> > Creating table sysmergeschemaarticles
> > Creating table sysmergesubscriptions
> > Creating table MSmerge_replinfo
> > Creating table MSmerge_tombstone
> > Creating table MSmerge_contents
> > Creating table MSmerge_genhistory
> > Creating table MSmerge_delete_conflicts
> > Creating table sysmergeschemachange
> > Creating table sysmergesubsetfilters
> > Creating table MSdynamicsnapshotviews
> > Creating table MSdynamicsnapshotjobs
> > Creating table MSmerge_altsyncpartners
> > Warning: only Subscribers running SQL Server 7.0 Service Pack 2 or later
> can
> > synchronize with publication 'CRMPub-Imscan_MSCRM' because decentralized
> > conflict logging is designated.
> >
> > Server: Msg 15024, Level 16, State 1, Procedure sp_grantdbaccess, Line
125
> > The group 'IMSCAN-DDC\SQLRepl {C9AFBE1E-67B2-4D9C-99C3-710AB8607B10}'
> > already exists in the current database.
> > Server: Msg 15024, Level 16, State 1, Procedure sp_grantdbaccess, Line
125
> > The group 'IMSCAN-DDC\SQLRepl {C9AFBE1E-67B2-4D9C-99C3-710AB8607B10}'
> > already exists in the current database.
> > New role added.
> > 'Domain Admins' added to role
'MSmerge_C15D4F59965F4505B09147FA0BAD2AAA'.
> > 'SQLRepl {C9AFBE1E-67B2-4D9C-99C3-710AB8607B10}' added to role
> > 'MSmerge_C15D4F59965F4505B09147FA0BAD2AAA'.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Server: Msg 20074, Level 16, State 1, Procedure sp_addmergearticle, Line
> 539
> > Only a table object can be published as a "table" article for merge
> > replication.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp column
> > exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMPub-Imscan_MSCRM' because it contains schema-only
> articles.
> > Warning: only Subscribers running SQL Server 7.0 Service Pack 2 or later
> can
> > synchronize with publication 'CRMMetaPub-Imscan_METABASE' because
> > decentralized conflict logging is designated.
> > New role added.
> > 'Domain Admins' added to role
'MSmerge_76B5E99ADD6C4C8C9A9FB2DA9B5C37A8'.
> > 'SQLRepl {C9AFBE1E-67B2-4D9C-99C3-710AB8607B10}' added to role
> > 'MSmerge_76B5E99ADD6C4C8C9A9FB2DA9B5C37A8'.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because at least one timestamp
> > column exists in one of its articles..
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > publication 'CRMMetaPub-Imscan_METABASE' because it contains schema-only
> > articles.
> >
> >
> >
> >
>
>


0
BF
4/29/2004 11:04:43 AM
Well, MS support has said a few things, mostly revolving around doing a
series of complete uninstalls and reinstalls, none of which have so far
worked.

One possible point raised was that our original CRM was us english v1, we
upgraded to (presumably) intl english 1.2, we aren't sure as 1.2 was
downloaded from the ms partner site directly.

That however shouldn't be an issue now as we are trying to create a new crm
instance on the systems without any previous databases. but that now isn't
working either, bombing out with the same error as before:

Setup was unable to install Microsoft CRM server.
Setup was unable to grant access to the Microsoft CRM databases.
Unknown error. (80040E14)

any thoughts from the group would be appreciated, been without CRM for a
week now. not helpful for the rollout!

cheers
-BF


"BF" <bf> wrote in message news:OC2SKndLEHA.2660@TK2MSFTNGP09.phx.gbl...
> The licensed name is simply 'Imscan' (without the quotes), can't really
see
> how that could be a problem. I'll see what MS support offers and post back
> my results.
>
> -Ben
>
> "John O'Donnell" <csharpconsulting@nospam-hotmail.com-nospam> wrote in
> message news:uG1fgDWLEHA.1156@TK2MSFTNGP09.phx.gbl...
> > Hello
> >
> > I did the same thing as you ie moved the CRM sql to a new box and
reloaded
> > the web box.
> >
> > It sounds as if your License name has some funny characters.
> >
> > I too followed the article you specified however you should speak to
your
> > CRM support person as it is possible to setup replication using the CRM
> > tools rather than running a script
> >
> >
> > "BF" <bf> wrote in message
news:OxvI%23jRLEHA.3216@tk2msftngp13.phx.gbl...
> > > Just thought I'd share a few of my recent experiences with the group.
> > >
> > > Past situation:
> > > CRM 1.2 installed on a server with SQL on the same system. Running on
> W2k
> > > server, in a native mode AD.
> > >
> > > this was running reasonably, but the server was at the end of its
> service
> > > contract and performance lagging, with the upcoming rollout of CRM for
> > > support as well as sales the active user base was about to double so
we
> > > needed better performance.
> > >
> > > The plan was to move the db's to a dedicated SQL server and shift the
> > front
> > > end to a new dual 2.8 xeon system (overkill but it does other roles
> too).
> > >
> > > so the plan was to follow ms document ID 32398 (search on google
against
> > > this group - MS seem to have 'forgotten' this one). but install CRM
> > frontend
> > > onto the new system instead of the original.
> > >
> > > the procedure was going well until step 6 - enabling replication on
the
> > > database. The ms doc doesn't state that you need single quotation
marks
> > > around the SQL server name, and even when those are in place the query
> > > analyzer throws out a number of worrying messages (full text pasted at
> the
> > > bottom under QARpt) the error message that worries me the most was
this:
> > >
> > > Server: Msg 20074, Level 16, State 1, Procedure sp_addmergearticle,
Line
> > 539
> > > Only a table object can be published as a "table" article for merge
> > > replication.
> > >
> > > I know nothing of SQL, but to me that looks very wrong.
> > >
> > > anyway we continued, no persevered. and tried the reinstallation of
CRM
> > (on
> > > the new hardware) just after selecting the databases the following
error
> > > message appears:
> > >
> > > Setup was unable to install Microsoft CRM Server.
> > > Setup was unable to grant access to the Microsoft CRM databases.
> > >  Unknown error. (80040E14)
> > >
> > > Which is pretty unhelpful I think you'll agree. There is nothing out
of
> > the
> > > ordinary with the event logs, and both systems were (at least at
logon)
> > > authenticating against the same DC so there shouldn't be any of the
> synch
> > > issues I've seen mentioned in this group. We tried many different
> > > combinations of the setup options with no joy and resorted to a call
to
> ms
> > > support. after taking an inordinately long time to open a call (one
> > wonders
> > > if they are using CRM ;) we discovered two things:
> > >
> > > 1) according to ms our crm license key is invalid. this is very odd as
> it
> > > worked fine.
> > > 2) to reinstall crm a new license key is required, presumably the old
> one
> > is
> > > stored in the db and cannot be re-entered. it takes ms 48 hours to
issue
> a
> > > new key!
> > >
> > > So I'm presently waiting for MS to issue the key. If anyone has any
> > thoughts
> > > on this, or just learns from my misfortune it'd be good to hear.
> > >
> > > -Ben Fountain
> > > Imscan Systems Limited
> > >
> > >
> > > QARpt
> > > New login created.
> > > 'distributor_admin' added to role 'sysadmin'.
> > > The dependent aliases were mapped to the new database owner.
> > > Database owner changed.
> > > Creating table sysmergepublications
> > > Creating table MSmerge_errorlineage
> > > Creating table MSrepl_identity_range
> > > Creating table sysmergearticles
> > > Creating table sysmergeschemaarticles
> > > Creating table sysmergesubscriptions
> > > Creating table MSmerge_replinfo
> > > Creating table MSmerge_tombstone
> > > Creating table MSmerge_contents
> > > Creating table MSmerge_genhistory
> > > Creating table MSmerge_delete_conflicts
> > > Creating table sysmergeschemachange
> > > Creating table sysmergesubsetfilters
> > > Creating table MSdynamicsnapshotviews
> > > Creating table MSdynamicsnapshotjobs
> > > Creating table MSmerge_altsyncpartners
> > > Creating table sysmergepublications
> > > Creating table MSmerge_errorlineage
> > > Creating table MSrepl_identity_range
> > > Creating table sysmergearticles
> > > Creating table sysmergeschemaarticles
> > > Creating table sysmergesubscriptions
> > > Creating table MSmerge_replinfo
> > > Creating table MSmerge_tombstone
> > > Creating table MSmerge_contents
> > > Creating table MSmerge_genhistory
> > > Creating table MSmerge_delete_conflicts
> > > Creating table sysmergeschemachange
> > > Creating table sysmergesubsetfilters
> > > Creating table MSdynamicsnapshotviews
> > > Creating table MSdynamicsnapshotjobs
> > > Creating table MSmerge_altsyncpartners
> > > Warning: only Subscribers running SQL Server 7.0 Service Pack 2 or
later
> > can
> > > synchronize with publication 'CRMPub-Imscan_MSCRM' because
decentralized
> > > conflict logging is designated.
> > >
> > > Server: Msg 15024, Level 16, State 1, Procedure sp_grantdbaccess, Line
> 125
> > > The group 'IMSCAN-DDC\SQLRepl {C9AFBE1E-67B2-4D9C-99C3-710AB8607B10}'
> > > already exists in the current database.
> > > Server: Msg 15024, Level 16, State 1, Procedure sp_grantdbaccess, Line
> 125
> > > The group 'IMSCAN-DDC\SQLRepl {C9AFBE1E-67B2-4D9C-99C3-710AB8607B10}'
> > > already exists in the current database.
> > > New role added.
> > > 'Domain Admins' added to role
> 'MSmerge_C15D4F59965F4505B09147FA0BAD2AAA'.
> > > 'SQLRepl {C9AFBE1E-67B2-4D9C-99C3-710AB8607B10}' added to role
> > > 'MSmerge_C15D4F59965F4505B09147FA0BAD2AAA'.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Server: Msg 20074, Level 16, State 1, Procedure sp_addmergearticle,
Line
> > 539
> > > Only a table object can be published as a "table" article for merge
> > > replication.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because at least one timestamp
column
> > > exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMPub-Imscan_MSCRM' because it contains schema-only
> > articles.
> > > Warning: only Subscribers running SQL Server 7.0 Service Pack 2 or
later
> > can
> > > synchronize with publication 'CRMMetaPub-Imscan_METABASE' because
> > > decentralized conflict logging is designated.
> > > New role added.
> > > 'Domain Admins' added to role
> 'MSmerge_76B5E99ADD6C4C8C9A9FB2DA9B5C37A8'.
> > > 'SQLRepl {C9AFBE1E-67B2-4D9C-99C3-710AB8607B10}' added to role
> > > 'MSmerge_76B5E99ADD6C4C8C9A9FB2DA9B5C37A8'.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because at least one
timestamp
> > > column exists in one of its articles..
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > > Warning: only Subscribers running SQL Server 2000 can synchronize with
> > > publication 'CRMMetaPub-Imscan_METABASE' because it contains
schema-only
> > > articles.
> > >
> > >
> > >
> > >
> >
> >
>
>


0
BF
5/6/2004 10:25:44 AM
Reply:

Similar Artilces:

sorry, I could not find any host named <domain name> (#5.1.2)
I upgraded to Windows 2003 and Exchange 2003 over the weekend. Now, I can not send email to yahoo accounts and when sending from yahoo back, I get the above message. I do not have a "smarthost" setup and am running DNS on the exchange as well. I went to www.dnsreport.com and it says all is fine. Any ideas with what is going on with my SMTP? Setting wrong? TIA, Darrin hi darrin! either check your DNS snapin, in the properties of your dns server if you have set dns forwarders. use at least one external dns, e.g. the dns of your isp. or you open the properties of you smtp vir...

RMS 2.0 Crashes when scanning item
My RMS2.0 Store Operations crashes on average once per day when I attempt to scan an item. I purchased it 3 months ago and it's been doing it since. I have to do a hard reboot to recover and upon restart, I get error message "cannot connect to database". I have to connect using administrator. I have 3 Giga byte of RAM. Occassionaly, I will open other applications as well (i.e. MS Access). Any help would be greatly appreciated. Dear Asmar, Frist of all go to Control Panel> Adminitration Tool >Event viewer and look the applicaiton Log try to see what error is co...

hello #2
...

Wait Cursor #2
Hi, I am having some problems with the Wait Cursor. I have an application with multiple screens sending requests and receiving responses from a hardware device. A Screen(suppose screen 1) that sends a request has to wait for a reply. Till then no activity is to be performed on that screen. However the user can operate with the other screens. So I put a Wait Cursor on screen 1. But now my entire application gets blocked and I cannot access any other view till the reply is received for Screen 1. How do I change the Cursor when I move from one screen to another. Also no event is fired when the W...

If Formula question #2
I'm trying to crossmatch 2 files... the first... a list of about 15 employee's who are being terminated (150 rows... 4 Columns: last name first name, dept., status). The second, a list of all employee's (approx. 600) that has about 2 columns of necessary information, including the column of informatio i'm trying to get for the first file. now... if the employee's name is on the first file... i need to be abl to pull the information that is in the cell of the "status" column o the second file. I've tried creating a column in each file with the concatenate ...

Lookup Function #2
I DON'T KNOW WHY SOMETIMES THE FUNCTION LOOKUP WORKS AND SOMETIMES NOT. DOES THE CELLS FORMAT MATTER? SOMEBODY CAN HELP ME. E-MAIL ME EDURROCHA@YAHOO.COM.BR i CAN SEND A EXEMPL -- erroch ----------------------------------------------------------------------- errocha's Profile: http://www.excelforum.com/member.php?action=getinfo&userid=1481 View this thread: http://www.excelforum.com/showthread.php?threadid=26449 Hi what is your exact formula? -- Regards Frank Kabel Frankfurt, Germany "errocha" <errocha.1dbti0@excelforum-nospam.com> schrieb im Newsbeitrag news...

Time difference #2
Hi, In Col. 'A' a time is enter through time(08,0,0) function and in Col. 'B' the current time through Now() function. How I can calculate the difference or the number of hours and minutes laps between two times. please help me to get the answer. thanks.. Hi use =B1-A1 and format as time or if the time can span midnight try =B1-A1+(B1<A1) -- Regards Frank Kabel Frankfurt, Germany ismail wrote: > Hi, > In Col. 'A' a time is enter through time(08,0,0) function and in Col. > 'B' the current time through Now() function. How I can calculate the &...

Deleting Macros #2
I had a document with no macro in it, which was fine. Then I created a macro, but later deleted it. But now, everytime I open the file it says that the workbook contains macros - enable/disable...... There are no macros in the workbook, so how can I get rid of the message at file open (without setting security level to low)? Thanks in advance. Glenn Hi Glenn you also have to remove the (empty) module in your workbook: - open the VBA editor (ALT+F11) - delete/remove the empty modules - close the editor, save your workbook and try again -- Regards Frank Kabel Frankfurt, Germany "G...

2 Differant Global address books
I have 1 forest with 2 child domains off the root. I would like users in domain A to see only users and groups from domain A in their global address book and users in domain B to see only users and groups from domain B in their Global address book. Does anyone have any suggestions or know of some referance material I can use to set this up?-- Mike C On Tue, 25 Oct 2005 04:31:04 -0700, Mike C <MikeC@discussions.microsoft.com> wrote: >I have 1 forest with 2 child domains off the root. >I would like users in domain A to see only users and groups from domain A in >their globa...

Reinstalling 1.2
With all the problems I have had with Crystal Reports and the 9.2.2 fiasco I want to just reinstall CRM1.2. Is it possible to reinstall 1.2 without losing all of the current data? I want to see if reinstalling the sorry @$$ sucker will resolve our Crystal Reports issues. There is no "repair" option that I can see. So it looks like an uninstall and reinstall. But I really do not want to lose our test data. Thanks Webster Carl, You can uninstall and then reinstall using the existing databases. the uninstall does not remove the DB's of the AD Org units, so they are stil...

Synching CRM Contacts into Outlook
We have a client that wants to download the CRM 1.2 contacts in Outlook 2003. The options is selected to synch in CRM SFO but does not happen. Is there anywhere else I should look? I know that there is a patch for CRM 1.0 but cannot find anything for 1.2 Thanks for any help John ...

Currency Problems
Hi All, I have a customer (UK) whose base currency is Euro. How do I set region = United Kingdom and currency = Euro at install. Secondly, Is the Punt still recognised? I thought Eire went to the Euro in 2002 and therefor the currency list at installation is wrong. Any thoughts Thanks Mike You should be able to select a base currency when you first install Microsoft CRM, which then becomes the 'default' currency for the installation of your Organisation, presumably this would be the Euro in your situation. Once this default currency for an Organisation has been chosen, i...

Monitoring Project Server with Nagios
Hi, does anybody offer scripts to monitor Project Server with Nagios like with SCOM? Thanks for any advice Adrian -- Adrian Miller ...

Importing from IMAP server ( non exchange )
I have to change our curent mail setup from a sendmail/imap on Linux to exchange I'm wondering about the following . 1) is there a tool/method to import users IMAP files 2) can I set exchange to recive user@x.x.x.x ( the exchange servers IP ) 3) set the exchange server to recive mail fro user@exchangeserver.domain.net ? ( it seems to give user unknow at he moment ) 4) froward all unfound user to our old mail server ? Chris 1. Not really. But is there any reason that you can't log in to the current IMAP server with Outlook and simply drag the items from the IMAP ...

Problem with SQL query
Hi, following SQL query results with Type Mismatch: strSqlU = "update t_upisnik set t_upisnik.bodova = SELECT sum(bodova)as suma from t_prijava where t_prijava.nepogoda = t_upisnik.nepogoda and t_prijava.kultura = t_upisnik.kultura " & _ " where t_upisnik.ID in (SELECT prijavnik from t_prijava)" Anyone have any ideas what I did wrong? 1) As written, it looks like you have 2 WHERE clauses, which I'm sure confuses Access. I suspect the first WHERE belongs with the subquery. Try specifying where that subquery starts & stops: strSqlU = &quo...

NETSCAPE 7.1
Hello! I have a problem for transfer mail from Netscape 7.1 to Outlook Express. Have you some solution? Thanks a lot. daniele <anonymous@discussions.microsoft.com> wrote: > Hello! > I have a problem for transfer mail from Netscape 7.1 to > Outlook Express. > Have you some solution? Ask in an Outlook Express newsgroup. -- Brian Tillman Smiths Aerospace 3290 Patterson Ave. SE, MS 1B3 Grand Rapids, MI 49512-1991 Brian.Tillman is the name, smiths-aerospace.com is the domain. I don't speak for Smiths, and Smiths doesn't speak for me. ...

Mailbox Report #2
I need to generate a report that will show me e-mail messages from and to a mailbox for a particular period of time. We are using Exchange 2003. Thanks On 22 Nov 2006 09:19:45 -0800, lajerowa@gmail.com wrote: >I need to generate a report that will show me e-mail messages from and >to a mailbox for a particular period of time. We are using Exchange >2003. >Thanks Enable Message tracking. ...

installing SQL 2008 express and database with my vb app
Hi I have built a application in vb.net pro 2008 that uses a SQL express database I have been able to create an installation application project that installs the application perfect, but I am having to manually setup SQL express and my database I have had a look on the web with no luck, but would like to be able to have my application instalation also install the SQL express product as well as my database Is this possible and where can I find a guide on how to do this ... Thanks <address_is@invalid.invalid> wrote in message news:515824539294325110.892775addre...

Sort data to show in a series 1,2,3
We have a large worksheet used by many users that may have various filters on various columns at any given time. Column A contains data 0 thru 8. I need code to add to a macro that will sort the worksheet by the VISIBLE data in Col A as follows: 0 must always be at the top, then the first visible row with a 1 would be next, then the first visible row with a 2, then the next row a 1, then a 2, etc...the remaining rows with 3-8 may just show in ascending order all 3's, all 4's etc...so that column A will look like 0,0,0,1,2,1,2,1,2,1,2,3,3,3,3,4,4,4,....etc This would be a...

Taking out an Exchange 2003 Server from a site
I want to remove an old exchange 2003 from my site. How does one go about doing this? I did the following so far: Installed Exchange 2003 on new hardware and join it to my exchange site. I followed Tech Net Article 822931. Do I need to do anything else in order to get the old server out of my site cleanly. -- Eric Sabo NT Administrator Hi Eric, Following the steps in that article should do it for you. To be 100% sure, you can stop and disable the services on the server you wish to decommission for a few days and see if any problems arise. Good luck! -- Randy Campbell Microsof...

row and column headings #2
I have inherited a worksheet/application made in Excel 97. The person who created this has done some interesting trick to the worksheet so that none of the worksheets in the workbook show any of the column and rwo headings. How was this done I can not find the code that causes this? I need to edit a piece of the formula but I can not find my way around the worksheet because the heading do not show. -- rdrunner ------------------------------------------------------------------------ rdrunner's Profile: http://www.excelforum.com/member.php?action=getinfo&userid=28313 View this thre...

Outllook 2002 and Windows XP #2
I have four different user accounts but one shared email account for the four users. How do you set up the individual accounts to have access to the same Outlook 2002? Depending on who opens Outlook and does and send/receive, that account user only has access to those messages in the inbox. How do you make a common inbox for all users? Thanks Click Newsgroups on the Outlook Express toolbar, type Outlook into the search box and press enter, then scroll the Outlook groups, probably Outlook and/or Outlook General, for the most appropriate group and try your question there. -- Michael ...

503 This mail server requires authentication?
Another weird NDR was brought to my attention this morning. This only happens when sending to a particular external domain. The following NDR is immediately returned when trying to send: The following recipient(s) could not be reached: user@external.com on 7/8/05 7:45 AM There was a SMTP communication problem with the recipient's email server. Please contact your system administrator. <mybridghead.domain.com #5.5.0 smtp;503 This mail server requires authentication. Please check your mail client settings.> Message tracking shows: Message Submitted to Advanced Queuing Start...

Excel 2002 on a Terminal Server 2003
My users have an issue in Microsoft Excel 2002 while connected to a Terminal Server 2003. About 80% of the time when they copy and paste in a spreadsheet they get a message "cannot empty the clipboard" I have tried everything and looked everywhere, but cannot find a fix. I found a hotfix from Microsoft w/ the exact same symptoms but it only applies to Office 2003, therefore the Microsoft techs DO NOT recommend this. The article is http://support.microsoft.com/default.aspx?scid=kb;en- us;840872. Any help would be extremely appreciated. Hi in the Terminal Server Configura...

importing saved messages from 2 accounts in outlook express
I just installed Outlook today and am having some trouble importing saved messages and folders. I currently use 2 seperate email accounts in outlook express (both w/ comcast) and have save folders and messages in each one. Outlook Express made it so easy, just switch identies. The problem I'm having is that Outlook is only importing folders/messages from 1 of the 2 accounts, the main account. I have set up both accounts in outlook exactly as they were in outlook express. I have switched the default user in outlook and tried importing again....same outcome...it reimports the same...