C
Cynthia
The following post was posted in December on one of the dbforum discussion groups. It is the same problem I have. Has anyone solved this problem? All of the solutions listed on this site have not been successful.
Thanks
Cynthi
We are using a combination of SQL server and Sharepoint
and Enteprise MSProject, so our team can all see the
project schedule on the web. Administrators can not only
see the project on the web, but can edit the MSProject
data in MSproject. We have a problem when certain users go
to edit the data in MSproject (an option when you are
looking at the project on the web via sharepoint). It
seems to be if the user ID is in the domain that the SQL
server is in, it works, if they are not it doesn't work
I have a document with screen snapshots of this failing, I
can send this if needed
Steps to reproduce the problem
1) Bring up Microsoft Project Web Acces
2) Go to the project center and highlight the project to
edi
3) Hit "Open in Microsoft Project
4) A screen splashes by. The title is "Microsoft Project
Server Security Login" and the text says "Please enter
your login information for the server
http://servername/projectserver
5) And then the failure dialog occurs. The title
is "Microsoft SQl Server Login" and the text says
Connection failed
SQLState: '01000
SQL Server Error:5
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpe
(Connect())
Connection Failed
SQLState: '0800
SQL Server Error: 1
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL server
does not exist or access denied
6)Then we get this Dialogin MS project
Server: Server IP/servernam
An unchecked check-box that says Use Trusted Connectio
Login ID: MSProjectUser000
Password: ******************
7) Hit OK to log in, and get the last dialog
Cannot connect
hThis coudl be
caused by a loss of netowrk connectivity, invalid username
or password, lack of an enterprise global template,
problems with the Microsoft Project Server or database, or
your Microsoft Project Server may not have enterprise
features enabled
If any user locally (in the same domain as the SQL server)
tries this, it all works perfect every time. We have had
two different users from other domains try this, and they
both get the same error
Thanks
Cynthi
We are using a combination of SQL server and Sharepoint
and Enteprise MSProject, so our team can all see the
project schedule on the web. Administrators can not only
see the project on the web, but can edit the MSProject
data in MSproject. We have a problem when certain users go
to edit the data in MSproject (an option when you are
looking at the project on the web via sharepoint). It
seems to be if the user ID is in the domain that the SQL
server is in, it works, if they are not it doesn't work
I have a document with screen snapshots of this failing, I
can send this if needed
Steps to reproduce the problem
1) Bring up Microsoft Project Web Acces
2) Go to the project center and highlight the project to
edi
3) Hit "Open in Microsoft Project
4) A screen splashes by. The title is "Microsoft Project
Server Security Login" and the text says "Please enter
your login information for the server
http://servername/projectserver
5) And then the failure dialog occurs. The title
is "Microsoft SQl Server Login" and the text says
Connection failed
SQLState: '01000
SQL Server Error:5
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpe
(Connect())
Connection Failed
SQLState: '0800
SQL Server Error: 1
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL server
does not exist or access denied
6)Then we get this Dialogin MS project
Server: Server IP/servernam
An unchecked check-box that says Use Trusted Connectio
Login ID: MSProjectUser000
Password: ******************
7) Hit OK to log in, and get the last dialog
Cannot connect
hThis coudl be
caused by a loss of netowrk connectivity, invalid username
or password, lack of an enterprise global template,
problems with the Microsoft Project Server or database, or
your Microsoft Project Server may not have enterprise
features enabled
If any user locally (in the same domain as the SQL server)
tries this, it all works perfect every time. We have had
two different users from other domains try this, and they
both get the same error