Pages

Search

Microsoft CRM - CRM cannot run

Microsoft CRM - CRM cannot run

CRM cannot run

Posted: 06 May 2004 12:50 PM PDT

Do you have SQL running on the same machine?

-Gary

<microsoft.com> wrote in message
news:97ad01c433aa$77a81ea0$gbl... 

Can CRM do this?

Posted: 06 May 2004 06:39 AM PDT

This is expected in v2, due out mid next year.

Gill 
news:<OzR6V$phx.gbl>... 
the following, we are 
our sales, invoices, 
would be great. The big 
customers. We support both 
completely list of all 
the system, this way 
the item, also and 
to each item and link 
coming year 
where it is possible to 
an amounut?? 
contract 
probably use 
is a 
would either 
information about each 
each serial 

Overdue activities

Posted: 06 May 2004 06:27 AM PDT

Hi Jan,

In the home page you see a list of all of your past due
activities as well as what is due today and tomorrow.

Hope this helps
Sam

 

Customising forms.

Posted: 06 May 2004 05:53 AM PDT

This will still not let you modify activity forms such as phone calls. This
feature is expected in the version 2 release


"Vinícius Pitta Lima de Araújo" <com.br> wrote in message
news:922c01c4337a$b71b68b0$gbl...
Off course who you want. Go to start/settings/costumize
system. I am using the portuguese version, so I dont know
if that is the correct way to acess this feature in
english version.

[]'s
Vinícius Pitta Lima de Araújo 

html emails

Posted: 06 May 2004 03:55 AM PDT

Your English is fine. Thanks for the information!
 

Migrate from ACT to MSCRM

Posted: 06 May 2004 03:12 AM PDT

We have people using our Export Pro tool for ACT! to MS Access, and then
using the CDF from that point.

http://www.nwoods.com/act/exportpro.htm

Jake
Northwoods Software


"Dirk" <microsoft.com> wrote in message
news:916501c43352$aa9e6a60$gbl... 

Rename Opportunites

Posted: 05 May 2004 03:31 PM PDT

I have not heard of anything but submitted a request to Microsoft for a
future version of CRM. Ideally I would like to go to an admin page which
lists all the terminology for CRM such as Accounts and be able to change
them to what I want such as Accounts becomes Customers etc.

A number of people have talked about possibly changing all the web source
code for these changes but it seems a long task for such a small thing.


"Steffen Klipfel" <spam> wrote in message
news:%phx.gbl... 

ASP.NET page to access CRM store

Posted: 05 May 2004 11:47 AM PDT

Update -

I set the process for the application to run under the
ExchangeCRMAppPool process and it fixed the problem. Heads up to
anyone running .aspx files to CRM.

Thanks
Josh


us (jkandiko) wrote in message news:<google.com>... 

Find Lead by Company Name

Posted: 05 May 2004 10:56 AM PDT

We customized the preview pane to add the company name. 
message 

Action Pack CRM License Structure?

Posted: 05 May 2004 10:43 AM PDT

Where did you order it from?


Ryan

"EdH" <com> wrote in message
news:phx.gbl... 
licenses, 

Leads List Nightmare :(

Posted: 05 May 2004 09:18 AM PDT

Well if your getting 10000 leads you can hire someone to do it for you :-)

If this is a regular occurence you may want to write a utility to do it.


"Todd M. Taylor" <com> wrote in message
news:O2G$phx.gbl... 
aren't 
there 
processing 

Faxing from CRM

Posted: 05 May 2004 08:56 AM PDT


"Jeff" <com> wrote in message
news:8d2d01c432b9$7c27d3e0$gbl... 

GFI Faxmaker

www.gfi.com

Hyperlinks to KB articles

Posted: 05 May 2004 08:07 AM PDT

Here's a not so graceful way to do this, but it works

1. Open the KB article that you want to link to in your new article
2. Press CTRL + N to open the article in a new browser window
3. Copy the URL from the address bar

From here, you would think you can just paste the URL into the new KB article, but in my tests of this, CRM dropped the last close bracket } from the hyperlink. So..

4. Paste the hyperlink in Word. You may have to re-type the close bracket } to get Word to add it to the hyperlink
5. Copy the link from Word and now you can paste it into your new KB article and it should work.

CRM Grids with no check boxes

Posted: 05 May 2004 07:55 AM PDT

CRM 1.2, Thanks 
selected byt using the 
The 
help. 

If Microsoft is listening, CRM wish list

