Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Cannot Login to MS GP

1,069 views
Skip to first unread message

frdbadf

unread,
Aug 11, 2008, 1:02:12 PM8/11/08
to
I have posted about this problem previously. I have a new install, MS SQL
2005 Standard. I can open MS SQL Server Management Studio, choose the SQL
named instance, login as SA there.

The SQL server is installed in mixed mode, doci 1252.

I have installed GP 10.0, however I cannot log in to GP Utilities, "Your
attempt to log in to the server failed because an unknown error occurred when
the user ID and password were being verified. Attempt to log in again."

This happend in office on a new pre installation server and now is occuring
on-site with client. The only difference between these 2 instances and my
past experience with GP has been the sort order I chose.

Any ideas?
--
Phil Gilbert
Free Radical, LTD.

frdbadf

unread,
Aug 11, 2008, 1:27:06 PM8/11/08
to
The exact version of SQL server is Server Workgroup Edition, 9.0.1399 RTM.

Server collation is listed as: SQL_Latin1_General_CP1_CI_AS


--
Phil Gilbert
Free Radical, LTD.

Mariano Gomez

unread,
Aug 11, 2008, 5:44:09 PM8/11/08
to
Have you tried a DEXSQL.LOG? Open your DEX.INI and set the following entries
to TRUE:

SQLLogSQLStmt=TRUE
SQLLogODBCMessages=TRUE
SQLLogAllODBCMessages=TRUE

In addition, have you setup a connection with SQL Server Native Client? If
so, is your connection validating properly?

Best regards,
--
MG.-
Mariano Gomez, MIS, MCP, PMP
Maximum Global Business, LLC
http://www.maximumglobalbusiness.com

frdbadf

unread,
Aug 11, 2008, 8:42:10 PM8/11/08
to
I enabled the statements and checked the DexSQL.log. It gives ERR 87, Named
Pipes Provider: Invalid parameter(s) found.

I checked SQL Native Client Configuration, Client Protocols, Named Pipes and
enabled it.

I am really perplexed as to where all of a sudden I am failing in the SQL
server install. I installed 2 with no problem, then on this 3rd Dynamic
Client who I am preparing to migrate their data on I have failed with this
same error on the offsite (my office) test server and their server on-site.

I just wonder what I am doing wrong suddenly.

thanks for the help.


--
Phil Gilbert
Free Radical, LTD.

frdbadf

unread,
Aug 11, 2008, 10:25:02 PM8/11/08
to
Found the problem... Upon installing MS Dynamics GP 10.0, when it asked for
the SQL server, I used the following format; \\server\sqlserver, Dynamics
accepted the entry and installed. Upon uninstalling and resintalling on my
test server, I entered using this format; server\sqlserver, problem solved.
I have already made change on Production server via remote access and success
there as well.

Thanks for trying to help Mariano! I learned somethings in the process.

Mariano Gomez

unread,
Aug 12, 2008, 10:19:01 AM8/12/08
to
Phil,

In your first installation, you used the server format for named pipes
(\\.\pipe\sql\query) hence the reason for the error.

Hal Steinkopf

unread,
Dec 2, 2010, 10:50:43 AM12/2/10
to
I have run across this same error under different circumstances. I am trying to access a SQL 2008 R2 datasource from a Windows 7 workstation with GP Utilities and get this error if the connection is a "SQL Native Client" ODBC setup. I changed it to a "SQL Server Native Client 10.0" ODBC connection and the problem went away.

Hope this helps someone.

Hal Steinkopf.
hstei...@sjra.net
In-house GP Administrator.

> On Monday, August 11, 2008 1:02 PM frdbad wrote:

> I have posted about this problem previously. I have a new install, MS SQL
> 2005 Standard. I can open MS SQL Server Management Studio, choose the SQL
> named instance, login as SA there.
>
> The SQL server is installed in mixed mode, doci 1252.
>
> I have installed GP 10.0, however I cannot log in to GP Utilities, "Your
> attempt to log in to the server failed because an unknown error occurred when
> the user ID and password were being verified. Attempt to log in again."
>
> This happend in office on a new pre installation server and now is occuring
> on-site with client. The only difference between these 2 instances and my
> past experience with GP has been the sort order I chose.
>
> Any ideas?
> --
> Phil Gilbert
> Free Radical, LTD.


