| Author |
cms2002 , sps, vs .net 2003 on windows2003
|
|
|
| I had installed windows 2003, then wss, then vs .net and then cms 2002
sp1a std ed.
The applicatino pool was set by default is spsAppPool1.
CMS was not working. I installed connector and both cms and sharepoint
work.
I tried to start working with my CMS project using VS .NET 2003.
I got:
Unable to create web project....
the two need to map to the same server location. HTTP Error 404.
I change the default pool to Default App Pool from SpsAppPool1 and I
get the following..
Unable to create web project....
the two need to map to the same server location. HTTP Error 403 access
forbidden.
I had gone thru most of the recommendations and applied them except
starting from reloading the os.
One more observation is, I tried to create a simple a.htm file in
c:\inetpub\wwwroot\ and access it thru the browser and get the error
403: access forbidden error
Can CMS 2002 Sharepoint and VS .NET work together.
Do we have to change the application pool between Default App Pool,
StsAppPool1 while working on CMS2002 and sharepoint and VS.NET?
Any documentation on how these three are supposed to work together..
I am posting this in other related boards as well. But if any one
working on CMS2002 knows answers to this issue can please respond.
many thanks
laks
| |
| Stefan [MSFT] 2004-12-18, 7:46 am |
| Hi Laks,
check this article:
http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm#AF0A8BBF-1488-450F-ADD1-E555312ADEC9
Cheers,
StTefan.
"laks" <alanlakman@yahoo.com> wrote in message
news:1103332960.278393.144200@f14g2000cwb.googlegroups.com...
> I had installed windows 2003, then wss, then vs .net and then cms 2002
> sp1a std ed.
>
> The applicatino pool was set by default is spsAppPool1.
>
> CMS was not working. I installed connector and both cms and sharepoint
> work.
>
> I tried to start working with my CMS project using VS .NET 2003.
> I got:
> Unable to create web project....
> the two need to map to the same server location. HTTP Error 404.
>
> I change the default pool to Default App Pool from SpsAppPool1 and I
> get the following..
>
> Unable to create web project....
> the two need to map to the same server location. HTTP Error 403 access
> forbidden.
>
> I had gone thru most of the recommendations and applied them except
> starting from reloading the os.
>
> One more observation is, I tried to create a simple a.htm file in
> c:\inetpub\wwwroot\ and access it thru the browser and get the error
> 403: access forbidden error
>
> Can CMS 2002 Sharepoint and VS .NET work together.
> Do we have to change the application pool between Default App Pool,
> StsAppPool1 while working on CMS2002 and sharepoint and VS.NET?
>
> Any documentation on how these three are supposed to work together..
>
> I am posting this in other related boards as well. But if any one
> working on CMS2002 knows answers to this issue can please respond.
> many thanks
> laks
>
| |
|
| Thx for the reply.
My site is configured for port 80 only. Much of my settings are
default.
SCA is configured to port 8080(installation instructions). Sharepoint
is configured to 80. Portal admin to a differnt port which is by
default...
I have set up two other machines without sharpoint and dont have this
issue with VS .NET...
I have tried to keep the IIS settings and folder permissions same as
the ones for the other two machines as well. I still get 403: forbidden
access.
more ideas...
thx.
| |
| Stefan [MSFT] 2004-12-18, 5:47 pm |
| Hi Laks,
the port is irrelevant!
If the site is NOT the default web site (independed of port) you need to
reconfigure this XML file and set the appropriate instance id.
Cheers,
Stefan.
"laks" <alanlakman@yahoo.com> wrote in message
news:1103373919.195808.256540@c13g2000cwb.googlegroups.com...
> Thx for the reply.
> My site is configured for port 80 only. Much of my settings are
> default.
> SCA is configured to port 8080(installation instructions). Sharepoint
> is configured to 80. Portal admin to a differnt port which is by
> default...
> I have set up two other machines without sharpoint and dont have this
> issue with VS .NET...
> I have tried to keep the IIS settings and folder permissions same as
> the ones for the other two machines as well. I still get 403: forbidden
> access.
> more ideas...
> thx.
>
| |
|
| Thanks for the reply again. i have inserted that line in the xml file
and still get the same. No new Visual studio project can be created
because of 403 forbidden access... any more suggestions??
Thanks very much
- laks
| |
| Stefan [MSFT] 2004-12-20, 5:48 pm |
| Inserted?
There is no need to insert this line.
You need to ADJUST this line!
It is already there!
Cheers,
Stefan.
"laks" <alanlakman@yahoo.com> wrote in message
news:1103563096.641124.29250@f14g2000cwb.googlegroups.com...
> Thanks for the reply again. i have inserted that line in the xml file
> and still get the same. No new Visual studio project can be created
> because of 403 forbidden access... any more suggestions??
> Thanks very much
> - laks
>
| |
|
| Thanks for the response. I had actually uninstalled CMS 2002 and WSS
2003. and installed in the order of
VS .NET, CMS 2002 on a different port 85, and then installed WSS to
default port (80). I create projects on the port that CMS is installed
to(85) and things are working fine. I had to get things rolling so went
with what i did. Just getting to read your message. The next machine i
configure i will try it out!
Thanks again
Cheers,
- laks.
| |
| Niklas E 2004-12-26, 7:46 am |
| Seems like a simple hotfix could be in place to avoid all users from having
to having to alter .config files and looking for web site IDs. CMS should
handle that.
Thanks alot for the FAQ. It is really good, but alot of these FAQs could be
fixed by Microsoft so users wouldn't end up in these situations.
When is SP2 due? Is there a fix list for SP2? Or has Microsoft stopped
developing CMS or what is happening with CMS in the future? What should we
tell our customers who are considering buying CMS?
Best regards
Niklas Engfelt
"Stefan [MSFT]" <stefang@online.microsoft.com> wrote in message
news:%23MZcDBP5EHA.524@TK2MSFTNGP09.phx.gbl...
> Hi Laks,
>
> check this article:
> http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm#AF0A8BBF-1488-450F-ADD1-E555312ADEC9
>
> Cheers,
> StTefan.
>
> "laks" <alanlakman@yahoo.com> wrote in message
> news:1103332960.278393.144200@f14g2000cwb.googlegroups.com...
>
>
| |
| Stefan [MSFT] 2004-12-26, 5:47 pm |
| Hi Niklas,
actually Windows XP is the recommended platform for MCMS developers.
And WinXP only supports the default web site. This is the reason that no
other web site is officially support by MCMS.
The product team is currently evaluating all details about a further service
pack for MCMS but a final decision has not been communicated.
Cheers,
Stefan.
"Niklas E" <raven_tln0sp4m@hotmail.com> wrote in message
news:OMu7Swz6EHA.2032@tk2msftngp13.phx.gbl...
> Seems like a simple hotfix could be in place to avoid all users from
having
> to having to alter .config files and looking for web site IDs. CMS should
> handle that.
>
> Thanks alot for the FAQ. It is really good, but alot of these FAQs could
be
> fixed by Microsoft so users wouldn't end up in these situations.
>
> When is SP2 due? Is there a fix list for SP2? Or has Microsoft stopped
> developing CMS or what is happening with CMS in the future? What should we
> tell our customers who are considering buying CMS?
>
> Best regards
> Niklas Engfelt
>
>
> "Stefan [MSFT]" <stefang@online.microsoft.com> wrote in message
> news:%23MZcDBP5EHA.524@TK2MSFTNGP09.phx.gbl...
http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm#AF0A8BBF-1488-450F-ADD1-E555312ADEC9[vbcol=seagreen]
>
>
| |
| Niklas E 2004-12-26, 5:47 pm |
| Ok. We develop on Windows 2003 machines to be sure to not having other OS
problems while deploying and to be able to debug in exactly the same way as
customers test and production environments. (I have had enough of those "It
should work fine" but it doesn't. ) We also have other products some of
which requiring server OS, e.g. SPS 2003.
Would be nice with a CMS 2002 SP2 ;)
Best regards
Niklas
"Stefan [MSFT]" <stefang@online.microsoft.com> wrote in message
news:eeo6eS46EHA.1400@TK2MSFTNGP11.phx.gbl...
> Hi Niklas,
>
> actually Windows XP is the recommended platform for MCMS developers.
> And WinXP only supports the default web site. This is the reason that no
> other web site is officially support by MCMS.
> The product team is currently evaluating all details about a further
> service
> pack for MCMS but a final decision has not been communicated.
>
> Cheers,
> Stefan.
>
>
> "Niklas E" <raven_tln0sp4m@hotmail.com> wrote in message
> news:OMu7Swz6EHA.2032@tk2msftngp13.phx.gbl...
> having
> be
> http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm#AF0A8BBF-1488-450F-ADD1-E555312ADEC9
>
>
| |
| Stefan [MSFT] 2004-12-27, 2:47 am |
| Hi Niklas,
point taken. But the chance to get this into a service pack are very low as
a service pack usually packages up several hotfixes and do not implement new
features.
Cheers,
Stefan.
"Niklas E" <raven_tln0sp4m@hotmail.com> wrote in message
news:eWYGBd56EHA.2180@TK2MSFTNGP10.phx.gbl...
> Ok. We develop on Windows 2003 machines to be sure to not having other OS
> problems while deploying and to be able to debug in exactly the same way
as
> customers test and production environments. (I have had enough of those
"It
> should work fine" but it doesn't. ) We also have other products some of
> which requiring server OS, e.g. SPS 2003.
>
> Would be nice with a CMS 2002 SP2 ;)
>
> Best regards
> Niklas
>
>
> "Stefan [MSFT]" <stefang@online.microsoft.com> wrote in message
> news:eeo6eS46EHA.1400@TK2MSFTNGP11.phx.gbl...
should[vbcol=seagreen]
could[vbcol=seagreen]
http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm#AF0A8BBF-1488-450F-ADD1-E555312ADEC9[vbcol=seagreen]
2002[vbcol=seagreen]
sharepoint[vbcol=seagreen]
access[vbcol=seagreen]
>
>
|
|
|
|