Posted: 05 May 2004 06:51 AM PDT

perhaps even run it on Linux as well eh gary :-)


"Gary" <NOSPAM.com> wrote in message
news:phx.gbl... 

Athlon64/Opteron and CRM 1.2?

Posted: 05 May 2004 06:16 AM PDT

Thanks a bunch.

-- Steve


On Wed, 05 May 2004 16:17:01 GMT, Matthew <com> wrote:
 



--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

TK Articles (for CRM) - how to obtain

Posted: 05 May 2004 05:31 AM PDT

Thanks John


"John O'Donnell" <com-nospam> wrote in
message news:phx.gbl... 
the 
point 
to 

No APS running at port 6400

Posted: 05 May 2004 04:45 AM PDT

Hi John,

thanks for asking:
 

Yes, only Crystal APS and WinHTTP Web-Proxy Auto-Discovery service do not
start.
 

Yes, I rebooted. No, it never worked. It is a fresh install. MBS CRM was
never installed on this server or in this network before.
 

No.

Thanks for our help.
Eike


"John O'Donnell" <com-nospam> wrote in
message news:euQ#phx.gbl... 

crm email router worries

Posted: 05 May 2004 04:36 AM PDT

Hi Mike!!


I don't think so. Mine is very stable and has been stable
for the last five weeks. Ok, its not on the Exchange
machine but it works seamlessly with our Exchange server
Maybe install it on a back-up machine first then do a
live installation.

I haven't seen anything in the newsgroups about any
issues. But, as I said, mine is stable.

Good luck

Jan

-----Original Message----- 
software on our 
concerned about?! 

is "topic" important?

Posted: 05 May 2004 02:48 AM PDT

It's important in the reports too...

ip problems

Posted: 05 May 2004 02:12 AM PDT

Hi John,
Here are my replies:

Does the server appear to be running normally?
Yes, the system runs 100% fine if accessed via IE on the server.

do you see errors in the event logs on the server?
"The browser service has failed to retrieve the backup list too many times
on transport \Device\NetBT_Tcpip_{E7B4818E-3936-4928-9966-D2D03E2D36A2}.
The backup browser is stopping."

are call crm services started on the server? Yes. The security service
fails to start sometimes, but once started the system runs.

is the machine you are trying to connect from on the same network segment
and in the same domain? Yes

is the machine runninf internet explorer? Yes

can the client machine ping the server? No, it times out when I use the
server name. And it displays the wrong IP address. However, I can reach it
by typing the correct IP address. This leads me to believe it's some kind
of DNS problem? Typing the correct IP into a browser on the client prompts
for network password, but fails to connect.

Thanks for your help with this!
Mike

Help, can't access the Web administrator

Posted: 04 May 2004 11:41 PM PDT

Hi Sveta,

Try this because I had a similar problem. I could access
CRM(I have admin rights) but my colleague couldn't. Look
on your server and associate your server's IP_Address
with the default website, admin website as well as the
CRM website in IIS. That sorted us out.

Hope this helps,

Jan
 
has all roles) and licences assigned. Can not look futher
now because no one can access the administrator. Can't
access from server or clients using the servername. 

CRM Telemarketing Management

Posted: 04 May 2004 09:51 PM PDT

Phillip,
we're a German MBS Partner and developing that kind of solution.
Steffen
"Phillip Austin" <microsoft.com> schrieb im
Newsbeitrag news:com... 
for telemarketing purposes? I would like to implement rules such as
frequency that different types of leads are contacted and make it easy for
my staff to see who should be called when. 
management calls and visits. Ideally these would trigger on recent activity
and/or time sine last call. 

Delete Users!?!

Posted: 04 May 2004 08:54 PM PDT

David

just so you know Microsoft CRM discourages you from deleting anything. One
reason is to maintain the integrity of the database. Throughout CRM you will
see that instead of deleting items you will instead de-activate them. Of
course the plus side is you never lose data.

With users you should assign their records to another user then remove their
license and disable them.

You should also be aware that if someone leaves your company you should
disable them in CRM ie transfer their data and remove their license etc
before removing them from the active directory. If you remove them from the
AD first you will not be able to remove their license in CRM




"David Michaud" <microsoft.com> wrote in message
news:87d001c43254$9dd83350$gbl... 

SQL Server and CRM - Disaster Recovery (Continued)

Posted: 04 May 2004 07:49 PM PDT

here they are
========
TechKnowledge
How to move Microsoft CRM data from one Microsoft SQL Server to a
different computer


