I'm still struggling with the notion that all of our developers must have Windows Server 2003 running on their desktops to build CS based applications.
There are few references on the net about this and the bottom line is that doing it on XP is an option but not recommended ('I told you so' on one of the blogs).
Being aware that some features may not work (warehousing) I still would like to have development done on XP. I've installed CS2007, already have VS2005. I've unpacked CSharpSite and when trying to access the page get this error: 'Login failed for user ''. The user is not associated with a trusted SQL Server connection'. I went to Commerce Server Mangager and for each (I hope I've covered all) connection to into Profiles, Marketing, Inventory and Transaction changed the connection string to use SQL Server authentication. SQL Server lives on a different machine. I created named user and assigned all bottom roles from that were avialable on roles property.
I hope I went thorugh all of connections. My understanding is that this would allow mylocalmachine\ASPNET user to access sqlserver on the other server
Developer's workstation
Pockey
does this mean that there's workaround to use machine1\ASPNET account and access remote database for cs2007 on machine2 using sql server authentication instead of windows base authentication
soulmate75
I don't want to sound negative but do I need VS2005 on my XP for primary development and a copy on VPC running WS2003 for CS2007 development They probably can shared same source on XP HD and can do co/ci of the code using XP but seems that CS2007 development I need a copy of new OS (WS2003), VS2005, CS2007 and any addons that are used for CS development.
Would possibly running 2 copies of VS2005 - one on XP and 2nd on VPC degrade the performance of the machine
spree
Just to double check, you've created needs the following role permissions in SQL for your new user:
MSCS_Admin: admin_reader_role
MSCS_CatalogScratch: db_datareader, db_datawriter, db_ddladmin
[SITE]_Marketing: db_ddladmin, mktg_runtime_role
[SITE]_MarketingLists: db_datareader
[SITE]_ProductCatalog: ctlg_catalogReaderRole, Inventory_RuntimeRole
[SITE]_Profiles: Profile_Schema_Reader, Profile_Runtime
[SITE]_TransactionConfig: Orders_Runtime
[SITE]_Transactions: Orders_Runtime
If you've followed these and you still can't connect, I honestly don't know what else this could be. Try writing a console application which creates a SQL Connection to a commerce server database using the same credentials to verify that this is in fact Commerce Server and not another infrastructure issue.
Dimmi3
mliesmons
Windows XP installation Instructions
See if the link above helps.
-Max
adi151478
mpco,
Keep in mind that the accounts you've created on your local windows XP installation and the logins you've created on SQL might not refer to the same account, as your development machine's "mylocalmachine\ASPNET" and the SQL Server machine's "mylocalmachine\ASPNET" aren't necassarily the same thing.
Is there any reason why you aren't using a domain controller in this environment Regardless of whether or not you develop on XP or Server, you should probably get all the machines on the same domain so that you can use domain accounts instead of machine accounts for SQL Server. This way, you can also go back to using integrated authentication for your connection strings.
I don't think this is an issue of Server vs XP, I think you're just using the wrong accounts to log in to SQL, and attaching all of your development machines to the same domain / active directory should greatly simplify your setup.
Musafir
I was trying to open sql server on machine 2 access through connection strings on machine 1. By default when cs installed on machine 1 it set database authentication to windows based. I've changed to a specific sql server user account that I've created on machine 2 assuming that when CS installed on machine 1 will use connection strings to connect to db on machine2.
I am using AD but have no control who runs IIS on machine 1. All machines in AD are members of same domain but IIS on machine 1 (XP Pro) is run under machine1\ASPNET instead of domainname\ASPNET
WarrickF
I used to run CS2002, VS 2003 and SQL 2000 with 512 mgs RAM on a Toshiba 9100 laptop with the VPC running on an external USB drive and I was happy with the performance.
The trick to speed up your VPC solution is make sure that you have an external drive to run your VHDs, put exceptions in your virus scanner to not scan VPC files and processes, run defrag on under the VPC system then defrag the external drive then run compacting wizard for your VPC. The smaller the drive the faster the VPC will run. Make sure not to run any Service or install anything that is not needed. For example if you are installing VS and you only code with C# then don't install the other languages better yet just install the VS express. If you are running desktop search tools make sure to exclude your external drive. The external drive should be 7300 RPM or better and a large cache helps.
Hope this helps,
-Max
JonAkaJon
that does sound encouraging (hopefully we don't have to install WS2003 as aprimary OS on developers machines).
I've tried to load VPC but it could not boot and it was asking me to load OS into CD. I've loaded WS2003 and it started to format virutal drive, install OS, etc. Is there a simpler way of doing it
Also, would VS2005 installed on XP part of the disk be visible on VPC or do I need to install new instance of VS2005 on VPC virtual disk. Also, can VPC WS2003 see XP partitions... actually I need a cheat sheet how to quickly get this up and running.
SheelaKathuria
I'm pretty sure that relates to the hotfix that Microsoft provides only to support callers. I had the same issue, so I gave up trying to run it on my own machine.
I can't remember the KB ID but I'm sure somebody will.
Paul
Rossel
mpco,
You shouldn't need to install Server 2003 as the primary workstation. VPC runs pretty well on either environment, I don't think you should have to reformat anything. Unless you've downloaded a pre-loaded VHD from somewhere, you're going to have to go through the process of installing an operating system on the image, there's really no quick way around that.
The good news is that once you've got everything installed, you can make copies of that VHD file and distribute it to your development team, so once you get that first image prepared, you shouldn't need to go through the process again.
You can technically work on your VHD from your XP installation of VS2005, although I think it simplifies debugging if you've got everything installed on the VPC. Again, you'll be able to see your physical hard drives if you install virtual machine additions on your Virtual PC.
Michael Herman - Parallelspace
yes, machine 1 and 2 configured as listed. Both are part of same AD domain. SQL based authentication in place. Can do sqlcmd to dbs on sql server running on machine2. Roles assigned as listed on one of the previous postings. Still not working..
I'm having doubts if this is worth pursuing since all blogs and these postings recommend doing development on WS2003. We have 45 developers and they cross work on CS and other projects. Does this mean that they have to have WS2003 instead of XP
I've seen someone recommending to run VPC using WS2003 but what would this change. I don't understand how VPC works but I don't think I could access XP part of the disk through WS2003 running VPC.
Chee Kiang
Just to clarify, is this the scenario you are dealing with:
Both machines reside in the same Active Directory domain/forest. You have changed the Commerce Server and site resource connection strings to use SQL-based authentication in place of Windows authentication.
If that is the case can you access the database server through SQL Management Studio / Enterprise Manager or SQLCMD / OSQL on Machine 1 As Joe notes do you have the appropriate roles assigned to the SQL Server account
It is recommended that you develop under Windows Server 2003 because it runs IIS 6 and will best represent your destination environment. The concept of application pools alone makes a difference when dealing amongst the two environments. There are other differences worth that are outlined in the MSDN library. Thankfully we'll see that problem go away with Windows Vista as the IIS 7 shipping there is supposed to mirror what ships in the next Windows Server release. If you want to leverage Windows authentication you can try setting the identity element in the web.config to emulate the concept of an application pool with a specific identity.
Cheers,
Colin
prk
mpco,
I think you're confusing Virtual PC with running multiple OS partitions.
Virtual PC runs on top of an instance of windows XP, you don't need to format your machine or change the OS to run VPC.
VPC provides an extra layer of insulation from any weird configuration changes that your developers have made on their individual machines, and establishes a controlled development environment such that code that programs developed on one VPC image should work correctly on another machine with the same baseline configuration.
In your case, you should dowload VPC (http://www.microsoft.com/windows/virtualpc/default.mspx), run it on your Windows XP machine and create a new virtualized environment which runs Commerce Server 2007, Windows Server 2003, VS2005 and SQL Server 2005.
If I remember correctly, you do need to install Virtual Machine Additions to allow developers to exchange files between a VPC and a physical machine, but installing that only takes a few minutes. There's honestly no reason I can think of for developing anything outside of a virtual environment anymore.