The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
Conectile Dysfucntion - If you server is down for more than 4 hours contact a doctor
Posted: 02 Jan 08 4:36 PM
|
I have a server (WinSrv2003 sp2) which houses my SLX web server. It also now has the sales client on it (to test this issue). I am unable to set a datalink connection from this machine.
Symptoms:
First when I try to open a client (sales, web manager - same result) I get the screen that asks if want to change the port, retry or skip to go to datalink manager (A SalesLogix server was not detected...) . So I skip to data link manager and try to set up connection. When I test the connection I get 'Unable to initialize data dictionary'.
We upgraded to SQL2005 a few weeks ago and installed the SQL Native provider on the machine. All worked fine. Monday we moved the SLX Db to a SAN. This also went well and other machines are able to log on fine.. Not sure if this is related or not..
Not sure where to go with this one.. SLX Tech support says unistall all SLX, Clean registry and reinstall.. I would like to know if there is anything else I can try before I 'cleanse' the machine. Thanks |
|
|
| |
| |
|
Re: Conectile Dysfucntion - If you server is down for more than 4 hours contact a doctor
Posted: 02 Jan 08 6:01 PM
|
| Typically, the data dictionary issue is almost always due to the absence of the SQL Native Client. You say you have installed that. I'd certainly re-install it and also make sure it's at the same revision as the DBServer (eg SP2). Also, in the SLXServer - how are you connecting to SQL Server - via NC or via SQL OLEDB ? Make sure both are consistent. |
|
|
|
Re: Conectile Dysfucntion - If you server is down for more than 4 hours contact a doctor
Posted: 02 Jan 08 7:28 PM
|
Yeah, I reconized the error as the SQL native client and thought I had a quick fix, but have unistalled and reinstalled twice.. ran the oledb provider install, checked service packs, rebooted several times.. I didn't check the revision of the SQL Native Client.. can I download it for SP2, or does it get patched? I'll check the MS site. As I mentioned, we upgraded to SQL 2005 several weeks ago. We ran the same install on about 100 client machines with no problems..
Also thought I would mention that when trying to set up the datalink the server will not autopopulate, but if I type it in I can find the connection in the drop down. So it kind of sees the connection, but can quite seal the deal..
|
|
|
|
Re: Conectile Dysfucntion - If you server is down for more than 4 hours contact a doctor
Posted: 02 Jan 08 11:19 PM
|
You can download it separately nowadays, it would also be patched during an SP2 install - the sqlncli.msi is dated 20th Feb 2007 and is 3,529Kb. Let me know if you can't locate it and I'll upload it for you.
In terms of the auto-populate. This is typically Win2003 related and normally not a problem as you simply type in the details and it all still works as you say. Have you switched off all AV's, F/walls etc. temporarily ? (inc. Win2003's own). You might want to also check that you haven't created an aliases in the network config for SQL2005 that are pointing at wrong server, IP etc. and that network protocols are IP etc.
*** Did you check that the SLX Server is running via Native Client or MSSQL provider ??
I'm still unclear with what is where - could you describe a little more:
(a) Server A - SQL Server 2005 (data reside on SAN)
(b) Server B - SLX Server
(c) Server C - Web Server
or Server C is also Server B for example...
|
|
|
|
Re: Conectile Dysfucntion - If you server is down for more than 4 hours contact a doctor
Posted: 03 Jan 08 7:57 AM
|
The sqlncli.msi I have been working with is dated Feb 10, 2007 and is 3,613,696 bytes... Google and MSDN (by google and MSDN I of course mean me) can't seem locate the one you speak of.. I found a few downloads with earlier dates..
Windows firewall is not running on this machine and I have tried shutting down AV - connection still fails. I am not sure where to check for 'aliases in the network config for SLQ2005.
***Also not sure wehre to check if SLX Server is running via native or MSSQL.. - Are you refering to the connection on the app server?
Your break down of servers is correct - The app, db and webserver are all seperate machines..
As a note, I tried to install the admin tools to see if that would 'jostle' this thing into shape (long shot). I cannot complete the install - it fails with the error
'Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 10005
Date: 01/03/2008
Time: 8:35:14 AM
User: xxxx\webdll
Computer: xxxSLXWEB
Description:
Product: SalesLogix Admin Tools and Servers -- Internal Error 2753. slxnetextensionsinstall.exe
|
|
|
|
Re: Conectile Dysfucntion - If you server is down for more than 4 hours contact a doctor
Posted: 03 Jan 08 9:16 AM
|
3,613,696 bytes is 3529Kb - wouldn't worry about the date - it's the right one.
Re-Install Admin again - this time, select custom and remove the .NET extensions. But, either way, you have a .NET/Installer issue to get this error.
***Also not sure wehre to check if SLX Server is running via native or MSSQL.. - Are you refering to the connection on the app server?
Wherever the SLX Server is installed (Server B in my scenario) - in there - check how the connection is defined to the database server (Server A) - it will either be Native Client or MSSQL OLEDB Provider (this is NOT the SLX Connection)
|
|
|
|
Re: Conectile Dysfucntion - If you server is down for more than 4 hours contact a doctor
Posted: 03 Jan 08 9:36 AM
|
In regard to aliases:
Start | Programs | Microsoft SQL Server 2005 | Configuration Tools | SQL Server Configuration Manager - expand SQL Native Client, Aliases are here.
You shouldn't need any aliases set - nor should there be any.
Whilst here - ensure the relevant protocols are on for both server and client - should be (in order) shared mem, tcp-ip, named pipes. |
|
|
|
Re: Conectile Dysfucntion - If you server is down for more than 4 hours contact a doctor
Posted: 03 Jan 08 10:20 AM
|
Hmmmm.. I find 3 alias on the app server - which was the DB server until moved to the SAN.. I deleted them. I found no alias on the SAN db server..
Also got the admin installed with your tip.. no change in situation..
I tried to browse to the san server from the web server and vice versa - neither could see each other - although both can see the app server. I have the network admin looking into this .. |
|
|
|
Re: Conectile Dysfucntion - If you server is down for more than 4 hours contact a doctor
Posted: 03 Jan 08 10:30 AM
|
Hmm, we seem to be talking cross purposes too - the SAN is not a server - it's simply a device that has plenty of disks, connected via iSCSI or Fibre, with LUN's etc. Ordinarily, you would have a SQL2005 server (Server A in my example) that has the MDF/LDF's mounted on a LUN within the SAN (it appears local to SQL Server but is mounted on the SAN) - this gives you the performance/redundancy from the disks/fibre but doesn't host SQL Server.
If this were the case - your SQL Server hasn't "moved" - but, in your case, it sounds like it has - could you clarify??
|
|
|
| |
| |
|
Re: Conectile Dysfucntion - If you server is down for more than 4 hours contact a doctor
Posted: 06 Jan 08 7:49 PM
|
| Resolved - I would like to especially thank Mike Spragg for his extra effort to assist me with this. The problem was a permissions issue - The web server is configured with a DMZ to allow traffic outside the network to hit the server. The network admin needed to add an additional IP to the Access Control List - either in the firewall or router - not exactly sure where the ACL lives.. Thanks again Mike for the additonal assistance. |
|
|
| |
|