Return to previous page

Document ID: 32398
Date Created: 8/11/2003
Date Last Modified: 2/11/2004
Language: English - United States
Country: USA
Product: Microsoft CRM
Versions: 1.0
Modules: Microsoft CRM Installation, Microsoft CRM Miscellaneous,
Microsoft CRM Server Administration

SUMMARY

This article describes how to move the Microsoft CRM SQL Server
databases to a different computer in the same domain.

MORE INFORMATION

Note This process is intended for use in a scenario where a user is
required to move the Microsoft CRM SQL Server databases to a different new
server in the same domain. This process must not be used to move data from
one server to another across domains. It must not be used to move from a
named instance of Microsoft SQL server to a default instance on the same
server.
IMPORTANT Read and understand the whole article before you try to
complete this process.

Make sure you verify these prerequisites have been met:

1. Have all users log out of Microsoft CRM.

2. Make sure that all Microsoft CRM Sales for Outlook Clients have
synchronized all their offline data to Microsoft CRM by going on-line.
Remove all Microsoft CRM Sales for Outlook clients in the deployment.

3. This process must be performed by the same domain administrator
account that installed Microsoft CRM.

4. Make sure you make a copy of all reports you have customized or
modified because these reports must be republished.

5. Make sure that you have a current backup of your Active Directory
system state and all the Microsoft SQL Server databases.

Move the databases

1. Make a Microsoft SQL Server backup of each of the three primary
Microsoft CRM databases. You do not have to back up the MSCRMDistribution
Database. This will be re-created on your new Microsoft SQL server manually.
The three databases are as follows:

- <OrganizationName>_CRMCRYSTAL
- <OrganizationName >_METABASE
- <OrganizationName >_MSCRM

To complete these backups:

a. Click Start, point to Programs, and then point to Microsoft
SQL Server to open Enterprise Manager.

b. Expand your Server until you see the databases.

c. Right-click your database and select: All Tasks | Backup
Database.

d. Leave the backup type set to "Database - complete".

e. In the destination field, click Add.

f. In the Select Backup Destination window, click the ellipsis
box. (...)

g. In the Backup Device Location window, set a file name and
location for the backup file, and then click OK.

h. Click OK until all windows are closed and you receive a
message that the backup has completed successfully.

i. Repeat steps A-H for all three databases you are backing up.

j. Do NOT delete anything from this Microsoft SQL Server at this
time, because you need the original setup for reference during this process.

2. Transfer the backup files made in step 1 to your new Microsoft SQL
Server.

3. After you transfer the backup files, create the three new
databases that you will restore the backups into. To do so, follow these
steps:

a. Open Microsoft SQL Server Enterprise Manager.

b. Expand your server until you have opened the Databases folder.

c. Right-click the Databases folder, and then select New
Database.

d. Enter a name for your database, <OrganizationName>_CRMCRYSTAL.
It is very important to make sure the naming syntax used is exactly as it
appears on your original SQL Server.

e. Repeat steps C and D two more times, creating your
<OrganizationName>_METABASE and <OrganizationName>_MSCRM databases. Again,
make sure the naming syntax exactly matches the databases on your original
SQL Server.

4. After the databases have been created, the backup files must be
restored.

a. Open Microsoft SQL Server Enterprise Manager.

b. Expand your server until you have opened the Databases folder.

c. Right-click your _Crystal database.

d. Select All Tasks | Restore Database.

e. In the Restore Database window, select to restore from Device.

f. Click Select Devices.

g. In the Choose Restore Devices window, click Add.

h. In the Choose Restore Destination window, click the ellipsis
box (...).

i. Select the location for the backup file for the _Crystal
database, and then click OK.

j. Click OK in the Choose Restore Devices window.

k. In the Restore Database window, click the Options Tab.

l. In the Options tab, select Force Restore over Existing
Database.

m. In the Restore Database File As: section of the window you
will see two paths for the physical database files. Make sure these paths
are valid locations. If they are not, you must modify them.

n. Click OK in the Restore Database window to start the restore
process. Depending on the size of your database, this may take some time.
When it is complete, you will receive a message that the restore completed
successfully.

o. Repeat these steps for your <OrganizationName>_METABASE and
<OrganizationName>_MSCRM databases.

5. After you successfully restore the databases, you must set up the
security groups by mapping to the NT security groups.

Note For this step, it is good to view the security folder on the
original Microsoft SQL Server for reference.

