Smartlist doesn't appear and the lookup doesn't display contents

Something happened to a pc where SQL 2000 & GP is installed locally.

When trying to see the smartlist, the windows is empty.  Also when clicking the lookup no contents appear.

However, if we click on the navigator button at button left of of a inquiry window, we get a SQL Error (see pic).  If we click on lookup a master record, it works; it gives the error when inquirying a inquiry window that would display transaction.

After reading the error, it looks that it may be the SQL instance

Please advice
rayluvsAsked:
Who is Participating?
 
Abdulmalek_HamshoCommented:
There is a conflict between your OS (Windows System) collation (in Regional Settings) and your DB collation.
0
 
rayluvsAuthor Commented:
0
 
Abdulmalek_HamshoCommented:
Sorry, conflict between your Windows Locale and DB Collation.
0
Introducing Cloud Class® training courses

Tech changes fast. You can learn faster. That’s why we’re bringing professional training courses to Experts Exchange. With a subscription, you can access all the Cloud Class® courses to expand your education, prep for certifications, and get top-notch instructions.

 
rayluvsAuthor Commented:
Thank you.  We began to check how to resolve this and used the following scripts to determine:

sp_helpsort
SELECT SERVERPROPERTY('ProductLevel')
SELECT @@VERSION
SELECT SERVERPROPERTY('ProductVersion')
SELECT SERVERPROPERTY('Edition')

How can we determine Windows Locale and DB Collation?
0
 
Abdulmalek_HamshoCommented:
As I mentioned before: Control Panel -> Regional Settings or Region and Language ->  Advanced or Administrative -> Change Locale.

One more important thing to check. When you create the ODBC connection in the client side, make sure to uncheck the following options:

1- Perform Translation for character data.
2- Use regional settings when outputting currency ...etc.

Please try this before checking the collation issue.
0
 
rayluvsAuthor Commented:
Ok will do this morning
0
 
rayluvsAuthor Commented:
Verified Change Locale and is correct (the same as the PC that GP works fine).  Also the ODBC, all is unchecked.

How can we verify the DB collation against the PC that is working fine?
0
 
Abdulmalek_HamshoCommented:
The collation is related to the DB not the PC.

Right click the SQL server in SQL Management Studio and select properties, you will find it here.
0
 
rayluvsAuthor Commented:
They are different.  

Do we have to reinstall SQL?
0
 
Abdulmalek_HamshoCommented:
No no, just give me what're your OS locale and your DB collation.
0
 
Abdulmalek_HamshoCommented:
And what's your Windows version?
0
 
rayluvsAuthor Commented:
Windows version is Windows 7

For DB collation we used "sp_helpsort".  The result:

      Latin1-General, case-insensitive, accent-sensitive, kanatype-insensitive, width-insensitive
      for Unicode Data, SQL Server Sort Order 52 on Code Page 1252 for non-Unicode Data.



0
 
Abdulmalek_HamshoCommented:
Well, it seems your windows locale is spanish. You need to make spanish enabled rather than being your default language in your windows. This can be done in Region & Language Settings.
0
 
rayluvsAuthor Commented:
Yes its Spanish and also we changed it to other Spanish regions, like Honduras, etc. and still same problem.

Is there a way to know the instance collation and the DB collation?> Maybe there is the conflict?

Please advice
0
 
Abdulmalek_HamshoCommented:
To change the DB Collation you would need days, so please concentrate on your Windows locale, please make it English with Spanish enabled.
0
 
rayluvsAuthor Commented:
English with spanish? How?
0
 
Abdulmalek_HamshoCommented:
Control Panel -> Region and Language -> Administrative -> Change System Locale -> Select English here
Control Panel -> Region and Language -> Keyboards and Languages -> Install/Uninstall Languages -> Install Spanish
0
 
rayluvsAuthor Commented:
Hi,

We just reinstall SQL & GP on the workstation and restore the backup DB and it worked.  Didn't get to test your last recommendation.
0
 
rayluvsAuthor Commented:
The problem is fixed.  What we noticed was that when initially SQL was installed it was another collation (but we are not sure since when we reinstall now we made sure that collation be the same as the server); all is working fine.

Any observations?
0
 
Abdulmalek_HamshoCommented:
Great. I expected that you have had a working SQL DB with the required collation.
0
 
rayluvsAuthor Commented:
Update of our situation & how it was resolved:

I was just informed that SQL wasn't re-install, the DB Collation was change.  I gave instruction not to do it since you said it takes days to do this, but one of the guys found the solution.  So anyways, here is what we did incase any user here ever need to do this:

There is a tool that comes with SQL, it's located at C:\Program Files\Microsoft SQL Server\80\Tools\binn.  The tool is called "rebuildm.exe".  We stopped the service and ran the tool; there is an option where you choose and DONE!
0
 
Abdulmalek_HamshoCommented:
rebuildm.exe does not rebuild the Collation dear, it rebuildes the "master" DB. I think you changed the collations of the master DB only, which is not the sufficient solution to your case.
0
 
rayluvsAuthor Commented:
That's it, rebuilding the master DB, in the collation configuration window.  Obviously we had to backup our DB, detach, then re-attach, re-work the security info, etc.  I personally didn't do this, but it's working fine now.

Thanx
0
 
rayluvsAuthor Commented:
Thanx.  Though the answered awarded didn't fix our problem, it was a possible cause if it was.

In our case, we fixed the "Smartlist doesn't appear and the lookup..." problem with SQL tool rebuild.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.