SQL server does not exist (sometimes)

[trava2]

I am running Macola SQL 7.6.1a on a new MS SQL 2000 server. 2 gigs RAM/{1} 2.4 xeon processor/gig nic. The users are running the Macola client on their workstations. During their normal day to day activities, everything works as it should, but during posting or any long process I get the following error. It seems to be random tables and times during these processes, and like I said access to the same tables works fine during normal activity, so I can rule out permissions.

Severe COM/ADO error occured in MacMSS.dll
DB Provider Error:Native Error number: 17
[DNETLIB][ConnectionOpen (connect()).]SQL Server does not exist or access denied.

Thanks,

Travis

Anyone seen my keys?

 

[kscheeler]

I would start with the following Microsoft article :

http://support.microsoft.com/default.aspx?scid=kb;en-us;328306&Product=sql2k

I believe your issue is more server related than client related. There are other links from that article talking about the possibility of the clients changing the connection protocol which should only be TCPIP vs. Named Pipes and also the other possibilities.

It's a good article to walk through different things to check.

Kevin Scheeler

 

[kscheeler]

Another possibility from Macola's infomine is:

Check for and rename the file MACREG7.dll if found in the \MACSQL root directory.

This file should be located in the C:\Program Files\Common Files\Macola Shared directory on each workstatio

Your path would be something like m:\macsql if you're looking on the SQL Server or c:\macsql if looking at a local copy on a citrix server.

Kevin Scheeler

 

[kscheeler]

One other thing has to do with functions that print large reports. Here's another article from Macola's infomine.

Windows XP workstations have a wait or timeout state and never complete when printing large reports or data intensive processes in Progression. Other workstations such Windows 98 and Windows 2000 print the same reports with out hesitation. What could cause this issue?

Answer:
The default maximum number of ephemeral TCP ports for Microsoft Windows is 5000. To increase the maximum number of ephemeral ports you must set the following registry parameter:

WARNING: The incorrect use of Windows Registry Editor may cause serious problems that may require a reinstall of the Windows operating system. Exact Software cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

Step1:

From Windows Start, Run, Regedt32.exe

Select, Hkey_Local_Machine\System\CurrentControlSet\Services\Tcpip\Parameters

From the Edit Menu, Select NEW, Select DWORD Value. Type the Value Name: MaxUserPort, select Enter.

Double Click on the new value name, MaxUserPort, from the Value window, select Decimal, set the Value data to 10000, select OK.

Step2:

From the Edit Menu, Select NEW, Select DWORD Value. Type the Value Name:TcpTimedWaitDelay, select Enter.

Double Click on the new value name, TcpTimedWaitDelay, from the Value window, select Decimal, set the Value data to 30, select OK.

Exit the registry from the menu bar, changes will take effect immediately without reboot of the workstation.


Hopefully, these will help solve the problem.

Kevin Scheeler

 

[trava2]

Funny, you'll answer me here before returning my call. Now I know where to go to find you. I'll try all of the above.

Thanks

T

 

[trava2]

Should be only tcp/ip ? I have them set with tcp/ip and named pipes.

 

[kscheeler]

I noticed your response here before I emailed you back. Yes, you should only have the clients connect to SQL via TCPIP. You can go into the client network utility and disable Named Pipes and you can also do it from the Server from Server Network Utility.

Kevin Scheeler

 

[trava2]

I tried all of above, no change i still get the error. I was looking at locked files and found:

select *From glctlfil_sql is locked by supervisor

There was no one logged on as supervisor. Could locked files be causing this error ??

Maybe Citrix in and take a look ?

T

A waste is a terrible thing to mind

 

[trava2]

do you think norton vp could be causing this ?

 

[abaldwin]

I would check to see that your DNS settings in house are correct.

Also check the problem workstations and insure that the shortcut they are using to start macola is using the proper pathing and not the unc pathing.

Andy

Andy Baldwin

 

[trava2]

I've checked DNS. Everything appears fine all records are correct and no errors in the event log. Why would you say to look there though. The reason I ask is that the sql server was the PDC emulator DC to start with. The first in this domain. I did find a record in DNS that pointed GC to this server, but I have since deleted it and the problem still exists. Is there anything in particular I can look for or any performace monitors I can run to try and narrow this down ? Anyone know if not being time synchronized may cause something like this ?

Thanks

Travis