Hi everyone,

We have been running SLX 7.2.2 on Citrix metaframe presentation server 4.0, windows 2003 x32, the server has been on its last leg for a while and I’m planning to upgrade both hardware and software in next few weeks. 

According to SLX compatibility guide latest supported version of citrix is 4.0 even though it is 5 years old, there is also no say about 64 bit host OS for the citrix.

Has anyone been able to run 7.2.2 on XenApp on 64bit windows OS ?

Thank you,

Alex

Hi,

I am guessing you are looking at putting 7.2 on 2008 Server R2?  If so, yes, it is not supported by Sage. However, we are working on that now. We have it working for the most part on XenApp 6 as a published application.  Issues we have had:

1. Outlook was having problems working with SLX.  We had XP SP3 compatibility turned on in Citrix. Turned off all compatibility, and it resolved this issue.

2. Can't get the SLX address book to show up in Outlook in XenApp even though we registered the slxab32.dll as the user, as an admin, and manually. That was supposed to fix it, but it didn't. Minor issue for us. Probably will live with it.

3. The Opportunity Snapshot in 7.2 is actually an embedded browser. We can't get any of the pop-up controls to work in this snapshot window. Every other pop-up on the system works fine.  If we open SLX in a XenApp desktop, the controls work fine. Then after that, they continue to work fine in the published SLX application for that user for ever more. Have been bouncing around the edges of this one, but it is a Citrix issue that we can't quite nail down. There is a post on the Citrix boards that describe this behaviour, but our Citrix admin says our issue is slightly different. 

There is more on this here: (if this forum allows the URL to be posted!): http://crm.ittoolbox.com/groups/technical-functional/saleslogix-l/citrix-xenapp-fun-opportunity-snapshot-controls-do-not-respond-3989851

and here:  http://community.sagesaleslogix.com/t5/Customer-Experience/Migrating-7-2-2-Client-to-new-Citrix-Farm/td-p/14185

Patrick,

At this point I have loaded SLX 7.2.2 Network client on 2008 R2 server x64 and unable to create network connection to the database.  i figured i should be able to log into SLX without Citrix.  Are you aware of any issues with 64bit OS ?

error i'm getting "Database login failed: named Pipes Provider: could not open a connection to SQL Server [67]"

Thanks,

Alex

Hi Alex,

We haven't had any issue with that, but we have not moved our SLX Production database to any x64 environments. We are still hitting on the Windows Server 2003 boxes and running our database on SQL 2003 as well.  Perhaps there is an issue there if you are putting your database onto a newer environment, but it doesn't sound to be a SLX issue persay, as much as an SQL to 2008 R2 issue. Saw another post here somewhat related (but older).

http://www.slxdeveloper.com/forum.aspx?forumid=5003&postid=21914 

Quote: Originally posted by Alex error i'm getting "Database login failed: named Pipes Provider: could not open a connection to SQL Server [67]"

Alex,

Please focus a bit on the error message that you are receiving.

Named Pipes Provider relates to the Library that your SQL Client is using. I would suggest to start by using the TCPIP Library first, which would remove this error, and find out if that works for you.

If the TCPIP Library works for you, that will tell us that the problems you are having relate to either Ports or Permissions needed for the Connections over Pipes.

I typically choose to utilize just the TCPIP library for SLX, however keep in mind that you may have to create SQL Aliases depending on your configuration needs if you cannot disable the other libraries.

Before I forget, and just in case, this is done via the SQL Configuration Manager. I typically disable all protocols (but TCPIP) on the Client Side, and then ensure that on the Server Side TCPIP is enabled.

not being a dba I’m trying to work my way through

On the client side I went into SQL Server configuration manager > SQL Server 2005 Network Configuration and made sure that TCP/IP is enabled, the only other enabled object is Shared Memory

In SQL Native Client configuration > Client protocols  TCP/IP is enabled I disabled  Named Piped and shared memory is enabled

I installed SQLEXPRESS to get configuration management tool.

On the server TCP/IP is enabled..

Same error

any thoughts?

thanks