Sage CRM

 View Only
Expand all | Collapse all

I just upgraded a client from EES 1.4 to MAS 200 S

Wayne Schulz

Wayne Schulz12-20-2011 14:00

  • 1.  I just upgraded a client from EES 1.4 to MAS 200 S

    Posted 12-20-2011 13:47
    I just upgraded a client from EES 1.4 to MAS 200 SQL with CRM version 7.1 in a cloud environment. Everything has gone fairly well except for the integration portion. I keep getting the error"" could not connect to the integration engine. error # 2: end-of-file on read or file full on write. I have followed sage advice to create an inbound rule for the integration service as well as modify the firewall and still no luck. CRM and MAS are on different servers, and it appears the service is running and the server name in CRM options is correct. Any other ideas?


  • 2.  RE: I just upgraded a client from EES 1.4 to MAS 200 S

    Posted 12-20-2011 14:00
    @PeterWolf is our resident SageCRM wiseguy


  • 3.  RE: I just upgraded a client from EES 1.4 to MAS 200 S

    Posted 12-20-2011 20:30
    Hi @JenniferChriston! I would want to have one of my engineers look into this if you are still having problems. I'm at a skeleton crew right now with the holidays - how urgent is it? Hopefully you are doing a test upgrade and not a live upgrade? Either way, can you email me details at pwolf@azamba.com if you are still looking for help? Did Sage advise you / did you install the MAS workstation piece on the CRM server? If so, does the CRM server connect to MAS ok?


  • 4.  RE: I just upgraded a client from EES 1.4 to MAS 200 S

    Posted 12-21-2011 07:34
    HI @PeterWolf , luckily this is only a test upgrade on a test server so it's not really urgent. Sage did not advise me to put a MAS workstation piece on the CRM server. I am working now again with the client's IT person to see if we need more security tweakings. I will let you know if that doesn't work....I appreciate the help.


  • 5.  RE: I just upgraded a client from EES 1.4 to MAS 200 S

    Posted 12-21-2011 09:12
    That's good news! Did you check to make sure the Integration piece is running? I'm travelling today for vacation but will check in tomorrow.


  • 6.  RE: I just upgraded a client from EES 1.4 to MAS 200 S

    Posted 01-19-2012 15:36
    @PeterWolf - Just wanted to update you on how I was able to fix this issue. It turns out we just need to make sure port 1433 was not blocked on the CRM server. I was spending all my time looking at their firewall and the integration server, I hadn't checked ports on the CRM server (SQL Server).


  • 7.  RE: I just upgraded a client from EES 1.4 to MAS 200 S

    Posted 01-19-2012 15:39
    Thanks Jennifer. Is that a MAS-CRM integration requirement? Or was it a client specific security configuration matter? I wasn't aware of a requirement to open that port (in all fairness, it may be a requirement but my technical skills are rusty - that's why I have a team to handle those things!).


  • 8.  RE: I just upgraded a client from EES 1.4 to MAS 200 S

    Posted 01-19-2012 15:42
    I have never had to do that before, but this was the first time we had a client that had a separate server for both MAS and CRM. I actually found that on a Microsoft knowledgebase article.


  • 9.  RE: I just upgraded a client from EES 1.4 to MAS 200 S

    Posted 01-19-2012 16:17
    I've asked my team - I will provide an update if anyone has any more information to add. Seems strange to me. Maybe it's a MS SQL thing?


  • 10.  RE: I just upgraded a client from EES 1.4 to MAS 200 S

    Posted 01-19-2012 16:29
    @JenniferChriston , are you saying that SQL Server is not on the same virtual server as CRM?


  • 11.  RE: I just upgraded a client from EES 1.4 to MAS 200 S

    Posted 01-19-2012 16:33
    Actually, after making sure I read everything, it does make sense, because the integration engine on the MAS server makes calls to SQL Server directly, not to CRM code. Note that the CRM setup in MAS asks for the SQL Server login info, not CRM login info.


  • 12.  RE: I just upgraded a client from EES 1.4 to MAS 200 S

    Posted 01-20-2012 05:46
    Yes ... port 1433 is the defaul port for MS SQL so if your firewalls are set to block it, there will be issues with connectivity from other servers. I guess this is why Sage is requires MS SQL certifications (I think)?


  • 13.  RE: I just upgraded a client from EES 1.4 to MAS 200 S

    Posted 01-20-2012 13:12
    Well good to know - I just did the MAS 500 SQL certification, I guess I will need to see if there is one for MAS 200/CRM