>> On Monday, August 11, 2008 1:27 PM frdbad wrote:

>> The exact version of SQL server is Server Workgroup Edition, 9.0.1399 RTM.
>>
>> Server collation is listed as: SQL_Latin1_General_CP1_CI_AS
>>
>>
>> --
>> Phil Gilbert
>> Free Radical, LTD.
>>
>>
>> "frdbadf" wrote:


>>> On Monday, August 11, 2008 5:44 PM MarianoGome wrote:

>>> Have you tried a DEXSQL.LOG? Open your DEX.INI and set the following entries
>>> to TRUE:
>>>
>>> SQLLogSQLStmt=TRUE
>>> SQLLogODBCMessages=TRUE
>>> SQLLogAllODBCMessages=TRUE
>>>
>>> In addition, have you setup a connection with SQL Server Native Client? If
>>> so, is your connection validating properly?
>>>
>>> Best regards,
>>> --
>>> MG.-
>>> Mariano Gomez, MIS, MCP, PMP
>>> Maximum Global Business, LLC
>>> http://www.maximumglobalbusiness.com
>>>
>>>
>>> "frdbadf" wrote:


>>>> On Monday, August 11, 2008 8:42 PM frdbad wrote:

>>>> I enabled the statements and checked the DexSQL.log. It gives ERR 87, Named
>>>> Pipes Provider: Invalid parameter(s) found.
>>>>
>>>> I checked SQL Native Client Configuration, Client Protocols, Named Pipes and
>>>> enabled it.
>>>>
>>>> I am really perplexed as to where all of a sudden I am failing in the SQL
>>>> server install. I installed 2 with no problem, then on this 3rd Dynamic
>>>> Client who I am preparing to migrate their data on I have failed with this
>>>> same error on the offsite (my office) test server and their server on-site.
>>>>
>>>> I just wonder what I am doing wrong suddenly.
>>>>
>>>> thanks for the help.
>>>> --
>>>> Phil Gilbert
>>>> Free Radical, LTD.
>>>>
>>>>
>>>> "Mariano Gomez" wrote:


>>>>> On Monday, August 11, 2008 10:25 PM frdbad wrote:

>>>>> Found the problem... Upon installing MS Dynamics GP 10.0, when it asked for
>>>>> the SQL server, I used the following format; \\server\sqlserver, Dynamics
>>>>> accepted the entry and installed. Upon uninstalling and resintalling on my
>>>>> test server, I entered using this format; server\sqlserver, problem solved.
>>>>> I have already made change on Production server via remote access and success
>>>>> there as well.
>>>>>
>>>>> Thanks for trying to help Mariano! I learned somethings in the process.
>>>>> --
>>>>> Phil Gilbert
>>>>> Free Radical, LTD.
>>>>>
>>>>>
>>>>> "frdbadf" wrote:


>>>>>> On Tuesday, August 12, 2008 10:19 AM MarianoGome wrote:

>>>>>> Phil,
>>>>>>
>>>>>> In your first installation, you used the server format for named pipes
>>>>>> (\\.\pipe\sql\query) hence the reason for the error.
>>>>>>
>>>>>> Best regards,
>>>>>> --
>>>>>> MG.-
>>>>>> Mariano Gomez, MIS, MCP, PMP
>>>>>> Maximum Global Business, LLC
>>>>>> http://www.maximumglobalbusiness.com
>>>>>>
>>>>>>
>>>>>> "frdbadf" wrote:


>>>>>> Submitted via EggHeadCafe
>>>>>> Microsoft LINQ Query Samples For Beginners
>>>>>> http://www.eggheadcafe.com/training-topic-area/LINQ-Standard-Query-Operators/33/LINQ-Standard-Query-Operators.aspx

0 new messages