On Windows 2000, I keep getting the error "Cannot create another system semaphore" when copying files from a WebDAV folder. The WebDAV folder is on a Windows Sharepoint 2003 server.
The strange thing is that Excel can open files on this server. But I cannot drag and drop the files to copy an entire folder.
1. Fix DCOMCNFG permissions so that System and Interactive users have "Allow access" in default security.
No luck.
2. Download Webdrive
No luck - croaks with error "Error performing inpage operation". Turns out this error just means that cannot access the source file.
It looks like an interesting application. Lets you map all sorts of servers to a Windows drive letter.
3. Install Perl HTTP::DAV.
http://www.webdav.org/perldav/
No luck - CPAN installer hangs during the build process.
4. Install Perl HTTP::DAV on Cygwin
No luck - don't have LWP and don't know how to setup a proxy for the default FTP.
5. Install "sitecopy" on Cygwin.
http://www.lyra.org/sitecopy/cygwin/sc-cygwin-tips.html
Need to install libxml2 first.
"Cannot authorize user" on the webserver!
This is frustrating!
6. Use a Java client "http://www.ics.uci.edu/~webdav/download.html"
Doesn't work with Sharepoint - Access denied!
7. Use Unison
http://www.cis.upenn.edu/~bcpierce/unison/index.html
Doesn't support WebDAV. Support SSH though.
Some nice collection of stuff about WebDAV
http://www.ella-associates.org/alexis-info/docs/webdav-stuff.txt
A list of clients and servers
http://www.ics.uci.edu/~ejw/authoring/implementation.html
Its 11:30 - I should leave :-( No luck as yet.
Thursday, April 22, 2004
Tuesday, April 13, 2004
Windows Installer tools
WIX - Windows Installer in XML is Microsoft's install tool. It generates MSI from an XML file. This blog article discusses the tool. There was a lot of comments and interest, but most are related to Microsoft/OpenSource. A few actually talk about the tool.
The links mentioned the N'ANT project which may be interesting too. It has tasks to build MSM/MSIs.
MSI2XML converts MSI to XML and back.
Jumping from here to other topics.
A SOAP WSDL API for blogging: BloggerAPI and MetaWeblogAPI using WSDL/SOAP.
Very interesting BLOG about model driven programming. It talks about Whitehorse which is Microsoft's next generation development tools. What is fascinating is that both IBM (in its Rational Rose + Eclipse = WebSphere ) and Microsoft Whitehorse are moving in the same direction. From whatever screenshots I've seen, Whitehorse looks interesting.
The links mentioned the N'ANT project which may be interesting too. It has tasks to build MSM/MSIs.
MSI2XML converts MSI to XML and back.
Jumping from here to other topics.
A SOAP WSDL API for blogging: BloggerAPI and MetaWeblogAPI using WSDL/SOAP.
Very interesting BLOG about model driven programming. It talks about Whitehorse which is Microsoft's next generation development tools. What is fascinating is that both IBM (in its Rational Rose + Eclipse = WebSphere ) and Microsoft Whitehorse are moving in the same direction. From whatever screenshots I've seen, Whitehorse looks interesting.
Creating a secure Wiki site
To create a quick WIKI for an interest group is easy and fun to do. However as with all good things, you have Wiki idiots who want to inject some junk or trash your Wiki.
Check out TWIKI.ORG for a secure WIKI site.
Check out TWIKI.ORG for a secure WIKI site.
Tuesday, April 06, 2004
SAP Internet Pricing and Configurator engine
IPC is SAP's offline pricing engine and configuration engine. It lets you configure complex products without being on SAP R/3.
I've been working on a project to install this so that some marketing folks can see KMATs without logging onto SAP.
We started off with IPC 2.0C. While it has a decent SWING GUI, it lacks a web browser interface. The next step was to investigate IPC 3.0 SP18. In my opinion, 3.0 SP 18 proved to be the most stable release. Pricing and configuration worked like a charm. It was easy to install and was up and running relatively fast.
We pushed on to IPC 4.0 SP4. This was a beast to install. The latest SCA (Patch 2) released 4/1/2004 doesn't work! Unfortunately the SDM tool doesn't let to install an older version. You have to junk the entire J2EE installation. Ugh!
I've got the SWING GUI working. The JSP pages for configuration are working, but for some strange reason no-pricing.
The nice things in IPC 4 is a centralized configuration management tool (XCM). It also has better documentation. IPC 3 had its documentation all spread out. However, they throw in a whole lot more into the J2EE engine which in my opinion isn't really worth the centralized management. The web browser based XCM requires a lot of other libraries that you must install. In contrast, IPC 3 was small and easier (just 4 EAR files) to deploy.
After all the server fun, I need to create a client installation. The client installation is disconnected from SAP. To simplify things, we decide to strip it down to the bare essentials. I've got it down to an archive file and an install.cmd. This creates the SQL database, installs the classes and installs the JRE. Having a local JRE avoids messy Java conflicts with other versions on the user's PC.
So how long should it take?
1. Install the plug in on SAP, create a RFC port, CPIC user id - 1 day from the BASIS group.
2. Install the IPC server, J2EE engine and IPC web apps, initial download and test - 1 day
3. Client installation - 15 min.
So in 3 days, you can have a full IPC installation ready.
The question is what next?
Just having the JSP UI doesn't do much unless you plug it into your other applications.
But for me, that is where we stop since all we want to do is display and simulate!
Signing off.
I've been working on a project to install this so that some marketing folks can see KMATs without logging onto SAP.
We started off with IPC 2.0C. While it has a decent SWING GUI, it lacks a web browser interface. The next step was to investigate IPC 3.0 SP18. In my opinion, 3.0 SP 18 proved to be the most stable release. Pricing and configuration worked like a charm. It was easy to install and was up and running relatively fast.
We pushed on to IPC 4.0 SP4. This was a beast to install. The latest SCA (Patch 2) released 4/1/2004 doesn't work! Unfortunately the SDM tool doesn't let to install an older version. You have to junk the entire J2EE installation. Ugh!
I've got the SWING GUI working. The JSP pages for configuration are working, but for some strange reason no-pricing.
The nice things in IPC 4 is a centralized configuration management tool (XCM). It also has better documentation. IPC 3 had its documentation all spread out. However, they throw in a whole lot more into the J2EE engine which in my opinion isn't really worth the centralized management. The web browser based XCM requires a lot of other libraries that you must install. In contrast, IPC 3 was small and easier (just 4 EAR files) to deploy.
After all the server fun, I need to create a client installation. The client installation is disconnected from SAP. To simplify things, we decide to strip it down to the bare essentials. I've got it down to an archive file and an install.cmd. This creates the SQL database, installs the classes and installs the JRE. Having a local JRE avoids messy Java conflicts with other versions on the user's PC.
So how long should it take?
1. Install the plug in on SAP, create a RFC port, CPIC user id - 1 day from the BASIS group.
2. Install the IPC server, J2EE engine and IPC web apps, initial download and test - 1 day
3. Client installation - 15 min.
So in 3 days, you can have a full IPC installation ready.
The question is what next?
Just having the JSP UI doesn't do much unless you plug it into your other applications.
But for me, that is where we stop since all we want to do is display and simulate!
Signing off.
Saturday, April 03, 2004
Auto-complete of file and path names in Windows 2000/XP on command line
This rather cool tip lets you use the tab key to autocomplete entries on the command line.
----snip----
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor]
"AutoRun"=""
"CompletionChar"=dword:00000009
"DefaultColor"=dword:00000000
"EnableExtensions"=dword:00000001
"PathCompletionChar"=dword:00000009
----snip----
----snip----
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor]
"AutoRun"=""
"CompletionChar"=dword:00000009
"DefaultColor"=dword:00000000
"EnableExtensions"=dword:00000001
"PathCompletionChar"=dword:00000009
----snip----
Subscribe to:
Posts (Atom)