a. Open Microsoft SQL Server Enterprise Manager.

b. Expand your server until you have opened the Security folder.

c. Right-click Logins, and then select New Login.

d. In SQL Server Login Properties - New Login. leave the
authentication set to Windows Authentication.

e. In the Domain field, select your domain.

f. In the Name field, you will see <Yourdomain>\.

g. Click the ellipsis box for the Name field, and then you will
see a list of your domain users and groups.

h. Find the SQLRepl group, select it, and then click OK.

i. Click OK to close all the Property windows. When you close
the last window, you may be prompted with the following message that you can
ignore and Close:

It has been detected that this login has permissions in the specific
database(s) - the login will have access to these database now.

j. Repeat steps C through I and select the SQLAccessGroup in step
H.

6. After the security groups have been set, the new system must be
prepared for replication.

Replication is the process that the Microsoft CRM Sales for Outlook
clients will use to go offline. Do not skip this step, even if you do not
currently use Microsoft CRM Sales for Outlook.

a. Open Microsoft SQL Server Enterprise Manager.

b. Open the Management folder in Enterprise Manager.

c. Make sure that the Microsoft SQL Server Agent is running. If
it is not running, right-click and select Start.

d. Click Start, point to Programs, point to Microsoft SQL Server,
and then click Query Analyzer.

e. In the Connect to SQL Server dialog box, connect to your
Microsoft SQL Server. Make sure to log in as a Microsoft SQL Server Admin
user.

f. From the toolbar drop-down list, select the database
<OrganizationName>_MSCRM.

g. Run the following command:

EXEC p_CRMReplicationSetup <SQL Server name>, <SQL Server name>,
<'Microsoft CRM database name'>, <'Metabase database name'>, <'replication
SQL Server directory'>, <'SQL login group name'>, <'MSCRMDistribution
database name'>

Where:

<Microsoft CRM_Database name> = This is the database that has a
name in the format <OrganizationName>_MSCRM.

<Metabase database name> = This is the database that has a name in
the format <OrganizationName>_METABASE.

<replication SQL Server directory> = This is the path to the
REPLDATA directory on the Microsoft SQL Server, for example: C:\Program
Files\Microsoft SQL Server\MSSQL\REPLDATA.

<SQL login group name> = This is the name located in the Logins
node under Security. It is in the format <domainname>\SQLRepl
{E5334FB9-440A-4BD8-A19A-0FA54E6B248C}. For more information about how to
find this name, see the following Note.

<MSCRMDistribution database name> = This is the database that has
a name in the format <OrganizationName>_MSCRMDistribution. If you do not
see this database in Microsoft SQL Server, specify the database name as
listed in the parameter, and then the database will be created.

Note To find the SQL login group name follow these steps:

a. Click Start, point to Programs, point to Microsoft SQL Server, and
click Enterprise Manager.

b. In the console tree, expand the Security node of the server
for which you want to determine the group name (the one you specified during
setup).

c. Click Logins to view a list of login names.

d. In the details pane, right-click the login name that is in the
format <domain name>\SQLRepl {E5334FB9-440A-4BD8-A19A-0FA54E6B248C}, and
then click Properties.

e. In the Properties dialog box, click the Database Access tab.

f. On the Database Access tab, the SQL login group name is the
name located in the User column for one of the populated rows. (Any one of
the names listed in this column will work.)

g. Right-click the name and then click Copy. Paste the name from
the User column into the <SQL login group name) parameter in the command
listed.

Example:

For an organization created with the name MyOrganization, with users
in the domain MyDomain, installed to a Microsoft SQL Server called MySQLSvr,
use code that is similar to the following:

EXEC p_CRMReplicationSetup MySQLSvr, MySQLSvr, 'MyOrganization_MSCRM',
'MyOrganization_METABASE', 'C:\Program Files\Microsoft SQL
Server\MSSQL\REPLDATA', 'MyDomain\SQLRepl
{E5334FB9-440A-4BD8-A19A-0FA54E6B248C}', 'MyOrganization_MSCRMDistribution'

7. After the replication is enabled, the MSCRM folder must be shared.

a. Open Windows Explorer on the new CRM server.

b. Locate the \Program Files\Microsoft SQL
Server\MSSQL\REPLDATA\MSCRM folder.

c. Right-click the MSCRM folder and select Sharing.

d. Share the folder with the name MSCRMSnapshotShare. Make sure
to match the syntax exactly.

e. For the share permissions, share the folder to the Everyone
group with full control.

f. For the NTFS file system permissions, give the domain users
group access with Read and Execute rights to the folder and sub-folders.

8. After the folder is shared, you must re-configure the Microsoft
CRM server and the Microsoft Sales for Outlook clients.

a. Remove all Microsoft CRM Sales for Outlook clients.

b. On the Microsoft CRM server, export your customizations using
Deployment Manager and then remove the Microsoft CRM server through
Add/Remove Programs.

c. After CRM has been removed from the system, restart the
server. After the CRM server has been re-started, delete the Microsoft CRM
folder in the Program Files folder.

d. Re-install the Microsoft CRM server. When you are prompted
during install, select to connect to existing databases and select the
location of the new Microsoft SQL server.

e. After installing, import and publish your customizations using
the Deployment Manager.

f. Re-install all Microsoft CRM Sales for Outlook clients.

9. Test the Microsoft CRM program and make sure that you can access
your data. Also test your Microsoft CRM Sales for Outlook clients to make
sure you can use the program.

10. At this point, you will not have access to the reports in
Microsoft CRM and the reports must be re-published. This task requires a
tool from Microsoft CRM Technical Support who can be reached at
1-888-477-7877 or https://mbs.microsoft.com/support/newstart.aspx.

11. After you have tested the Microsoft CRM Sales for Outlook clients
and confirm that the Web application functionality is working, you can clean
up your old Microsoft SQL server. To do so, follow these steps:

a. Open Microsoft SQL Server Enterprise Manager.

b. Expand your server until you see the Replication folder.

c. Right-click the Replication folder and select Disable
Publishing.

d. A Wizard will appear.

e. Click Yes to disable publishing, and then complete the Wizard
steps. This process can take several minutes or more.

f. After replication is disabled, you can delete the Microsoft
CRM databases.

After you have successfully completed the process of moving your
Microsoft CRM SQL databases from one server to another, remember to schedule
regular backups of the database on the new server.


================================
TechKnowledge
SQLAccessGroup and SQLRepl Groups do Not Exist in Microsoft SQL Server
Enterprise Manager for Microsoft CRM Deployment


Return to previous page

Document ID: 31478
Date Created: 6/18/2003
Date Last Modified: 7/16/2003
Language: English - United States
Country: USA
Product: Microsoft CRM
Versions: 1.0
Modules: Microsoft CRM Setup

Issue

How to add the SQLAccessGroup and SQLRepl group into Enterprise
Manager Logins area in order for Replication for Microsoft CRM to be set up
correctly?

Resolution

If the SQLAccessGroup and SQLRepl access groups do not exist within
the Logins area of Enterprise Manager, then Replication for Microsoft CRM
cannot be setup correctly.

If these access groups do not exist, the sp_grantlogin stored
procedure can add them into the Logins area.

1. Open Microsoft SQL Query Analyzer.

2. Type the following in a new query:
EXEC sp_grantlogin 'domain\group'

Note - In the above example, replace domain with the name of your
domain. And replace group with the full pre-windows 2000 group name for
SQLAccessGroup. The full name can be found in Active Directory Users and
Computers. Highlight the Microsoft CRM Organization Name and the
SQLAccessGroup will be listed. Highlight the group, right-click and choose
Properties. The full name will be listed in the Group Name field, it will
include SQLAccessGroup followed by a long GUID. Copy the contents of that
field and use it to replace 'group' in the script above.

3. Run the script against the master database.

4. Repeat steps 2 and 3 for the SQLRepl access group.

5. In Enterprise Manager, navigate to Security | Logins. Verify that
the SQLAccessGroup and SQLRepl access groups have been added.

6. In the Logins area, highlight SQLAccessGroup, right-click and
choose Properties.

7. Click on the Database Access tab and check the box next to the
MSCRM, METABASE and Crystal databases.

8. For the Crystal database, grant Public and dbo access.

9. For MSCRM and METABASE, grant Public access and then click OK.

10. Now highlight SQLRepl user, right-click and choose Properties.

11. Click on the Database Access tab and check the boxes next to MSCRM
and METABASE.

12. Grant Public access to both MSCRM and METABASE and click OK.

The access groups will now exist with the proper access. For more
information about the sp_grantlogin stored procedure, refer to SQL Books
Online and complete a search for sp_grantlogin.


===========================


"Chris Ericoli" <com.au> wrote in message
news:tpgi.com.au... 
the 
not 
message 
unsure 
Please